
MSNET: Network services already loaded, going "config"
Building a driver plug
-
in
First, recheck the
list of network drivers
again. People are sending
me drivers that are already on the list.
If you want to add a driver not listed, here is how tod
o that.
The driver must be a .CAB file. Let's build (for example) the E100B driver file. When
building an other driver, replace e100b with the name of the driver you are building.
You will need the NDIS2 Dos driver (e100b.dos) and you must create an e100
b.ini file, with
at least the "DriverName=" line.
Sample e100b.ini
DriverName=e100b$
; Some common parameters
;
; SPEED = [Auto | 10 | 100]
; FORCEDUPLEX = [Auto | 1 | 2]
;
1 = Half; 2 = Full
; SLOT = 0x38
; NODE = "00AA001
23456"
Also you must have a ndis.txt file.
Sample ndis.txt file
E100B Intel(R) PRO PCI Driver v4.27 062101
The ndis.txt file must have just 1 line (with CR/LF at the end) and it has two fields
separated by spaces (no tab!):
1.
Filename, must star
t at column 1, max. 8 chars
2.
Description, must start at column 14, max. 62 chars
If you plan on using a PCI adapter, you will also need the ndis.pci file which contains the
description and PCI Vendor/Device ID's of any adapters you intend on using. The s
ample
ndis.pci below illustrates the syntax of the file. To obtain the PCI Vendor/Device ID of your
particular card you can use:
1.
Craig's PCI diagnostic software
2.
Consult the list found at:
http://www.yourvote.com/pci/
Look up the Vendor ID and Device ID
3.
Use
PCIscan
Sample ndis.pci file
ret="E100B"
ven=8086 "Intel"
dev=1229 "8255x
-
based PCI Ethernet Adapter (10/100)"
2449 "PRO/100 VE Desktop Adapter"
1038 "PRO/100 VM Adapter"
1002 "PRO 100 Mobile Adapters"
See also:
Pciscan.txt file
Warning!
If you want to send your driver plug
-
in to me, make sure you are using the
real
ve
ndor driver.
Comentarios a estos manuales