Networking Connectivity
Intel® Server Adapters
Creating a DOS Boot Disk using Windows NT* 4.0 or Windows* 2000 Server

This information is provided solely as a convenience to Intel customers. If you have questions about Windows NT* or the Network Client Administrator tools, consult your Windows NT documentation (specifically, see the Microsoft Technet* article titled "How to Set Up the MS Network Client Version 3.0 for MS-DOS ") or contact Microsoft for assistance.

This capability is built into Windows NT 4.0 Server. See Microsoft Knowledgebase article Q252448 for information on how to add this capability to Windows 2000*.

Use this procedure when you have an Intel LAN adapter that is not listed on the list of adapters shown by Windows NT* 4.0 when creating a Network Installation Startup Disk.

To perform this task you will need:

  • The latest driver disk for the network adapter you are using.
  • A Windows NT 4.0 server with client directories or the Windows NT 4.0 installation CD.

Procedure:

  1. Create a DOS boot disk on a machine running MS-DOS 6.2x or newer.

  2. Place the disk in the disk drive on the Windows NT 4.0 server.

  3. Select Start, Programs, Administrative Tools (Common), Network Client Administrator.

  4. Be sure the Make Network Installation Startup Disk option is selected and click Continue.

  5. If you have not previously shared the network client files, either share the directory on the CD by selecting Share Files and entering a new shared directory name, or copy the files to a new directory by selecting "Copy Files to a New Directory, and then Share", then follow the on screen instructions to complete the creation of the new share.

  6. If you have previously shared the network client files, Use Existing Shared Directory should be selected. Click Ok.

    Note: The previous steps may fail if your server does not have a properly configured network interface and/or no IP address assigned.

  7. Select the Network Client v3.0 for MS-DOS and Windows in the Network Client window.

  8. From the list of adapters under Network Adapter Card select Intel EtherExpress 16 or 16TP. Click Ok.

  9. Type in the name of the computer that you will be booting. Type in the user name that you will logon as. Type in the domain. Choose the appropriate network protocol. Click Ok.

  10. Be sure the disk is in the disk drive and Click Ok again. Click Ok after the disk is created and Exit from Network Client Administrator. Click Ok on the final message about memory management.

  11. After the disk is created you will need to edit 3 text files on the disk. Use any text editor.

  12. Edit A:\AUTOEXEC.BAT. Delete the last 2 lines that read:

    echo Running Setup...
    z:\msclient\netsetup\setup.exe /$

    Save the file.

  13. Edit A:\NET\SYSTEM.INI. Go to the section labeled [network drivers]. You will notice the line:

    netcard=exp16.dos
    Change the name of the driver after the equal sign to the name of the NDIS DOS driver file on the driver disk for your adapter. For example, if you are using an Intel® PRO/100 S Desktop adapter the line will read:
    netcard=e100b.dos
    Save the file.

  14. Edit A:\NET\PROTOCOL.INI. Look for the section labeled [ms$ee16]. You will notice the line:

    drivername=EXP16$
    Change the name of the driver after the equal sign to the name of the DOS NDIS file, replacing the extension (.DOS or .EXE) with a dollar sign*. For example, if you are using an Intel® PRO/100 S Desktop adapter the line will read:
    drivername=e100b$
    Any optional NDIS 2 driver parameters (e.g. speed, duplex) should follow this entry. See the documentation for your specific product for available parameters.

    Save the file.

  15. Copy the ndis driver (usually a .DOS file, but some Intel mobile adapters use a .EXE file) from the adapter disk to the A:\NET directory on the boot disk.

  16. MOBILE ADAPTERS ONLY - All Intel mobile adapters that use the E100B.DOS NDIS driver also require the point enabler utility CBCOMBO.EXE. Copy this file to the A:\NET directory also. It should be called by the first line in the AUTOEXEC.BAT file and must be before the first NET command (e.g. a:\net\cbcombo memory=xxxx). Also, if EMM386 is loaded in the CONFIG.SYS, you may need to exclude the memory range used by the mobile adapter (e.g. DEVICE=A:\DOS\EMM386 RAM X=E000).

  17. You should be able to boot to this disk and it will log you onto the Windows NT 4.0 server.

Troubleshooting notes
The current NDIS 2 DOS driver for the Intel® PRO/1000 family (E1000.DOS) will work with EMM386.EXE loaded if used with members of the XT, XF, MT and MF families. It will not work with the PRO/1000 Server Adapter, PRO/1000 T Server Adapter or PRO/1000 F Server Adapter. EMM386.EXE must be version 4.49 or higher.

If you do not have sufficient room on the diskette, you can make more available space by deleting the file \NET\EXP16.DOS and the hidden file DRVSPACE.BIN.

**Some drivers do not use this convention, and there is a six character limit to the file name. If the driver name is longer than 6 characters, it should be truncated to the first 6 characters. Look on the driver disk for an example of what the driver name should be in the PROTOCOL.INI. For example, the Intel EtherExpress PRO 100 ISA adapter uses the name e100is$.

This applies to:

Intel® PRO/1000 MF Dual Port Server Adapter
Intel® PRO/1000 MF Server Adapter
Intel® PRO/1000 MF Server Adapter (LX)
Intel® PRO/1000 MT Dual Port Server Adapter
Intel® PRO/1000 MT Quad Port Server Adapter
Intel® PRO/1000 MT Server Adapter
Intel® PRO/1000 XF Server Adapter
Intel® PRO/1000 XT Server Adapter

Solution ID: CS-008440
Last Modified: 07-Oct-2013
Date Created: 18-Jan-2004
Back to Top