Search options (Page 78 of 213)

did you try properly nameing the file?

What is the HWID of the device you are testing with?

tpdps here http://forum.driverpacks.net/viewforum.php?id=13  (modems included)

There is at least one way to make it faster but the tool is still alpha...
It uses a technique that extracts only drivers that will potentialy match the local machine.
this has cut time from about 12 min to around 8 min...
What can i say it takes time to search over 1000 folders of drivers...

M2 will likely be faster... since we are not putting the SAD folder on an ODD (cd or dvd are searchable from add new hardware wizard) there is no benefit to useing M1.

uploading 8.0x graphics packs now

do you mean the first few reboots during the initial install...

Or do you mean everytime the PC is booted to windows after the install?

can you provide some more details perhaps include your DPs_BASE.log? Did you use RVMI, AutoImage, nLite, hfslip or other update packs or slipstreams?

Yes I am interested in knowing how the conflict occurs... If you will be willing to help us to help you, that just rocks

DriverPacks BASE is only supposed to alter files marked as replace in the mass ini...
DriverPacks BASE is only supposed to add files not excluded with a skip tag
DriverPacks BASE will only modify files that are listed in the mass ini as "TAG" in the format TAG.sy?

since your filename ultradfg does not exist in the mass INI anywhere at all it would never be in the list for any file operations.
Only listed files are altered in any way

Well you did not state which BASE or DriverPack MassStorage version so I will assume 8.12x BASE and 9.01 Mass (latest releases)
(demerit awarded lol)

since ultradfg is not found in DriverPack MassStorage ver 9.01 there is no reason it would be altered by base...

Only files who match the ms_1_tag= line are ever altered... and only if the ms_1_exc_disableIfOS= line is not set...
Not only is that not a related file name BUT *.INF files are never touched, only *.sys references...
Hint: use examdiff on the file before and after DriverPacks... Both with and without your addon (three tests)

IDK how the two things could possably be related ??? and nothing you mentioned so far leads us to any answer.

It seems to me you probably should break the rules in this case, run your addon after DriverPacks... What happens?

Does this only happen with a particular mass storage pack... Or with any? Which ones? Which version of DriverPacks BASE are you using?

Check read before you post and update some details and try the above ideas...
IE let's see your DPs_BASE.log please

thanks for reporting.

PS what were the lines preceding and following the ultradfg.inf = 100,,,,,,_x,,3,3 line? (just a few both ways please, obviously we need before and after DriverPacks)

I don't belive this particular project is current anymore.
This thread is over two years old and the DL link is dead.

Please follow the links to BootLand for current info downloads and documentation. Tell them we said hello!.

Welcome to DriverPacks.

read the tutorial in my signature for a "how to" use the DriverPacks

Let's tag this with a [REQ]...

We need to get some of those mass storage drivers marked for ms_1_exc_disableIfOS="w2k" in the mass storage INI to get us back under the limit for win 2k.

(you can add this line to a few drivers you don't need and repack yourself to get up an running right away )

LOL...

Yes, SAD will allow you to "put a batch file to auto-start on first boot and this batch can automagically erase all drivers when finished "

Yay, We rock! (Because it IS true)

I am sure I speak for the entire DriverPacks Team when I say we are very grateful for your praise,

Thank you

The DriverPacks team

PS Welcome to the DriverPacks Forum

PSS When a machine joins a domain its SID is updated. (you are both right) So the question is do you join the domain after you deploy? if not then SID can be an issue... I use GHOST because it automagicaly sets a unique SID when you deploy .

SAD...

Run DriverPacks BASE select SAD (Stand Alone Driver-update)

Call the dp_inst_tool.cmd at any time...

You stand corrected