From: Subject: Creating a Network Boot Disk Date: Tue, 23 Oct 2001 12:31:23 +0200 MIME-Version: 1.0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Content-Location: http://scilnet.fortlewis.edu/tech/Network/bootdisk.htm X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Creating a Network Boot Disk
Creating a Network Boot Disk

NDIS - Network Driver Interface Specification (Microsoft)=20

EtherExpress=99 PRO/100A Adapter =
Creating a Client Install Disk for Windows NT*

The EtherExpress=99 PRO/100 adapter does not appear on the list of = adapters in=20 the Windows NT 3.50, Windows NT 3.51, Windows NT 4.0 Client Installation = dialog.=20 However, you can select the EtherExpress 16 adapter, then modify the = diskette to=20 work with the EtherExpress PRO/100. These instructions apply to both the = Windows=20 for Workgroups Client and DOS Client Installation disks.

Creating the Client Installation diskette

  1. At a DOS workstation, format a bootable floppy diskette to use as = the=20 Client Installation diskette.=20

    Example: FORMAT A: /S

  2. Go to the Windows NT server and start it (if you haven't already). =

  3. From the Program Manager in NT, choose the Network Administration = window.=20

  4. From the Network Administration window, choose the Network Client=20 Administration icon.

  5. In the Network Client Administrator dialog box, choose Make = Network=20 Installation Startup Disk, then choose Continue.

  6. In the Share Network Client Installation Files dialog box, choose = the=20 appropriate action:=20

    • If this is the first time you have run the Client Installation = program,=20 choose Copy Files to New Directory, then Share. Insert the Windows = NT CD ROM=20 or diskettes as prompted.=20

    • If you have previously copied the software, choose Use existing = path.=20

    • Choose OK after making your choice.


  7. Enter the data requested in the Target Workstation Configuration = dialog=20 box, using the appropriate settings:=20

    • Choose the size of Floppy drive you intend to use (3.5" or = 5.25")=20

    • Choose the type of Network client you desire (DOS Client 3.0 or = Windows=20 for Workgroups 3.11=20

    • For Network Adapter Card, choose Intel EtherExpress 16 or 16 TP. =

    • Choose OK after making your choices.


  8. If you select the Windows for Workgroups client, Windows NT = displays the=20 MS Windows for Workgroups Installation dialog box. Choose OK after = reading=20 this dialog box. This dialog box will not display if you select the = DOS=20 Client.

  9. Enter the data requested in the Network Startup Disk Configuration = dialog=20 box, using the appropriate settings:=20

    • For Computer Name, enter STARTUP. If you use a name other than = STARTUP,=20 that name must not be used by any other workstation on the network.=20

    • For User Name, enter the name of your choice.=20

    • For Domain, enter the domain name of your Windows NT server.=20

    • For Network Protocol, choose NetBEUI unless you know you need a=20 different protocol.=20

    • Choose OK after making your entries.

Modifying the Client diskette for the EtherExpress PRO/100 = adapter

  1. Take the Client Installation diskette and the Intel EtherExpress = PRO/100=20 diskette to a computer that has a hard disk drive.

  2. Insert the EtherExpress PRO/100 diskette and copy the E100.DOS = file to a=20 temporary directory on the hard drive.=20

    Example: COPY A:\NDIS\E100.DOS C:\TEMP

  3. Insert the Client Installation diskette and copy the E100.DOS file = into=20 the NET subdirectory on the diskette.=20

    Example: COPY C:\TEMP\E100.DOS A:\NET

  4. Edit the SYSTEM.INI file found in the NET subdirectory of the = Client=20 diskette, changing all occurrences of EE16 or EXP16 to E100. The = following=20 samples show the original SYSTEM.INI file for the EtherExpress 16 = adapter and=20 the changes required for the EtherExpress PRO/100 adapter.=20

    NOTE: The * (asterisk) marks lines that are different = between the=20 two files.

    NOTE: This code is case sensitive.

    EtherExpress=20 16
    SYSTEM.INI    		 EtherExpress=20 PRO/100
    SYSTEM.INI
    [network] [network]
    filesharing=3Dno filesharing=3Dno
    printsharing=3Dno printsharing=3Dno
    autologon=3Dyes autologon=3Dyes
    computername=3DSTARTUP computername=3DSTARTUP
    lanroot=3DA:\NET lanroot=3DA:\NET
    username=3DSupervisor username=3DSupervisor
    workgroup=3DYour_Group_Name = workgroup=3DYour_Group_Name
    reconnect=3Dno reconnect=3Dno = directhost=3Dno
    directhost=3Dno dospophotkey=3DNdospophotkey=3DN
    lmlogon=3D0 lmlogon=3D0
    logondomain=3DYour_Domain_Name logondomain=3DYour_Domain_Name
    preferredredir=3Dfull preferredredir=3Dfull =
    maxconnections=3D8 maxconnections=3D8
    autostart=3Dfull autostart=3Dfull
    [network drivers] [network drivers]
    *netcard=3Dexp16.dos netcard=3De100.dos
    transport=3Dndishlp.sys,*netbeui transport=3Dndishlp.sys,*netbeui
    devdir=3DA:\NET devdir=3DA:\NET
    LoadRMDrivers=3Dyes LoadRMDrivers=3Dyes
    [Password Lists] [Password=20 Lists]

  5. Edit the PROTOCOL.INI file found in the NET subdirectory of the = Client=20 diskette, changing all occurrences of EE16 or EXP16 to E100. The = following=20 samples show the original PROTOCOL.INI file for the EtherExpress 16 = adapter=20 and the changes required for the EtherExpress PRO/100 adapter.=20

    NOTE: The * (asterisk) marks lines that are different = between the=20 two files.

    NOTE: This code is case sensitive.

    EtherExpress=20 16
    PROTOCOL.INI    		 EtherExpress
    PRO/100=20 PROTOCOL.INI
    [network.setup] [network.setup]
    version=3D0x3110 version=3D0x3110
    *netcard=3Dms$ee16,1,MS$EE16,1 = netcard=3Dms$e100,1,MS$E100,1
    transport=3Dms$ndishlp,MS$NDISHLP transport=3Dms$ndishlp,MS$NDISHLP
    transport=3Dms$netbeui,MS$NETBEUI = transport=3Dms$netbeui,MS$NETBEUI
    *lana0=3Dms$ee16,1,ms$netbeui = lana0=3Dms$e100,1,ms$netbeui
    *lana1=3Dms$ee16,1,ms$ndishlp = lana1=3Dms$e100,1,ms$ndishlp
    *[ms$ee16] [ms$e100]
    *drivername=3DEXP16$ drivername=3DE100$ ;IRQ=3D3 = ;IRQ=3D3
    ;IOADDRESS=3D0x310 IOADDRESS=3D0x310 =
    ;IOCHRDY=3DLate IOCHRDY=3DLate
    TRANSCEIVER=3DThin = Net(BNC/COAX) TRANSCEIVER=3DThin = Net(BNC/COAX)
    [protman] [protman]
    drivername=3DPROTMAN$ drivername=3DPROTMAN$
    PRIORITY=3DMS$NDISHLP PRIORITY=3DMS$NDISHLP
    [MS$NDISHLP] [MS$NDISHLP]
    drivername=3Dndishlp$ drivername=3Dndishlp$
    *BINDINGS=3Dms$ee16 BINDINGS=3Dms$e100
    [ms$netbeui] [ms$netbeui]
    drivername=3Dnetbeui$ drivername=3Dnetbeui$ =
    SESSIONS=3D10 SESSIONS=3D10
    NCBS=3D12 NCBS=3D12
    *BINDINGS=3Dms$ee16 BINDINGS=3Dms$e100 =
    LANABASE=3D0 LANABASE=3D0

  6. Follow the instructions in the Windows NT documentation for using = the=20 Client Installation diskettes to install the client software. =
Troubleshooting hints=20

*NET USE command reports --

ERROR 53: The computer name specified in the network path cannot be=20 located.

Make sure the network path specified on the NET USE command line in = the=20 AUTOEXEC.BAT file matches the path shown on the server you used to = create Client=20 Installation diskette.To do this:

  1. Open the Network Administration window from Program Manager.=20
  2. Choose the Network Client Administrator icon=20
  3. Choose the Continue.=20
  4. Compare the setting for the Path in this dialog box with the path = listed=20 on the NET USE command in the AUTOEXEC.BAT=20 file.