|
|
|
 |
 |
|
| EtherExpress™ PRO/10 and PRO/10+ ISA adapters |
| Creating a Windows NT* Client Installation Disk |
|
 |
|
|
This information is provided as a convenience to Intel® customers. For
questions about Microsoft* Windows NT* or the Client Installation
process, consult the Windows NT *documentation or contact Microsoft* for
assistance.
The EtherExpress PRO/10 adapter does not appear on the list of
adapters in the Windows NT 3.50 Client Installation dialog. However, you
can select the EtherExpress 16 adapter, then modify the diskette to work
with the EtherExpress PRO/10 adapter. These instructions apply to both the
Windows for Workgroups Client and DOS Client Installation diskettes.
Creating the Client Installation Diskette
- At a DOS workstation, format a bootable floppy diskette to use as
the Client Installation diskette.
Example: FORMAT A: /S
- Go to the Windows NT* server and start it (if you haven't already).
- From the Program Manager in Windows NT*, choose the Network Administration
window.
- From the Network Administration window, choose the Network Client
Administration icon.
- In the Network Client Administration dialog box, choose Make Network
Installation Startup Disk, then choose Continue.
- In the Share Network Client Installation Files dialog box, choose
the appropriate action:
- If this is the first time you have run the Client Installation
program, choose Copy Files to New Directory, then Share. Insert
the Windows NT* CD ROM or diskettes as prompted.
- If you have previously copied the software, choose Use existing
path.
- Choose OK after making your choice.
- Enter the data requested in the Target Workstation Configuration
dialog box, using the appropriate settings:
- Choose the size of Floppy drive you intend to use (3.5 inches or
5.25 inches).
- Choose the type of Network client you desire (DOS Client 3.0 or
Windows for Workgroups 3.11).
- For Network Adapter Card, choose the Intel® EtherExpress 16 or 16 TP card.
- Choose OK after making your choices.
- If you select the Windows for Workgroups client, Windows NT*
displays the Microsoft Windows* for Workgroups Installation dialog
box. Choose OK after reading this dialog box. This dialog box will
not display if you select the DOS Client.
- Enter the data requested in the Network Startup Disk Configuration
dialog box, using the appropriate settings:
- For Computer Name, enter STARTUP. If you use a name other than
STARTUP, that name must not be used by any other workstation on
the network.
- For User Name, enter the name of your choice.
- For Domain, enter the domain name of your Windows NT server.
- For Network Protocol, choose NetBEUI unless you know you need a
different protocol.
- Choose OK after making your entries.
Modifying the Client Diskette for the EtherExpress PRO/10 Adapter
- Take the Client Installation diskette and the Intel® EtherExpress
PRO/10 adapter diskette to a computer that has a hard disk drive.
- Insert the EtherExpress PRO/10 adapter diskette and copy the EPRO.DOS file
to a temporary directory on the hard drive.
Example: COPY A:\NDIS\EPRO.DOS C:\TEMP
- Insert the Client Installation diskette and copy the EPRO.DOS file
into the NET subdirectory on the diskette.
- Example: COPY C:\TEMP\EPRO.DOS A:\NET
- Edit the SYSTEM.INI file found in the NET subdirectory of the
Client diskette, changing all occurrences of EE16 or EXP16 to EPRO.
The following samples show the original SYSTEM.INI file for the
EtherExpress 16 adapter and the changes required for the
EtherExpress PRO/10 adapter.
Note the asterisk (*) marks lines that are different between the two files.
| EtherExpress 16 adapter SYSTEM.INI |
EtherExpress Pro/10 adapter SYSTEM.INI |
| |
|
| [network] |
[network] |
| filesharing=no |
filesharing=no |
| printsharing=no |
printsharing=no |
| autologon=yes |
autologon=yes |
| computername=STARTUP |
computername=STARTUP |
| lanroot=A:\NET |
lanroot=A:\NET |
| username=Supervisor |
username=Supervisor |
| workgroup=Your_Group_Name |
workgroup=Your_Group_Name |
| reconnect=no |
reconnect=no |
| directhost=no |
directhost=no |
| dospophotkey=N |
dospophotkey=N |
| lmlogon=0 |
lmlogon=0 |
| logondomain=Your_Domain_Name |
logondomain=Your_Domain_Name |
| preferredredir=full |
preferredredir=full |
| autostart=full |
autostart=full |
| maxconnections=8 |
maxconnections=8 |
| |
|
| [network drivers] |
[network drivers] |
| *netcard=exp16.dos |
netcard=epro.dos |
| transport=ndishlp.sys,*netbeui |
transport=ndishlp.sys,*netbeui |
| devdir=A:\NET |
devdir=A:\NET |
| LoadRMDrivers=yes |
LoadRMDrivers=yes |
| |
|
| [Password Lists] |
[Password Lists] |
- Edit the PROTOCOL.INI file found in the NET subdirectory of the
Client diskette. Change all occurrences of EE16 or EXP16 to EPRO.
The following samples show the original PROTOCOL.INI file for the
EtherExpress 16 adapter and the changes required for the
EtherExpress PRO/10 adapter.
Note the asterisk (*) marks lines that are different between the
two files.
| EtherExpress 16 adapter PROTOCOL.INI |
EtherExpress Pro/10 adapter PROTOCOL.INI |
| |
|
| [network.setup] |
[network.setup] |
| version=0x3110 |
version=0x3110 |
| *netcard=ms$ee16,1,MS$EE16,1 |
netcard=ms$epro,1,MS$EPRO,1 |
| transport=ms$ndishlp,MS$NDISHLP |
transport=ms$ndishlp,MS$NDISHLP |
| transport=ms$netbeui,MS$NETBEUI |
transport=ms$netbeui,MS$NETBEUI |
| *lana0=ms$ee16,1,ms$netbeui |
lana0=ms$epro,1,ms$netbeui |
| *lana1=ms$ee16,1,ms$ndishlp |
lana1=ms$epro,1,ms$ndishlp |
| |
|
| *[ms$ee16] |
[ms$epro] |
| *drivername=EXP16$ |
drivername=EPRO$ |
| ;IRQ=3 |
;IRQ=3 |
| ;IOADDRESS=0x310 |
;IOADDRESS=0x310 |
| ;IOCHRDY=Late |
;IOCHRDY=Late |
| ;TRANSCEIVER=Thin Net (BNC/COAX) |
;TRANSCEIVER=Thin Net (BNC/COAX) |
| |
|
| [protman] |
[protman] |
| drivername=PROTMAN$ |
drivername=PROTMAN$ |
| PRIORITY=MS$NDISHLP |
PRIORITY=MS$NDISHLP |
| |
|
| [MS$NDISHLP] |
[MS$NDISHLP] |
| drivername=ndishlp$ |
drivername=ndishlp$ |
| *BINDINGS=ms$ee16 |
BINDINGS=ms$epro |
| |
|
| [ms$netbeui] |
[ms$netbeui] |
| drivername=netbeui$ |
drivername=netbeui$ |
| SESSIONS=10 |
SESSIONS=10 |
| NCBS=12 |
NCBS=12 |
| *BINDINGS=ms$ee16 |
BINDINGS=ms$epro |
| LANABASE=0 |
LANABASE=0 |
- Follow the instructions in the Windows NT* documentation for using the
Client Installation diskettes to install the client software.
Troubleshooting Hints
NET INITIALIZE command reports:
Warning: PROTOCOL.INI missing a Key Entry for IOADDRESS. An EtherExpress PRO adapter is found at I/O address XXXh.
- Note the address reported in the warning message.
- Edit the PROTOCOL.INI file in the \NET directory of the Client
Installation diskette, making these changes:
- Delete the semicolon (;) on the IOADDRESS line found in the
[ms$epro] section of the PROTOCOL.INI.
- Make sure the IOADDRESS matches the number displayed in the
warning. For example, if the warning message reported finding the
adapter at the address 210h, the IOADDRESS line should read
IOADDRESS=0x210
NET USE command reports:
ERROR 53: The computer name specified in the network path cannot be
located.
Make sure the network path specified on the NET USE command line in the
AUTOEXEC.BAT file matches that on the server you used to create Client
Installation diskette. To do this:
- Open the Network Administration window from Program Manager.
- Choose the Network Client Administrator icon.
- Choose Continue.
- Compare the setting for the path in this dialog box with the path
listed on the NET USE command in the AUTOEXEC.BAT file.
This applies to:
|
|
 |
|
End of Interactive Support AnnouncementThese products are no longer being manufactured by Intel. Additionally, Intel no longer provides interactive support for these products via telephone or e-mail, nor will Intel provide any future software updates to support new operating systems or improve compatibility with third party devices and software products.
THESE DOCUMENTS ARE PROVIDED FOR HISTORICAL REFERENCE PURPOSES ONLY AND ARE SUBJECT TO THE TERMS SET FORTH IN THE "LEGAL INFORMATION" LINK BELOW.For information on currently available Intel products, please see www.intel.com and/or developer.intel.com
|
|
Solution ID: CS-010522
Date Created: 15-Apr-2004
Last Modified: 23-Oct-2006
|
|