Morgue

Finally got a few minutes spare to myself to try the SAD2 script. Worked wonders. At least, from what I could tell within the VM. Much more preferable to run the script afterwards, and as suggested, i've integrated the basics into the boot.wim. Just to set up applications and settings in the post install.

Just uploading the error log I had from last night's driver integrate. As you can see, there's no special characters used, nor spaces. Driver_Errors.txt

Thanks. The interesting thing is, if I use the script Mr_Smartepants developed to integrate the drivers, it catches them all. The script itself is just a batch file using DISM to do the integration, and it manages to locate and integrate all the drivers without any issues. If I can provide more information for you, let me know how. And yeah, the second part of my post was aimed more at Mr_Smartepants. I should go and sign up at driverpacks and give him a PM, but I figure he's the kinda guy (like myself) to check this thread 50 times a day :icon_cool:

G'day all! Just started using this application last night and I am thoroughly impressed. A round of applause for Legolash2o. The frequency of updates, attention to detail, quick responses and extremely high level of quality is just amazing. First a note: I've read through about half of these threads and saw the sticky post regarding errors with DISM and special characters. I also remember you writing a fix (or warning I believe) to people using special characters in their drivers. It seems that in build 34, regardless of special characters, a warning will be shown to everyone when trying to integrate drivers into their release. Upon inspection, it seems to have thrown out my entire driver folder hierarchy as erroneous (I don't use spaces or special characters. C:\Drivers\x64\G_A\Nvidia\1 etc). Despite the warning, it still seems to find and process all my drivers. Currently integrating all of the x64 win 7 drivers on driverpacks.net (672). The driver integration finally finished. At the end of the installation, there was an error and 60 drivers did not integrate. Of the 6 that were shown not to integrate, creative had 2 entries. This leads me to a question, i've already tried to integrate the drivers into a previous image that I've fiddled with, which installs correctly in my VM, however I've noticed I've got a 12 gig DriverStore\FileRepository folder in my image. Brings my entire install up to 22.9 gig. Is there any way I could reduce this folder's size? I'd really like to be able to integrate the entirety of the driverpacks into my disk (Iso image is only 4gig so far, quite acceptable) and have it auto detect the drivers during the windows install (or first boot). I've read through Mr_Smartepants posts at driverpacks.net, saw the manual integration thread (my first integration attempt, pc is currently processing the an AIO driver integration now), also saw the SAD2 script, perhaps that is what I'm after, if I understand the post correctly. Any help is gratefully appreciated. Interesting tidbit: My pc fell asleep halfway through this driver integration. It shouldn't have fallen asleep, but it seems DISM doesn't inform windows that it's currently busy and processing. Driver integration resumed perfectly when it woke back up. Wonderful!