1 Reply by Thinkster

(11 replies, posted in Feedback and Support - DriverPacks Base)

Yes, I am using KTD.   Is there a good reason I shouldn't use it?   I figured that if someone ends up replacing a network card or sound card, etc. that it will be able
to utilize the drivers from the driver pack that way.

Also, Just verifying on my Winnt.sif file and the Driver Signing stuff is set to ignore, but the warnings still pop up during the 'KTD/Driver Pack cleanup' routine

[Unattended]
UnattendMode=FullUnattended
UnattendSwitch="No"
OemSkipEula="Yes"
FileSystem = LeaveAlone
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
Hibernation="No"
OemPreinstall=Yes
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

Go to forum: Feedback and Support - DriverPacks Base

2 Reply by Thinkster

(11 replies, posted in Feedback and Support - DriverPacks Base)

I'm getting the same problem.  With previous versions of Driver Packs,  there were only path problems where it couldn't find certain files and it would beep maybe 12-20 times and of course I'd have to click OK each time.  Now,  it doesn't complain about paths, but complains that it has not Passed Microsoft Windows blah blah blah and it moves on but ends up beeping about 300-400 times which can get annoying.  Is there anyway to force windows to ignore that it has not passed therefor eliminating the beeps?

Go to forum: Feedback and Support - DriverPacks Base

3 Reply by Thinkster

(2 replies, posted in Feedback and Support - DriverPacks Base)

Yes, I was using 6.06.1
unfortunately I don't have the original svcpack.in_ anymore.   As for the HWID of the sound card,
I will try to post that next time I fire up that test machine...

Go to forum: Feedback and Support - DriverPacks Base

4 Topic by Thinkster

(2 replies, posted in Feedback and Support - DriverPacks Base)

OK, Tried the latest version of Driver Base & Drivers and although I like the GUI,
it does not seem to work like before.    I selected Chipset, LAN, Sound A & B only and attempted to
slipstream.  The first time it got to a point and crashed with an error message "Could not Extract \I386\svcpack.in_"
So I thought, why is it trying to mess with that file as that's a list of Service Packs to install and shouldn't be related to drivers!  So I resolved that by taking a svcpack.in_ from an older build and putting that in place.   Well then I tried slipstreaming and it worked without error, but it deleted all the data in the svcpack.ini file, leaving only one KB83667 or something like that.
So I burned my build and tested everything.   Well, the PC has a Sound Blaster PCI128 and it failed to install the driver for that.  I found the folder named D on the C: drive and then went to the S Folder, then the CR Folder and windows was able to find the driver it needed for the sound card.  But it didn't install automatically through the Driver Packs so I figured something must be wrong. 
And then I though it was supposed to do something after first login, but it doesn't seem like it did because it left all it's baggage on the C: drive and didn't clean up anything.

Oh well, guess I gotta wait till the bugs are fixed and I was looking forward to this version too..

Go to forum: Feedback and Support - DriverPacks Base