So, the v2 driver lives under D\L\1.  If I want add the v3 driver, are these the steps?
1. Unpack the LAN DriverPack (DP_LAN_wnt5_x86-32_8121.7z) file.
2. copy in the eg1032v3.inf, eg1032v3.cat, eg1032v3.sys files into the D\L\1 directory.
3. Repack the DriverPack.
4. Slipstream the new DriverPack.  (I read elsewhere that if I update a single driver, that
I can rerun the slipstream step without starting the CD build step from scratch?).

Looking at the top-level DriverPack_LAN_wnt5_x86-32.inf file, I'm wondering if some fields need to be updated there as well?  Here are the contents:

[DriverPack]
platform	= "wnt5_x86-32"
name		= "LAN"
rootDir		= "D\L"
; OPTIONAL
classes		= "Net"
driverCount	= "137"
decompSize	= 50.2
compSize	= 7.3
; 812

[NV3]
; REQUIRED
exc_count		= 1
; OPTIONAL
exc_1_tagFiles	= 0
exc_1_+hwids= 3
exc_1_+hwid1	= "PCI\VEN_10DE&DEV_00DF&SUBSYS_E0001458&REV_A2"
exc_1_+hwid2	= "PCI\VEN_10DE&DEV_00DF&SUBSYS_02501462&REV_A2"
exc_1_+hwid3	= "PCI\VEN_10DE&DEV_00DF&SUBSYS_A5511297&REV_A2"
exc_1_-hwids	= 0
exc_1_+infFiles	= 0
exc_1_-infFiles	= 0
exc_1_commands	= 2
exc_1_command1	= "%SystemDrive%\devcon.exe update %DPSROOT%\D\L\NV3\nvnetbus.inf "PCI\VEN_10DE&DEV_00DF&SUBSYS_*""
exc_1_command2 	= "%SystemDrive%\devcon.exe update %DPSROOT%\D\L\NV3\nvenetfd.inf "{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF""

I'm wondering if I need to bump the driverCount, decompSize, and compSize fields?  Anything else?

Hello,
Currently, the DriverPack has a EG1032v2 driver.  The newer cards are v3, and if this older driver is forced, a "cannot start [Error: 10]" results and the device is unusable.  The v3 driver is here:
http://downloads.linksysbycisco.com/dow … 2v3_dr.zip

A couple of questions (which might be FAQS):
1) if this driver were simply a newer version of the v2 driver, what are the steps required to replace the older driver in the DriverPack with the new one?

2) in this case, it is a different, new driver.  What is the best method for adding this new driver, if it isn't in the DriverPack? (I did read the FAQ warning that text mode drivers are a special case, and graphics drivers are complex).

thanks for all your hard work.