Search options (Page 29 of 159)

I've got all three graphics packs updated.  I haven't tested them yet though.
I completely reworked the two g\a1\dps_A1*.inf files and this should fix your problem.
I'll upload them this morning.  I'll update the threads in the testing area later.

Holy crap, there's another one.  I've left this in place to show what we're dealing with.  I deleted two accts today already.

[url=TinyURL.com/pqum87c]Read BEFORE you post.[/url]
This is a DriverPacks support forum.  Please post your DPs_BASE.log and full HWID list.
Please explain what you did so that we can try to replicate the problem with the DriverPacks.

There is little mention of what you did with DriverPacks to cause the problem.
[url=TinyURL.com/pqum87c]Read BEFORE you post.[/url]
This is a DriverPacks support forum.  Please post your DPs_BASE.log and HWID list.

Those are on the list of things to do for the next release.  I didn't have time to implement them in 11.11.

Those will be in for testing for 11.12 or 12.01 release.

Sure, but leave the line "set KTD=N" because that variable used further in the code.

That sounds like a BS answer to me.  They even WHQL their beta drivers so I don't understand their answer either.

Well, that's an unusual method for install.  It might work but I wouldn't recommend that way.
I still recommend that you directly integrate DriverPacks with DriverPacks BASE (method 2 is my personal favorite) with DriverPacks Finisher executed during RunOnceEx (again, my preference) and see if the problem still exists.

If my hunch is correct (disclaimer: I don't use sysprep), then when minisetup is run on the target machine it loads a ram-drive at X:\ and executes certain utilities from there to the target system.  That may be your culprit.
Of course I may be 100% wrong and someone versed in sysprep lore will prove me to be an idiot.
...moving thread to the sysprep side of the house...

Whoa, what?  So the driver that doesn't work is the one from \D\S\S15 ???
Now I'm confused.  Why would you load a driver manually that doesn't work?

Excellent first post!
Welcome to DriverPacks!

That's an odd bug.  Your HWID doesn't match any of the known "problem kids".  I'll dig around and see what I can find.
Do you know the driver version that gets loaded automatically that doesn't work?

Your HWID isn't matched to any driver in my working copy (11.11 release) except for the folder as you noted \D\S\S15

Can you test this for us?
DP_Sound_B_wnt5_x86-32_1110b1
Download:

If the existing driver is newer than the one in the Audio DriverPacks, then the existing driver will never be replaced during the SAD2 upgrade.
But is this a problem?  If the audio works, what benefit do you have by ripping out a functioning driver?

Just because a driver is newer, does not make it better.

To answer your question, follow these steps:
1) Open the device manager (type 'devmgmt.msc' at the Run box)
2) Double-click the device you want to remove.
3) Click the 'Driver' tab
4) Click the 'Uninstall' button
5) Agree to all the message boxes (Remove all files).
6) Restart.  Driver is gone.