Creating the images Creating the floppy boot image (using WinImage): 1.

Get a Windows 98 SE OEM boot image (http://www.bootdisk.com/bootdisk.htm) and open it using WinImage 2. Delete all files except autoexec.bat, command.com, config.sys, himem.sys, io.sys, and oakcdrom.sys. 3. Overwrite (drag and drop) autoexec.bat and config.sys in the image with the ones located in the BOOT folder, and add mscdex.exe to the image. 4. Save the image (File => Save) as Image file (*.ima) Creating the CD image (using MagicISO) 1. Open MagicISO and select File => New => Bootable CD/DVD Image 2. Select From bootable image file, and select the boot image you created with WinImage 3. Drop the files from the CD folder into MagicISO 4. Save the image Boot Image Details Files Autoexec.bat commands that are executed automatically once DOS is finished loading drivers Command.com command line interpreter (CLI); processes all commands and loads drivers Config.sys contains configuration parameters for DOS and loads device drivers Himem.sys extended memory management driver (provided by Microsoft) Io.sys Mscdex.exe CD-ROM interface application; maps CD-ROM to a drive letter Oakcdrom.sys CD-ROM driver Config.sys Sets IO parameters, last drive letter, and loads extended memory driver and CD-ROM driver Autoexec.bat Loads the CD-ROM interface application into extended memory and maps the CDROM to drive G, referencing the device driver name mscd001 as set in config.sys when loading the CD-ROM driver Creates an environment variable named CDROM, and sets the value to G: Adds the CD-ROM drive letter to the PATH environment variable Changes the current drive to the CD-ROM Executes exec.bat on the CD

CD Details Files GHOST\GHOST.EXE Symantec Ghost 8.2 executable GHOST\MOUSE.COM Mouse interface driver GHOST\MOUSE.INI Mouse configuration file (sets mouse type to PS2) PCI\NET\[DRIVER]\[DRIVER].DOS NDIS2 driver for NIC PCI\NET\[DRIVER]\PROTOCOL.INI Configuration file for NIC PCI\NET\NETBIND.COM Microsoft DOS LAN Manager Netbind PCI\NET\DIS_PKT.DOS MAC/DIS to Packet Driver converter PCI\NET\PROTMAN.DOS Microsoft DOS Protocol Manager PCI\NET\PROTMAN.EXE Microsoft DOS Protocol Manager PCI\device.com CLI device driver loader PCI\loadnic.bat NIC detection and initialization script PCI\niclist.map NIC device to driver mappings PCI\pciscan.exe DOS hardware detection application exec.bat executed by autoexec.bat on the boot image to continue automated procedures EDITVAR.EXE user input interface

Exec.bat Calls the pci\loadnic.bat script Executes EDITVAR to prompt the user for the name of the GhostCast session and store it in the environment variable gcast Loads the mouse interface driver Executes Ghost with the parameters clone, source is GhostCast session (using the name stored in the environment variable gcast), destination is drive 1, automatically reboot upon completion, and execute Ghost without any user interaction Loadnic.bat Empties pci0, pci1, and pci2 environment variables Executes pciscan, passing niclist.map as the hardware maps file If a NIC is found (if pci0 is not empty): o The device driver name is stored in the environment variable pci0, as specified by niclist.map o Loads protman.dos (Microsoft DOS Protocol Manager), passing the path of the folder in which the NIC driver and its corresponding PROTOCOL.INI is located o Loads dis_pkt.dos (MAC/DIS to Packet Driver converter) o Loads the NIC device driver o Executes netbind.com (Microsoft DOS LAN Manager Netbind) If a NIC is not found (if pci0 is empty): o A message is displayed to the user and the PCI devices that were found are listed

Niclist.map Contains a listing of PCI device mappings and the return values in the following format: ret=NIC_driver_name ven=NIC_vendor_id Vendor_name dev=NIC_device_id Device_description To add another NIC to the CD 1. Obtain the NICs vendor and device ids These can be found using one of the following methods: o In Device Manager in Windows, go to the NICs device properties, select the Details tab, and look at the Hardware Ids. You will see PCI\VEN_1234&DEV_4567&. 1234 and 4567 are the vendor and device ids, respectively o When booting the computer from the CD, if the NIC is not detected, a list of PCI devices that were found will be displayed, including the vendor and device ids (Vend and Dev.) 2. Obtain the NDIS2 driver for the NIC This should include a .DOS file and a PROTOCOL.INI file. 3. Create a new folder inside the PCI\NET folder with the driver name (for example, if the driver file is B44.DOS, then create a folder named B44). Place the DOS driver and the PROTOCOL.INI file inside this folder. Note that in some instances, you may already have the driver on the CD for the NIC you need, but the mapping for that specific card isnt in the hardware mappings list. If that is the case, only replace the .DOS file if the one you downloaded it newer than the one already in the folder, and proceed to step 5. 4. Format the PROTOCOL.INI file properly. The following is required: [protman] drivername=PROTMAN$ [pktdrv] drivername=PKTDRV$ bindings=nic intvec=0x60

chainvec=0x66 [nic] drivername=NIC_driver_name$ (for example, for B44.DOS, this should read b44$) There may be additional parameters required. See the NICs original PROTOCOL.INI for details. 5. Modify the PCI\niclist.map file. Add the appropriate vendor and device ids. The ret value should be the NIC driver name (same as the NIC driver folder name) 6. Update the ISO with the new niclist.map file and add any necessary folders into the NET folder. 7. Burn the ISO.