if you have time check to see if there is a newer driver for that device... If so we can update the pack and see if that fixes it!
be sure to test it and make sure it works or no sense in adding it to the pack

its 2 different hardware devices though. Sigmatel and Realtek HD Audio. I wonder if anyone else is able to test/replicate

Bigfoot made a suggestion in post 12...
you could use Vernalex Sysprep Driver scanner to add it to the sysprep OemPnPDriversPath and see if that works

if you have time check to see if there is a newer driver for that device... If so we can update the pack and see if that fixes it!
be sure to test it and make sure it works or no sense in adding it to the pack

Is this likely to be a problem with SAD or the driver pack itself? I have a work around, but I'd prefer that i didn't have to (because scripting a reboot after the "automagic" driver install after a devcon rescan is a pita).

Can't find any documentation on this... but it just may be the solution I have been searching for... the 16k limit would fit with the issues reported and explain a lot of the problems we have been having with too many tpdps being added... We suspected we had hit some sort of limit but most documentation led us/me to belive the cap was higher than 16k. Any clues as to how to implement pointing to a file and what the format of the file would be? (A binary format I must assume, but that is not specific enough to generate one, nor specificaly how to indicate it in the registry. ) Typical MS merry go round it documented somwhere but good luck finding it (i thought bing was supposed to be the cure for that ) I've tried every keyword search i can think of... with three different search engines and the built in MS search. I jsut need to figure out what the correct question is LOL

1. Dell D630 Intel 965 Express driver installs, but leaves a second entry under display adapters - "Update Driver automagically" fixes this.
2. Acer TM6493 laptop has an "!" on its Built-in IR Port.

It also might sort my sound problems out (fingers crossed), I also have a problem with Intel Mass Storage not working right (BSOD on boot in AHCI mode) - trying DriverPack MS Nightly.

You can still use a script with devcon to remove and reinstall a particular device .

the answer to why it failed is / will be contained in setupapi.log... I haven't had a chance to review the one you submitted yet.

alternately you could try running SAD twice... IE sometimes certain drivers will depend on others, hda depends on hdabus (hdabus=KB888111), hdabus depends on pcibus, no hdabus then no hda this would require two / three passes Test: run SAD reboot run SAD agian... does it work now?

Twice = no go. (specifically run SAD, reboot, run SAD again).

Will try adding chipset to OEMPNPDriversPath, then reimaging.

Uninstall, Scan and then Windows "automagics" it works fine however (no online connectivity, i'd assume its pulling it from the driver cache after SAD puts it there), no reboot required.

http://users.on.net/~randomtask/DPsFnshr-tm6493-2.log
http://users.on.net/~randomtask/DPINST-tm6493-2.LOG
http://users.on.net/~randomtask/setupapi-tm6493-2.log

*edit*

Same again with OEMPNPDrivers for Chipset.

The driver works - I just think its installing wrong or something.

My impression was the limit of a DevicePath reg entry was the limit of any single reg entry one megabyte?
We have been having an issue with no drivers being installed when too many 3rd party DriverPack were used...
Can you show me where you found it documented that the devpath limit was 64k? that would really help us!

Source was here - http://blog.remyservices.net/2007/09/28 … -image-pc/

further reading tells me that its not quite that long...

http://support.microsoft.com/kb/256986

Either way its more than 4096/2048. - my programmer friend tells me its 16k, unlimited if you point to a file somewhere (although i am unsure if you can do that for this particular key).

I also found these tools helpful - http://technet.microsoft.com/en-au/maga … light.aspx - specifically PNPPath.vbs (which can apply both the registry and an .inf file).

Thanks, will look into this

My impression was the limit of a DevicePath reg entry was the limit of any single reg entry one megabyte?
We have been having an issue with no drivers being installed when too many 3rd party DriverPack were used...
Can you show me where you found it documented that the devpath limit was 64k? that would really help us!

Thanks for the feedback, looking forward to more

Jeff

OEMPNPDriversPath has a limit of 4096 in normal windows installation, and half that in SysPrep. If you exceed a path length of 2048 in sysprep then either nothing is installed or only the first 2048, usually nothing .

I suggest you include chipset in  OEMPNPDriversPath, that may cure your issue.

What about using the reg entry? HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath

My understanding was you were allowed 64,000 there? (I tried both)

I looked at that, I couldn't really find much in the way of a tutorial (or even a base idea). Is the idea you build an image to be sysprepped, then shutdown, boot BartPE with OLSP and do it that way?  Any further info on a good starting point with OLSP would be nice.

Will test this before doing below.

Will try doing this next run (S.A.D is missing a few things from our images, trying to add them via OEMPNPDriversPath - if that works, then I'll try add chipset).

Thanks for the help.