http://forum.driverpacks.net/viewtopic. … 159#p20159]]>
If i need to write some "codes" to make .bat files (I saw some ware), pls post a template where we can change the basic parameters & use with it.
I have read how to use "DP base" software & having bit of a understand about it. but not the advance steps.
(Sorry for my English & grammar)
]]>OverFlow wrote:I am beginning to belive we have exceeded the max size allowed for a registry entry in windows XP...
working on verifying this now... (I belive the max size for a single reg entry is one megabyte)
Is there anything more I can do to help confirm this is the issue?
I've now figured out what SAD is.
I've been using DriverPacks for a long time, but I run it from the command line, so I've only ever noticed the options in the default comments of the DPs_BASE.ini. Perhaps a future base release can update those comments for dumb people like me to include mention of SAD as an option?
So going on the suggestion of SAD for 3rd Party, is there any thoughts of including that automation as an option in the BASE so that running it once will both integrate the main packs and SAD the other packs (perhaps setting SAD to run automatically after the finisher)?
Sure. We can do that.
Let's make sure we are correct about the path size being the issue...
Try implementing everything except HID pack.... I believe the issues lie within that pack.
Skipping or including HID doesn't seem to make the difference for me. It really does seem to track to the quantity of drivers, not any specific pack.
]]>I am beginning to belive we have exceeded the max size allowed for a registry entry in windows XP...
working on verifying this now... (I belive the max size for a single reg entry is one megabyte)
Is there anything more I can do to help confirm this is the issue?
I've now figured out what SAD is. I've been using DriverPacks for a long time, but I run it from the command line, so I've only ever noticed the options in the default comments of the DPs_BASE.ini. Perhaps a future base release can update those comments for dumb people like me to include mention of SAD as an option?
So going on the suggestion of SAD for 3rd Party, is there any thoughts of including that automation as an option in the BASE so that running it once will both integrate the main packs and SAD the other packs (perhaps setting SAD to run automatically after the finisher)?
]]>What is "SAD"? I've been thinking I need to hack DP_Install_Tool.cmd to achieve this. Is there a better way?
]]>As the 3rd party packs are less used or regulated adding them as a second stage is a good idea. This would effect a smaller number of users.
That's my 2 cents worth.
Great idea from predator2003
Stu
]]>I think what happens is;
1- We try to add a devpath entry over 1MB
2- The 'add reg' fails and 'nothing' is put in as the path value, IE the devpath reg value is blank, empty, "", Null.
Since no device path is set then windows setup only installs the included windows drivers... continueing normaly
(except none of the DriverPacks have been searched)this can be tested by extracting a set of packs that is known to fail...
1- Manually run devpath on the extracted packs
2- Checking the registry
why not simply implentanting a 2 step Driverpack Installation into Base
First Step: extracts all DP's but installs only MainDP's (only MainDP's Paths into Registry)
Second Step: after setup, before finisher, execute all 3rdDP's?So we can save a lot of Space in the Reg for the expanding MainDP's.
Sorry if it's a stupid idea ;-)
that can be done too...
use DriverPacks BASE for main packs and call SAD for the 3rd party DriverPacks...
However i wish to know if my postulate is correct first
PS no it is not a stupid idea. It is an excellent idea
.
Please tell me if my postulate is correct using the method described above (if you have a moment).
Jeff
]]>So that leads to the obvious question, is there a way around that limit?
]]>working on verifying this now... (I belive the max size for a single reg entry is one megabyte)
]]>Where I'm at currently, the following works:
All BASE packages plus the following 3rd Party packs:
DP_LCD_wnt5_x86-32_810.7z
DP_Misc_wnt5_x86-32_90322.7z
DP_Modem_wnt5_x86-32_90805.7z
DP_SmartCardReader_wnt5_x86-32_80228.7z
DP_Graphics_A_PhysX_wnt5_x86-32_906.7z
Adding more 3rd Party packs then this seems to cause problems, but I'm still too early in my investigation to blame another pack. I'll report back when I have more info.
]]>@mr_smartepants: are you saying I can add 3rd party driverpacks without re-running DPs_BASE?
Yes! 
What you're doing is fine. But once you have DriverPacks integrated, you can drag/drop DriverPacks to/from the OEM folder and retest. The only exception to this is dpms, you MUST re-run DriverPacks BASE to integrate a different version of dpms into your source. The other DriverPacks don't require any special handling other than drag/drop (and rename to 8.3 filenames).
Easy!
]]>@mr_smartepants: are you saying I can add 3rd party driverpacks without re-running DPs_BASE?
Well, I found that I could re-run DPs_BASE having it add the 8 packs above 1 by 1 and everything kept working (I assume each time it uninstalled all the driverpacks and started over). Then I went and added the HID and printer packs together...failure. Then I tried each alone...failure. Then I removed both...failure (which had succeeded before). So either I was sloppy and didn't do what I thought I was doing, or this process has some error.
To eliminate (or reduce) human error, I'm starting the process over. I have a new clean install with just the non-3rd party packs...success. So now I'm going to keep a copy of the last working install, so I don't have to remove 3rd party packs. I'll report how that goes.
]]>