Warning :

I removed all links to boot images and network drivers because my provider ask me to.

 

The information here may still be valuable to you as a tutorial, However, Bart's page on network boot disks on http://www.nu2.nu/bootdisk is the best shop in town for all this.

 

 

Do not send emails about netutils.zip or other Microsoft patented material, I will not send any of those.

You may however ask me to send you some of the freeware tools referenced in this page

 

 

How to create a bootable TCP/IP CD-ROM

  1. a \NET and a \DOS directory on the CD 

  2. a boot disk with a boot menu to choose the NIC (it sets a variable)

  3. This boot disk creates a ramdisk (on a specified letter), I used xmsdisk from

  4. The AUTOEXEC.BAT script copies (or unzip ) the \net directory onto the RAM DISK depending on wether it is a bootable floppy , CD or HDD.

  5. The NETCFG.BAT script modifies protocol.ini and system.ini depending on the chosen NIC and on questions it asks you (DHCP or NOT, Domain Name...).

  6. NETSTART.BAT loads all the drivers

Check those files :

N.B. the boot menu must have CD-ROM driver loaded and enough memory to load network drivers which can be really big 

here is the \NET subdirectory to put at the root of your CD and the boot DISK (uses winimage http://www.winimage.com ) to give to your burning software, you have to write it to a diskette first !

 

Note: the NETSTART.BAT script loads a special IP stack (dis_pkt.dos) which comes with GHOST and DriveImage. This enables you to use the IP features (multicast...) of both products

 

 

Here are the tools I used to make this boot disk

 

Create a Boot FLOPPY with NET capabilities

 

In order to create a boot floppy we have to pack both DOS files and Network drivers on a single Floppy. These files are packed into two ZIP files. Only necessary files are present uncompressed on the floppy disk

 

For a floppy-based network boot disk includes the following files:

Content of the Netutils.ZIP file :

Content of the NET.ZIP file :

Lanman DOS client files :

CONNECT.DAT
DRIVERS.DOS
EMSBFR.EXE

LMHOSTS
MDGND.DOS
NDISHLP.SYS
NEMM.DOS
NET.EXE
NET.MSG
NETWORKS
NMTSR.EXE
PROTMAN.DOS
PROTMAN.EXE
PROTOCOL
SETUP.INF
TCPDRV.DOS
TCPTSR.EXE
TCPUTILS.INI
TINYRFC.EXE
UMB.COM
WCSETUP.INF
WFWSYS.CFG

DIS_PKT.DOS, packet driver for ghost and drive Image

configuration files:

PROTOCOL.INI  

SYSTEM.INI

batch files:

NETCFG.BAT

NETSTART.BAT

NIC drivers :

XCEMNDIS.EXE

NE2000.DOS    

OCE20ND2.DOS
OCE4XND2.DOS
OCTENABL.DOS, enabler for Olicom PCMCIA boards
OLITOK16.DOS
CBENDIS.EXE
E100B.DOS
EL59X.DOS
EL90X.DOS
ELNK3.DOS
NETFLX3.DOS
PCIND.DOS , PCi ne2000

How do you add a NIC ?

 

To add a NIC you need 2 things :

Add the NIC file to the NET directory

Add two lines to the NETCFG.BAT file (the file is self-explaining)

Add a submenu item and a section under the same name to CONFIG.SYS

If this is a PCI board, edit NIC.MAP file to return the id  string as in CONFIG.SYS and NETCFG.BAT, this will enable PCISCAN to detect it.