How to create a network boot Virtual Floppy Disk file without ever using a floppy drive using DeployCenter tools.

Article:TECH109545  |  Created: 2006-01-18  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH109545
Article Type
Technical Solution


Environment

Issue



Below are the steps on how to create a network boot Virtual Floppy Disk (VFD) on systems having no floppy disk drive.

 


Solution



The following will be needed to create a VFD:
 

  • Symantec DeployCenter 5.7 VFeditor.
  • OEM-supplied NDIS2 (or DOS) driver (e.g. *.DOS file) from the manufacturer of the network interface card.
  • Symantec Ghost Boot Wizard (Optional).

I. Create a Virtual Boot Disk (VFD) file:

  1. Launch Symantec Boot Disk Builder by clicking on Start > Programs > Symantec DeployCenter 5.7.0 > DeployCenter 5.7.0 Tools > Boot disk builder.
  2. At the first screen click Standalone Boot disks.
  3. Click on the Next button.
  4. In the "Specify ImageCenter location and command line parameters" window, select Do not run Imagecenter.
  5. Click the Next button.
  6. In the "Standalone Boot Disks" window, click the Virtual Boot disk file radio button.
  7. Click the ellipse (...) button to the right of the "Virtual Boot disk file" section.
  8. In the Open window, navigate to or select Desktop.
  9. Type a file name (e.g. GhostNBF.vfd) in the file name field.
  10. Click on the Open button.
  11. In the "Symantec Boot Disk Builder" window, click  the Finish button.
  12. If prompted: "Would you like to save these settings for future use?", click the No button.
  13. Click on the Exit button.

II. Add Ghost.exe and NIC driver the Virtual Boot Disk file:

  1. Launch VF Editor by clicking on Start > Programs > Symantec DeployCenter 5.7.0 > DeployCenter 5.7.0 Tools > VFEditor.
  2. Open the .VFD file created in step 9 above:
    1. Click File > Open.
    2. Navigate to the desktop.
    3. Select the .VFD file.
    4. Click on the Open button.
  3. Once the floppy image file has been read click Image.
  4. Click Change Format.
  5. Click the radio button by 2.88 MB.
  6. Click OK.
  7. Click File > Save to save the changes made to .VFD file.
  8. Press Ctrl + Left click on following files: pqdotask.bat and restrmbr.exe.
  9. Right click the highlighted files and click Delete File.
  10. If prompted, click OK to the warning.
  11. Using Windows Explorer create a sub-folder called "Ghost" on the desktop.
  12. Copy "C:\Program Files\Symantec\Ghost\Ghost.exe" to the "Ghost" folder.
  13. Using Windows Explorer create a sub-folder called "Net" on the desktop.
  14. Navigate to "C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common".
  15. Copy the following files into the "Net" folder on the desktop: DIS_PKT.DOS, netbind.com, protman.dos, protman.exe.
  16. Do either a or b. (Doing substep a. will add the NIC driver to Ghost console for future use and doing substep b. will add the Network driver just to the VDF file being created.)
    1. Add network driver to ghost console:
      1. Create a network interface card (NIC) template for the client machine this .VFD will be used with. Please refer to the Symantec Knowledge Base document Adding or modifying NIC templates in the Ghost Boot Wizard (http://service1.symantec.com/support/on-technology.nsf/docid/2000011211551725) for more information.
      2. Once the NIC template has been obtained, copy the .dos file and .ini files located in the following folder to the desktop:
        C:\Documents and Settings\All Users\Application. Data\Symantec\Ghost\Template\.
      3. Using Windows Explorer copy the "*.DOS" and "*.INI" files to the "Net" folder created on the Windows desktop.
      4. Go to step 17.
    2. Add network drivers only to this VDF:
      1. Download and unpack (if needed) the OEM-supplied NDIS2 (or DOS) driver (e.g. *.DOS file) from the manufacturer of the network interface card and place them on the desktop.
      2. Create a new notepad file name titled: "protocol.ini" and save it to the desktop that includes the following text:
        [protman]
        drivername=PROTMAN$
        [pktdrv]
        drivername=PKTDRV$
        bindings=nic
        intvec=0x60
        chainvec=0x66
        [nic]
        drivername =<
        driver_name>$
        Where ": is the first eight characters of the filename of the OEM-supplied "NDIS2 *.DOS" file.
        (e.g. if the file name of the OEM-supplied NDIS2 driver is B57.DOS then the drivername value within the "protocol.ini" field would be "drivername = b57$").
      3. Using Windows Explorer copy the "*.DOS" and "*.INI" files to the "Net" folder created on the Window's desktop.
  17. Drag and drop the "Net" and "Ghost" sub-folders from the windows desktop into VF editor.
  18. Drag and drop out of  VF editor to the windows desktop "autoexec.bat" and "config.sys" files and then click Yes if prompted to copy files to desktop.
  19. Using Notepad, edit the "autoexec.bat" and "config.sys" files so that they contain the following:

    AUTOEXEC.BAT
    @echo off
    SET TZ=GHO+08:00
    prompt $p$g
    \net\netbind.com
    if exist MOUSE.COM MOUSE.COM
    echo Loading...
    cd \ghost
    echo Loading...

    GHOST.EXE

    CONFIG.SYS
    DEVICE=\net\protman.dos /I:\net
    DEVICE=\net\dis_pkt.dos
    DEVICE=\net\<
    name_of_dos_driver>
    LASTDRIVE = Z

    this is the name of name of the OEM-supplied NDIS2 DOS Network interface card driver that will be used by the client of this *.VFD (e.g. B57.DOS)
  20. Click Save to save the changes made to "autoexec.bat" and "config.sys" files within notepad, then drag and drop the files back into the "VFEditor" window.
  21. Click OK to inject files and Yes on each file to "Overwrite existing files."
  22. Click File and select Save to save the changes made to "*.VFD file."


    The "*.VFD file" is now ready to be tested.
The "*.VFD file"

can be use to:

    • Deploy Center’s PXE configuration utility,
    • Creating a floppy disk emulated CD.
    • Packaging within a quick boot executable created with "Symantec Boot Disk Builder."




 



Legacy ID



2006121815121225


Article URL http://www.symantec.com/docs/TECH109545


Terms of use for this information are found in Legal Notices