that is a great idea...

Yes the QSC saves you from haveing to cab the drivers more than once
the first time you cab the drivers DriverPacks BASE caches them for the next time.
So yes it will take Much Longer on the first run for M1.
On any run after that it will not have to cab the drivers again - it simply copies them.
IE Nine minutes first run... Two minutes second third or fourth runs... smile

This is normal and by design, and kinda cool big_smile...
I see that you already figured this out on your own. I will mark this as solved.

Have a great day and welcome to DriverPacks

Jeff

post the HWIDs please...

the only diferences between 8.12 thru 8.12.4 were language updates...

and yes SAD M1 is a superior solution...

Were you going to update your post above?

jsut use the html source...

thanks a million!

the PNF's that are created during the process are cached versions of the original inf's but are unsigned. PNF's are supposed to accelerate driver installations but they fail because they are unsigned... (i don't know why you would have to ask MS why they created something that doesn't work...) I can tell you it worked better before SP3

2,507

(107 replies, posted in 3rd Party DriverPacks)

Every once in a great while we get lucky enough to have him stop by for us for a minute..(mock rant).. LOL

Very cool... thanks for the idea...

You da man!

I have never gotten enough info/feedback to properly add this fix to base...
IE i still don't know if this fix is also required for 2k3...

2,509

(17 replies, posted in Software)

That is because you are using KTD. KTD uses MakePNF which is supposed to cache the INFs to speed finding drivers but instead it creates duplicate unsigned INTs that are referred to their originals... although PNFs are a MS convention PNFs don't work and is further aggravated by XP SP3
Don't use KTD it never worked well and never used the finisher (which is key to installing MANY drivers)
that is why we wrote SAD...

Your problems are a result of KTD... Don't use KTD, it never worked well anyway.

You don't need KTD functionality.
DP_Chipset= "yes"
DP_CPU= "yes"
DP_LAN= "yes"
DP_MassStorage= "yes"

The drivers you selected for KTD are never going to change for the life of the PC since they are on the MB...
The idea behind KTD is like; you may add a modem months later to the machine and it will have the 6 month old driver available.
For devices that can not be upgraded you are just wasting time and space. don't do it... and your issue is solved.

if you have a need for KTD funtionality (although i can not think of a single good reason for KTD) then SAD is the solution that has replaced KTD...

well we wrote them in HTML... wink

Wow that is very cool...

go ahead and post it here! (update your first post even)
that will get a sticky for sure!

2,513

(4 replies, posted in Vista-Tool)

Um... i was never a fan of Vista and Muiz picked up the ball and ran with it...
It does work and is "ready" it may not have the polish that DriverPacks BASE does but neither does vista tongue.
Yes adding the vista DriverPacks is worth doing! and the packs for vista eachhave thier own frum wher you can grab them, Bâshrat the Sneaky is in process of adding support for the vista packs to the website as we speak wink

as with nLite and BASE don't add drivers with both...

We are streched pretty thin on man power... sorry about the state of our documentation.

Always nice to have a fan! now if we only had two... wink

In as much as i am really warming up to Win7 I will definately support that for DriverPacks BASE and probably as a result of that i will accidentally add BASE support for vista too...


But to your main question yes ther are packs check out each of the vista forums for links to the packs be sure to thank Muiz and confirm that it is actually ready wink

Welcome...

can you use the tool in my signature to post your hardware ID's (HWIDs tool)

Please add code tags to your post... http://forum.driverpacks.net/help.php#bbcode

Thanks for including your logs. It really helps us to support you!



NM, added code tags for you!

OH.... it's one of those?

Thanks for reposting in the correct forum and updateding the details we will look into it

Welcome back!

off topic post containing no useful info deleted.
(delete, perhaps you heard of it wink)

Just a link to a google search to a list of warez...
Is that the best you have in the way of rhetoric.

Look if you are going to defend the Alamo... you're going to have to dig deep.

yeah adding an exception for a KB is no problem its designed to9 handle that already much like we did with kb888111

PapaGrief is refering to this
http://ubcd4win.com/forum/index.php?s=3 … entry69497


no reason to attack mr_smartepants he was only trying to help after all,
and you did report bogus info (You reported to us the version of autoit that DriverPacks BASE was compiled with. big_smile)
and provided nothing in the way of details either here or at ubcd4win as to your process, this makes it hard to help.

And yes you do need help....!

Furthurmore this Glitch you are reporting is actually user error.
I can only guess, but I think you made more than one error.
(please take a moment to read "Read BEFORE you post")

I Bet you did not read the BartPE tutorial either... did you?
It's in my signature, and included with DriverPacks BASE,
and avaialble from the help button on the plugins page from PEBuilder
Because if you had read the tutorial and read before you post... then we would not be having this discussion.

Sorry about your attitude problem,
but before you report a Glitch you should at least RTFM
In the case of DriverPacks BartPE, the manual is only one page long.
Had you read that one page you would not be reporting an issue.

the pages that load after the location of platform page depend on your selections on the location / platform page.
If you do not make a valid selection - then there are no other pages to show you...
And there will not be any other pages until you do make valid selections on the location page.
The pages that follow the location page can't be properly determined until after you provide valid input for the platform and the location fields on that page wink (clearly you did not read the help at the bottom of that page either)
so to sumarize you cant select packs until after you select a valid platform and location.

I am also going to guess you did not read the first instruction that applies to you in the tutorial

Extract / install the DriverPacks Base program to a folder that IS NOT in your plugin folder - IE C:\DPsBase\
Again if you had taken only one minute to read it then you would not have attacked mr_smartepants...
or reported a bogus issue that is actually user error... annouce you don't need help when obviously you do...
additionaly we are not mind readers we don't know what you did - if you don't say... IE the version # you used
then be snide to us about the whole thing

Yes you do need help... because your so lost that you don't even realize that you are in fact lost.

Silly you needs to be nice to the people who are helping you for free... hmm
Oops, make that you should be sorry for wasting our time... and being rude about it too

2,520

(88 replies, posted in Feature Requests)

they are out as is the Vista tool... Thanks to Muiz...

please take a moment to look around...

i was just re-reading this

Won't the mass storage controllers work just my setting the HDD controller to standard IDE before you shutdown
then when the system boots it will use txtsetup.sif to install the correct txtmode drivers.

If the mass storage drivers were available to minisetup then they would be replaced by the drivers in the mass pack.
so all you need to do is have the mass storage pack extracted somewhere and put the folders in the devpath entry.
except for some of the known issues with certain hardware requireing registry entries that woud be 90% effective and OSP more like 98% ?

well my routine is much more exacting, as is kickarses.

that is why it is hard to follow. it is actually intuitive. it first identifiys the manufacturers supported then finds each of the manufacturers individual platforms (2k, XP, 2k3, x64) "supported section" line by line. this avoids misreads you might encounter by accidentaly importing hwids that are ;disabled or are in a section that is actually an "exclusion" section wink. this is Tricky because many of the lines use variable substitutions and dealing with variable substitutions in an inf from a program is kinda tricky wink.

the output of mine has the advantage that the hwids for each of our supported platforms are separated so that only the correct hwids lists (based on platform IE XP,win2k, ect...) are applied to the target machine wink. (IE we dont need to extract folders based on HWID matches that are "win2k only drivers" when we are installing XP - ect...)

I think I have created the tool you that you set out to create... Please let me know if i have not wink
IE
   If my tool works why does it matter if the temp file used is in a different format???
    Or tell me why the format is important to you and what that format is / needs to be...
      are you trying to achive KTD or some similar function... talk to me...
      I'm sure it's easily doable if only i know what it is we're doing tongue
and yes if it works I'll add it and credit you for motivateing me wink

- I may never know if it works... wink tongue big_smile

PS Ithink mine works for 2k xp and 2k3 too...

2,523

(73 replies, posted in Vista / 7 DriverPack Mass Storage)

That was very diplomatic Fragbert...
I certainly hope it is well recieved by muiz.
He should be able to realize you are only trying to be helpful in the nicest possable way. big_smile

please "read before you post" in my signature...

Update your request with description of your process RVM/nLite/hfslip, DPs_BASE.log and hwids.

Look at the Nvidia.ins file wink

did you ever try my tool?