Search options (Page 8 of 213)

That is how I do it that is how I tell everyone to do it. Run DriverPacks BASE and add DriverPacks to a COPY of your final image. If you want to add DriverPacks again make another copy of your final add it to that. Big GOLD STAR and two points awarded to botus for good form on our forum.

I would like to say at this point that the last line of your statement is not entirely accurate.
IF you add DriverPacks LAST (note the big if and the big last)
AND IF you have NOT changed the image. (AT ALL)
THEN you have two, count them two, One...Two. Two options !
Option one. Remove DriverPacks. Run DriverPacks BASE on the source with no packs selected. Poof, it's gone.
Option two. Update DriverPacks. Run DriverPacks BASE on the source with updated packs selected. (it's removed first, then updated )

Special note... If those "if"s are not met... and changes were made after DriverPacks was added. It makes pea soup out of your core windows installation files. you were working on a copy right?

Extra special note: Windows does not run on pea soup alone.

http://driverpacks.net/driverpacks/wind … ss-storage

also give me the same... Emailing Wim now (AKA Bâshrat the Sneaky)

Yes we can add missing torrent files but I am having trouble remembering how. I also have a very impressive (read; allmost every pack ever) archive of DriverPacks if needed

Found my notes, i can refresh files if anyone wants me to.

replace chipset and CPU with chipset.
replace any other pack you like.
Don't mess with Mass storage unless you want to recreate the disc.

TEST that much... Does it work?

Forget SAD, ERASE ERASE ERASE... SAD stands for Stand Alone, you are not doing stand alone you are doing an install, totally different. doesn't apply. doesn't matter. is not a factor. Unrelated. horse of a different color. Apples and oranges. Cart before the horse. dissimilar.
it's either or. A) you are doing an install OR B) you are using SAD on a running machine.
It can't be both, you are doing a windows install... SAD does not do windows install.
SAD is for installing drivers when you are NOT DOING AN INSTALL. Thus the name Stand Alone Driver install It doesn't require windows setup to work... It can STAND ALONE.
there is no program to update during an install, since there is no program. the program is windows setup and it's included with windows.

Quit trying to make something so simple seem hard. It's not. Wim and I wrote this stuff to be super easy for an entry level tech or advanced user, and it is. You are WAY overthinking this.

ONE step at a time. just update the existing packs and test. and report here

"Just Do It"
Nike

Where did you get this install image?

click on search at top of page. enter "nightlies" as the search term and "subject only" as where to search, all forums as the scope. - BAM... list of public nightlies. Sorted by date, most recent on top.

PS if you ask the same question again for the fourth time i am going to make fun of you. I have answered your question in detail four times now. the answer is not going to change even if you ask again a thousand times.

@techdud Way over his head dude... baby steps

yes, chipset drivers should only be for on the motherboard hardware .

Tech!! Good to see you... thought you got sucked into a black hole or something

i tested two of the listed packs, and the new dll was not required. techdud left them as they should be packed for DriverPacks BASE XP slipstream. Try it just replacing the packs first. (except mass storage, mass storage must be slipstreamed with DriverPacks BASE)

yes if you want to be able to support any video card, even really really old ones then add the 3rd party DriverPack.

All of those packs require SAD3??? I don't think so. What did i miss?

edit.....

did Techdud pack them with newer 7zip?... ack!

See this topic,

http://forum.driverpacks.net/viewtopic.php?id=5928

if he did we simply update the DLL on your disc, no problem.

[GUIRunOnce]
%SystemDrive%\Dp_Install_Tool.cmd

is the short answer... BUT what NT5 packs "require" SAD3???
Related help: http://unattended.msfn.org/unattended.xp/view/web/18/

this is going to require some detailed / specific instructions from me to make work...

IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.

There will be issues with the GUIRunOnce listed above... related to timing
http://unattended.msfn.org/unattended.xp/view/web/31/
Guirunonce runs AFTER user logon as that user, RunOnceEx runs PRIOR to user logon. If AutoLogon is enabled they will seem to run at the same time . We will not be able to run commands after a command that requires / forces a reboot, the rest won't run or will be ended while running . I have similar requirements for my UAXP install and have working scripts .

again vague, no details or examples, no logs, no HWIDs, no drivers mentioned, no OS version (SP3, MCE, Pro) no description of your process or environment or application. is this one PC or many, how many. During install, post install. is this a machine you are attempting to repair?

so here is an answer befitting your question.

yes you can install some (not all, not even most, just some... a few, ... depending) drivers with no user input, as described in my last post.

NO you CAN'T make a windows install that you can just plug anything you want into it and it won't ask for a driver. NO you must do something (driver install like SAD) post install of most core hardware.

pre - during install
1=If driverpacks has been added to your install media and you install clean you won't see any driver prompts. .

post install
1-extend windows native support KTD only works with very simple drivers, IE monitor drivers. It will FAIL with any driver that requires an installer (video), and will fail with most drivers that are more than a simple INF/SYS file arrangment

2-Run SAD after hardware upgrade

or stop wasting my time and ask a question with a specific problem
(The specific OS, the specific device and it's HWID, a link to the driver for that device, the versions of everything and a description of how to duplicate the issue. I think that last one you got half right)

I could ask you "I have a truck that gets ten miles to the gallon, can you tell me how much gas is in the tank?"
you could probably guess that it's not much, but telling me "Not Much" isn't a useful answer is it. but it's the best answer you got for me with the details i provided ain't it.

Since Vista and Win7 are both NT6 The methods are extremely similar. Should be no issue to repeat what you already did, and make a few adjustments as required.

There has been some debate about two packs or one.

USB seems to be a chipset level driver... If something makes sense to you try it .

could split out the two fat cats into a 3rd party DriverPack making it an option... with or without utility.

the full explanation is here http://forum.driverpacks.net/viewtopic.php?id=2461

but basically you just

1) remove the folders and the associated entries in the packs INI file.

2) use 7zip to repack.

Optional:
  If you are really living large you can use this method to pack it. http://forum.driverpacks.net/viewtopic. … 538#p57538 That helps some of our sister sites to use our packs more efficiently with their tools and we release them officially this way as good will gesture.

test, update, retest, reupdate,... success, share