Search options (Page 90 of 213)

um... Wow that sure is a hard way to do it...
If it works great, but not the way most of our users or I would do it.

Did you find your SAD folder? ...

#1 Installing XP SP2 then updating to sp3 first thing is sloppy.
     It creates an unnecessary mess and burns disc space needlessly.
     Slipstream SP3 to your source. Minimum... it would not hurt to add patches you need too.
     ...Remember you said "basic as possible" <IE clean>... you shot yourself in the foot right out of the chute
     The Result is a Lean Mean Processing Machine
     (None of the uninstaller reg entries, files & BS - You're not going to uninstall them anyway)

#2a Use DriverPacks BASE to add the mass storage text mode drivers (Only) to your source.
     - By doing this you don't need -bsmd or the mass storage section in your sysprep.ini... the mass storage drivers are already included as if they were provided by MS themselves. All you need to do is set the mass controller to standard IDE before you do that last shutdown... then the new controller will automatically be supported for text mode / PE / Mini setup. (much easier than all that garbage you went through)

#2b Use Offline SysPrep by Galepo to add your mass drivers.

Create a SAD M2 folder copy it to the image
IE "%SystemRoot%\Options\Drivers"
the drivers will remain at "%SystemRoot%\Options\Drivers" for anyone who needs them...
They can be extracted if needed...
OR "%SystemRoot%\Options\Drivers\DP_Inst_Tool.cmd may be run at any time (The prefered method of installing updateing drivers not to mention that it saves you 2 gig of disk space)

I like the fact you pre-extract the drivers to thier location for mini-setup.
Do devpath, make sure the devpath entry starts with SystemRoot\inf (i vaguely remember a bug where it had been ommited)
DON'T Make PNFs -=- (They only result in popup h*ll and possibly thousands of bleeps. Since every single pnf will fail driversigning (and unsigned drivers won't install anyway) - annoying and a waste of time the original signed INFs are readily available and are vastly prefered over their pnf cached versions...)

by simply adding the D\ folder structure to the devicepath reg entry 80% of drivers will be found and installed...
(KTD simply updates the path after the files have been moved. [well it also runs makepnf which is BAD])
( after Setup.exe has already run it is very very ineffective - and a good percentage will fail without the finisher running after a driver is installed (Graphics for example))
The ONLY ways to get the remaining drivers installed are to either run the DriverPacks finisher, or run the original installer program from the vendor.

See how far you get with those clues... and report back

HINT: you can use presetup.cmd to stage your drivers, finisher and related files and it also runs devpath. Do this right before you reseal and set the IDE controller to standard.  The script is already written and works perfect

Slipstream a source with DriverPacks (all packs you need) and then just copy the OEM folder to the root of any local disc... presetup will then be able to find it and stage everything for you . Presetup.cmd will be in teh I386 folder of a M2 slipstreamed source, created the same time as the OEM folder.

can you please try this nightly... here.

please report your results similar to above.

Welcome to DriverPacks. That is an excellent first post sir! Wonderful details...

did you download last year? try the newer version please...

Can you post your DPs_BASE.log?

I googled...but failed to connect the dots... and did not recognize the name...
i tend to lag a little in the AM as a rule anyway

well then you are actually talking about true KTD... 
I need to understand why you want KTD to be able to give you the best answer...
The solution may be different based on your intent. 
  IE there is no reason to EVER KTD for chipset drivers.
  (if you put in a new MB (requiring a chipset driver) your going to reimage anyway because of HAL issues)
 
Show me your DPs_BASE.log and i will tell you where your SAD folder is...
Hint is was the location you used when you ran SAD. If you did not browse to a location then it created \DriverPacks.net\ at the root of the HDD you ran DriverPacks BASE from. (IE C:\DriverPacks.net\)

you will not end up with an INI you will end up with a folder... that contains all that you need.

Run DriverPacks.net\DP_Inst_Tool.cmd  ANY  TIME  YOU  LIKE...

runonceex guirunonce manually - 6 months after the install
you could put it on a memory stick and run it from there... if you were upgrading a video card for example.

there are very very very few situations where KTD is cool - I have seen some... but its rare.
the reason is hardware seldom changes after deployment.
If it does, then a Tech is going to be there installing it, and he can use a current copy of the packs tu update teh drivers by ODD or mem stick, USB HDD, Network repository... wherever teh current copy is. hardware does not add itself...

give me some details and we will give you the solution.
Jaak used to always say "Help us to help you."

it is possable... it is also difficult...
And requires hacking system files, We don't support methods that break licensing.

it is also likely that your older dell may not support booting from a USB HDD...

Again MSFN is the source of a wealth of info on topics like that one...
you may also have some luck at UBCD4Win.com on this subject.

You really can't spare 20 dollars for a burner?

KTD does not do exactly what you think it does...

KTD just leaves the drivers taking up space on your HDD... that is not what you want...
you want the drivers installed... (don't you?)
After the machine is deployed you don't need them anymore do you? (burning Gigabytes of HDD space)
So really you don't wish to "Keep The Drivers" (KTD)
you just want to borrow them till the machine is deployed

You want to install the drivers... that is what SAD does.

DriverPacks BASE creates the SAD folder... run BASE select SAD...

more related posts
http://forum.driverpacks.net/viewtopic. … 612#p31612
http://forum.driverpacks.net/viewtopic. … 078#p31078

take a look at the sticky in the testing team forum " How to update the Driver Packs by JakeLD "

short answer is to use excel to import your csv... and sort by columb

Read http://forum.driverpacks.net/viewtopic.php?pid=4#p4  (read BEFORE you post)

provide DPs_BASE.log,
and HWID's (tool below)
what version and Service Pack level of XP   "IE XP Home SP1"

What device was not installed when you used the DriverPacks slipstreamed source to install the viao?
(that would have been the picture to post above)

please see definition #1

http://www.google.com/search?hl=en& … p;ct=title

"Warez" refers primarily to copyrighted works traded in violation of copyright law. The term generally refers to illegal releases by organized ...

IE if you put an OS available for download... you have "traded in violation of copyright law." and it is therefore Warez... As stated.

Look it up yourself

I can search for DriverPacks and get more than 3 million hits
IE Results 1 - 10 of about 11,400,000 for 'driver packs'. (0.34 seconds)

better yet Windows 98
Results 1 - 10 of about 54,100,000 for 'windows 98'. (0.32 seconds)

care to try DOS?
Results 1 - 10 of about 782,000,000 for DOS. (0.29 seconds)

we get three million downloads in a couple of days LOL

YOu might as well post a BIG SIGN that says NOBODY is interested in it
or we could say 780 million more people care about DOS than care about XP-64
or fifty million more people would like to see DriverPacks for win98 .. lol

http://forum.driverpacks.net/viewtopic. … 359#p31359

marked solved...

Have a great day, and thanks for posting!

Here i don´t understand why you write the .inf file since it has executed before during the installation of windows

+inf is used by the finisher it reades the HWIDS in th inf and looks to see if the HWIDS in that inf are present in the machine.

Well done...