Bart's Network Boot Disk
...People tell me my network bootdisk is by far the best found on the web...
Version 2.7
Last updated on Mar 30, 2004
Important notice: the development and maintenance for this page has stopped. Please don't contact me about this page! I'm leaving the page as it is, for reference...
Table of contents
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 to do 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 e100b.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 = "00AA00123456"
|
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!):
- Filename, must start at column 1, max. 8 chars
- 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 sample ndis.pci below illustrates the syntax of
the file. To obtain the PCI Vendor/Device ID of your particular card you
can use:
-
Craig's PCI diagnostic software
- Consult the list found at: http://www.pcidatabase.com/
Look up the Vendor ID and Device ID
- 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 vendor driver.
You can check this by looking up the vendor (V) and device (D) ID in
Craig's pcidevs.txt.
Pack the files e100b.dos, e100b.ini, ndis.txt and ndis.pci into a cab
file called e100b.cab and you are done.
Don't include a protocol.ini. Msnet uses e100b.ini not protocol.ini.
An easy way to build your cab files:
- Download makev3.zip (59KB) and unpack it in
some directory, let say c:\modboot\makev3\
- In the "source" directory create a directory called "e100b".
Put your files e100b.dos, e100b.ini, ndis.txt and ndis.pci
into this directory (c:\modboot\makev3\source\e100b).
- Open a command prompt, goto the c:\modboot\makev3\ directory and run
"make e100b". If all goes OK, you can find your module as
c:\modboot\makev3\cabs\e100b.cab
Again... when building an other driver, replace "e100b" with the name of the
driver you are building.
If the NIC is a PCMCIA card there is no need to create a ndis.pci file but do
create an autorun.bat containing the command to execute the card's Enabler.
Prefix the Enabler's file name with %ramdrv%\net\.
| Sample autorun.bat file |
|---|
@echo off
echo AUTORUN:
%ramdrv%\net\3celcm.exe
echo.
|
