This is not (directly) a DriverPacks issue...

Thanks CDOB... as always, you have taught me something. Dont ever stop teaching me PE, You're the best

e1000325.inf

e1000325.din is used at uninstall. PROUNSTL.EXE is used at uninstall too.
Both files are not required to access hardware.

What happens:

PNP tries to copy files and fails at PE.
PNP seems to compare existing files. If a file is missing, driver is not installed.
Network card is missing.

A work arround seems to be: include all files, even non required one.

911cd work arround: copy basic required files and comment CopyFiles lines.

InfCacheBuild was developed to create Infcache.1 and to adjust *.inf files http://oss.netfarm.it/winpe/

PE PNP dosn't copy files anymore, use existing files.
Network driver is loaded. Network card does work.

Current DriverPacks BASE does add necessary files to get a working NIC card.
*.sys and *.dll files are sufficient.

Some possibilities:
Adjust DriverPacks BASE to include uninstall files. That's a waste of space at boot media.
Or adjust *.inf files:
a new, adjustable DriverPacks BASE part to edit *.inf files. (CopyFiles is a example, there are more entries)
Or use InfCacheBuild: ask the end user to use InfCacheBuild.

UBCD4Win build script does use InfCacheBuild.

And remember: most NIC drivers does work at original *.inf files.

All other drivers work just fine without their supporting files in BartPE. In most all cases (99%) only the .INF and the .SYS file are required for BartPE.  I don't see any reason to bloat the PE footprint past the 700k CD limit without a valid reason. I am absolutely not going to globaly include all files for all drivers, that would make the final BartPE disc well over 3 gig.

If certain drivers need support files included then we need to simply/only include those specific files for those specific drivers... So far we are only talking about certain Intel LAN drivers. I am also not convinced at this time that the EXE file is required. It is likely that the .DIN files alone are the issue. Anyone care to test that theory?

mr_s - I think all files are excluded except INF, DLL and SYS

I can confirm this bug exists even with the 1007r3 pack and the current DriverPacks BASE.
When DriverPacks BASE creates the PE plugin folders, the following files are excluded (.din, .exe, .cat, maybe others)
This is a bug, and doesn't just affect Intel.  It's how DriverPacks BASE handles the file types during PE plugin creation.

This issue I am having appears to be related, but in

      DP_LAN_wnt5_x86-32_10051\D\L\I

...there are several .din files....the filess causing me issues appear to be from the missing entries (and missing in the "DriverPacks.net\LAN\wnt5" though they are in the driver pack) -- *edit below is a patch*:

plugin\DriverPacks.net\LAN\LAN.inf -- Add the following after line [SourceDisksFiles], but before line [SourceDisksFiles.3790]

wnt5\PROUnstl.EXE=2,,1
wnt5\E1Y5132.DIN=2,,1
wnt5\e1e5132.din=2,,1
wnt5\e1k5132.din=2,,1
wnt5\e1q5132.din=2,,1
wnt5\e1r5132.din=2,,1
wnt5\e100b325.din=2,,1
wnt5\e100bnt5.din=2,,1
wnt5\e1000nt5.din=2,,1
wnt5\e1000325.din=2,,1
wnt5\fei5132.din=2,,1
wnt5\ixe5132.din=2,,1
wnt5\ixgb325.din=2,,1
wnt5\ixgb3251.din=2,,1
wnt5\ixn5132.din=2,,1

Decompress

<bart pe builder>\plugin\DriverPacks.net\BASE\DriverPacks

Copy the listed files above to...

<bart pe builder>\plugin\DriverPacks.net\LAN\wnt5

Although when I attempted to look for the drivers that I see are working in a windows environment they all show with the latest time stamps (i checked the check-sums too) when comparing them:

c:\windows\system32\Drivers\
c:\windows\system32\e100msg.dll
c:\windows\system32\e1y5132.din
c:\windows\system32\NicCo2.dll
c:\windows\system32\NicInstY.dll

They all correspond to the ones in DP_LAN_wnt5_x86-32_10051\D\L\I...

However when I slipstream to a BartPE the network card drivers fail to load.

Edit: Sorry, I missed the reply that noted *.din files were missing from the inf

A possible work around is to include .exe and .din files globally to the folder for the plugin part of it

<bart pe builder>\plugin\DriverPacks.net\LAN\wnt5

That is what we need user feedback for

I will figure out how to implement an "exception" for this driver. - Since this is not neccessary for ANY other driver I will have to probably have to write some code into BASE and crete a new exception type in the packs INI file... IDK yet

At least you have done the hardest parts You found the BUG and have provided the fix. It's all down hill from there!

Thanks for all the good feedback it makes DriverPacks better for everone!

PS For right now you have posted the workaround for all to use! Well done!

wnt5\E100B325.CAT=2,,1
wnt5\E100B325.DIN=2,,1
wnt5\E100BMSG.DLL=2,,1

So what this problem seems to be is a case of missing files.

DriverPacks BASE should detect these (and others, most likely) as required when creating the LAN BartPE plugin.

An example of this is here : http://www.911cd.net/forums//index.php?showtopic=1669

Just prior to submitting, I tested copying those 4 files to plugins/DriverPacks.net/LAN/wnt5 and adding the following to LAN.inf :

wnt5\E1000325.CAT=2,,1
wnt5\E1000325.DIN=2,,1
wnt5\E1000MSG.DLL=2,,1
wnt5\PROUNSTL.EXE=2,,1

Now BartPE detects the VirtualBox Intel NIC correctly!

I stickied this and updated your title to [BUG]

I'm having trouble integrating the LAN DriverPack into BartPE. I'm using PEBuilder 3.1.10a with DP LAN 10.04.1, and the NICs I tested are all Intel network adapters, including the ones in VirtualBox 3.0 (example: "PCI\VEN_8086&DEV_100F&SUBSYS_075015AD&REV_02\3&267A616A&0&88: Intel(R) PRO/1000 MT Network Connection")

My method of integration is as described here : http://users.telenet.be/jtdoom/basetute … lpFile.htm

PEBuilder works fine, without any errors or warnings, and I can see the various .INF and .SYS files from the DriverPack integrated into the CD ISO image.

My pebuilder/drivers/NET and pebuilder/drivers/SCSIAdapter folders are empty.

However when I boot, network adapters are not detected.