【求助】如何在MS-DOS驅動網卡

**ahwamidi** · 2004-05-06, 09:47 PM

我在WINDOWS XP驅動是顯示Intel 21140-Based PCI Fast Ethernet Adapter (Generic)
那我該如何驅動在DOS呢?
有詳細資料嗎

**purk** · 2005-07-12, 08:05 PM

Creating a Network Boot Disk
NDIS - Network Driver Interface Specification (Microsoft)

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

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

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 NT, choose the Network Administration window.

From the Network Administration window, choose the Network Client Administration icon.

In the Network Client Administrator 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" or 5.25")

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

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

Choose OK after making your choices.

If you select the Windows for Workgroups client, Windows NT displays the MS 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/100 adapter

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

Insert the EtherExpress PRO/100 diskette and copy the E100.DOS file to a temporary directory on the hard drive.
Example: COPY A:\NDIS\E100.DOS C:\TEMP

Insert the Client Installation diskette and copy the E100.DOS file into the NET subdirectory on the diskette.
Example: COPY C:\TEMP\E100.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 E100. The following samples show the original SYSTEM.INI file for the EtherExpress 16 adapter and the changes required for the EtherExpress PRO/100 adapter.
NOTE: The * (asterisk) marks lines that are different between the two files.

NOTE: This code is case sensitive.

EtherExpress 16
SYSTEM.INI EtherExpress PRO/100
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=Ndospophotkey=N
lmlogon=0 lmlogon=0
logondomain=Your_Domain_Name logondomain=Your_Domain_Name
preferredredir=full preferredredir=full
maxconnections=8 maxconnections=8
autostart=full autostart=full

[network drivers] [network drivers]
*netcard=exp16.dos netcard=e100.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, changing all occurrences of EE16 or EXP16 to E100. The following samples show the original PROTOCOL.INI file for the EtherExpress 16 adapter and the changes required for the EtherExpress PRO/100 adapter.
NOTE: The * (asterisk) marks lines that are different between the two files.

NOTE: This code is case sensitive.

EtherExpress 16
PROTOCOL.INI EtherExpress
PRO/100 PROTOCOL.INI
[network.setup] [network.setup]
version=0x3110 version=0x3110
*netcard=ms$ee16,1,MS$EE16,1 netcard=ms$e100,1,MS$E100,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$e100,1,ms$netbeui
*lana1=ms$ee16,1,ms$ndishlp lana1=ms$e100,1,ms$ndishlp

*[ms$ee16] [ms$e100]
*drivername=EXP16$ drivername=E100$ ;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$e100

[ms$netbeui] [ms$netbeui]
drivername=netbeui$ drivername=netbeui$
SESSIONS=10 SESSIONS=10
NCBS=12 NCBS=12
*BINDINGS=ms$ee16 BINDINGS=ms$e100
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 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 the path shown 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 the 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.