SAD ( to be renamed SoFI {Software First Installer} )

argh! too bad. I kinda liked that "SAD makes you happy." :)

talking about nature, I like using feminine words, but not as much as for computer things... /2 cents

Re:
DPsRootDel  = "false" option.  Am I understanding this correctly, the option is only if you are using a thumb drive or external drive for the location of the \D\ folder and if the option is not used all of the drivers are still installed on the machine and not removed.

ONLY if you are useing M1 (Method One) and Not useing a Read Only media
IE M1 SAD location on a thumb drive - or a network share...
without the switch the original files would be deleted from your source location.
pay no attention to this if you are not useing Method 1
- 99 out of 100 users are not useing M1
although SAD ( to be renamed SoFI {Software First Installer} ) clearly has advantages as an m1 source on an ODD since add new hardware wizard will recursively search an ODD.

Glad we have been able to make your life easier! That is why we are here!

have a great day and thanks for the kind words

In response to markstrelecki's and OverFlow's post about SAD being intended for a machine that has all of its updates a tool that I uses that might help is c't update available here http://preview.tinyurl.com/yp993m  It will download and create an iso of all of the Windows and office updates for XP, Vista, Server 2003 and multiple versions of Office.  Work great if you dont have a WSUS server. 

Again many many thanks to everyones hard work.

testing will benefit all when you tell us
1; what you did (all the steps)
2: what you expected
3: what result you had

x1;  how did you reproduce the isue?
X2; IF.. could you FIX? IF so, how did you fix the issue.

I would like you to be part of what makes us get into a structured improvement move. We are in a flux.. we are NOT fluttering.

Your testing of what is "in flux" will benefit all when you tell us
1; what you did (all the steps)
2: what you expected
3: what result you had

examples:
When you report GOOD or bad, while testing against known DriverPacks issues in drivers, the generated logs help.

If you have a niggle with the GUI or orher DriverPacks Base function and NOT a HWID conflict.. Please, PLEASE tell us what you expected to see in the interface (DriverPacks GUI) or what you had expected to see when you changed option, or as result after you ran it with your options.

for logs, we should have a FAQ.
simple; (gui in CPL for folder options) unhide all system,  and unhide system known extentions.
OR (the dark DOS screen aka cmd console)
CD\
dir /s /e /h *.log
dir /s /e /h *.ini

edit....  (forget set=) forget MsDos.

OTOH, this is too long to be in a sig and not beyond basic. I just wonder why so many do not know how to post those relevant logs.
we gonna havta have a faq?
find logs and INI by cmd or path, as shown in signatures by the DriverPacks gurus

Yeah, it's kind of the same, the option was mainly added because it was requested much and it certainly is more convenient to work from the BASE GUI seeing as we already have it.

Isn't SAD the same as making a CD/DVD/Folder and putting DPINST.exe in it???

One little comment however. How about a hyperlink pointing to driverpacks.net in the "About" screen?
Me lazy ...

Will test and overload my sun virtual machine

but why not just use DriverPacks normaly... ?