Search options (Page 91 of 213)

yes it gave me the answer...

you did not add KB888111 which is required for HD sound.

that KB is included with sp3 but not with sp2...

Problem Solved..

I just needed the question i originaly asked to be answered  "OS and ServicePack?"
you only half answered the question... a question that was clear and consise

We have been told by several users that XP drivers are often bundled with the Recovery / Restore discs from the OEM...
Might be worth a look see...

Please let us know when / where you find it...

Might be worth looking at Muiz's Vista 3rd party DriverPack too... sometimes Vista drivers will also include XP compatability.

http://forum.driverpacks.net/viewtopic.php?pid=31245
under guidelines...

We support our application and the packs...
(we don't find drivers for people - how could we, since we likely don't have the hardware to test any particular driver on)

If you have USED the DriverPacks and discover a driver is missing...
(since you did not include a DPs_BASE.log or pack/ver info i assume you did not use DriverPacks even though it is obvious you have been here a while )
YOU may be able to find that driver and then ask us to add it to our packs, provide us a link to the driver you have tested an know works...

I see that you did include your HWIDs... Thank you!   That is very helpful.

Only after you discover that your driver is not included in the existing DriverPacks then request we add a driver you know will work for you (and presumably everyone else too).

Be sure to look at all of our 3rd party DriverPack too...

ven 1033 is NEC perhaps that is a helpful clue...

don't ever run makePNF...
   Clear enough

PNF's are a cached copy of inf contents. however the PNFs are unsigned.
Any driver referenced in a PNF most likely WILL NOT be used, since PNFs are unsigned.
PNFs are meant to speed up driver location but they don't...
PNFs don't work if you want to know why ask MS... But i can tell you for a fact the PNF method fails...

It is very likely that your sounddrivers failed in your other post BECAUSE you DID use makePNF
They might also have failed as a result of KB888111 since you ddi not report your OS or version in that post, I can't be certain.

Woo Hoo!

Thanks so much for helping us to help you. It truely makes DriverPacks better for everyone!

Your hard work and time invested is greatly apprecieated.

Welcome again to DriverPacks, we are glad your here!

Jeff
DriverPacks admin.

excellent details... a very nice post sir!

Since webcam is a third party pack you could have added the driver yourself, tested it and resubmitted the pack.
a reg entry can be handled quite easily by the DriverPacks finisher... that is what it is for

if you have access to that machine again just let me know and i will show you how to add / test it

Thanks again, most excellent details

Jeff

the tutorial is several years old it is more of an outline than anything.
the md5s are on each download page... (get to them from the "overview" page)
auto md5 checks roll out with the new site (coming soon).

M1 is considered obsolete. (yeah you guessed it already)
re: The time utilized it in extracting all the drivers then Cab compressing them.
If you turned QSC = ON then the Cabs are Cached. 
You won't then have to wait 9 hours for a Second (or third) slipstream
they would simply be copied from the Quick Stream Cache on successive runs.
The M1 process with the current set of main packs requires

370MB (Packs) + 2.2GB (extracted) + 1G (QSC) [for one set of 10 packs] + 1Gig (destination) =
puts you in the vicinity of 5 gig so I thought I should make sure we had at least that much.
That is about 10% of your reported free space

the better approack to this issue is to use the SAD feature of DriverPacks.

By running the DP_Inst_Tool.cmd file from a M2 slipstreamed disk
a local machines Drivers will be automaticaly updated.
and it uses less than 400 MB on lyour disc
instead of over 1 Gig.
DP_Inst_Tool also works with an M1 source

An M2 slipstream takes about 1 minute on your machine (9 min with an aqgressive AV program)
An M1 slipstream takes about the same amount of time on your machine - AFTER the first run -- if QSC is on.

KTD is rarely useful, if at all. If you are adding new hardware just run SAD at that time, using the most recent drivers

let us know how your doing - thanks for reporting

How much free space do you have on your H: drive?

did you verify the MD5 checksums or file size on your downloads?

Why have you chosen M1 and KTD?

Welcome to DriverPacks. Wonderful details for a first time post!

which pack are you having trouble with?

Updated
thank you for pointing it out.

DriverPacks does not support network isntalls or any install taht is winnt32.exe based...

use AutoImage by RogueSpear to integrate DriverPacks into a network (RIS) installation

does this error still occur if the chipset plugin is disabled?