Creating a win95 boot disk

• Use mtools to create the image. Edit /usr/local/etc/mtools.conf and add the line:

  drive z: file=".drivez" 1.44m

• Create an empty `disk' (this creates a file called .drivez in your current directory):

  mformat -c z:

• Put the following files on it (the non-hyper linked files can be obtained from the win95 distribution or your NIC driver disk):

   Volume in drive Z has no label
   Volume Serial Number is 2382-8DE1
  Directory for Z:/
  
  aspi2hlp sys      1105 12-12-1999   8:11 
  autoexec bat       241 12-12-1999   8:11 
  bputil   com     28298 12-12-1999   8:11 
  command  com     93034 12-12-1999   8:11 
  config   sys        86 12-12-1999   8:11 
  e100b    dos     32371 12-12-1999   8:11 
  himem    sys     32935 12-12-1999   8:11 
  ifshlp   sys      3708 12-12-1999   8:11 
  io       sys    223148 12-12-1999   8:11 
  kdisable sys        66 12-12-1999   8:11 NOTE: Binary file
  kenable  com         7 12-12-1999   8:11 NOTE: Binary file
  msdos    sys       128 12-12-1999   8:11 
  ndishlp  sys      6140 12-12-1999   8:11 
  net      exe    375962 12-12-1999   8:11 
  net      msg         1 12-12-1999   8:11 
  protman  dos     22810 12-12-1999   8:11 
  protman  exe     14952 12-12-1999   8:11 
  protocol ini       278 12-12-1999   8:11 
  ramdrive sys     12663 12-12-1999   8:11 
  setver   exe     18939 12-12-1999   8:11 
  snapshot exe      6122 12-12-1999   8:11 
  system   dat     16384 12-12-1999   8:11 Registry dump of this
  win      bat      1124 12-12-1999   8:11 
  win0     bat       107 12-12-1999   8:11 
         24 files             890 609 bytes
                              560 128 bytes free
  

  Note that this particular image uses Incom's `tcp boot rom' (done before I knew about etherboot - duh :-)).
  bputil.com is a utility to remove the boot image from memory. If you are using etherboot, replace this with rmrd.com
• Customize the various files (system.dat, autoexec.bat, msdos.sys, win.bat, win0.bat, protocol.ini) for your situation.
• Make the image bootable by copying the first 512 byte block of a win95 boot disk to the image. Note that the dos 7.x boot block seems to know about the dos file system - the location of io.sys on the disk doesn't matter.
• If using etherboot, run mknbi-dos on .drivez file and copy the resulting file to your /tftpboot directory (give it a sensible name).
  If using incom's prom, copy the .drivez file to your /tftpboot directory.
  In both cases, make the new image the boot file for your client in your bootp or dhcp config file.
• The kdisable/kenable programs disable and enable the keyboard to prevent users from interrupting the boot process.
• There aren't many comments on what the various scripts do - may comments will be added at some time...
• Once you get the thing working, write some scripts to generate the boot disk with appropriately customized batch/registry/ini/etc. files.