Search options (Page 112 of 213)

the key to finding out what did or did not work is in the setupapi.log
You might also find the dpinst.log useful.

Nothing, I repeat... Nothing, is as effective as having the drivers available during setup. (RIS)
However the redistributable MS tool DPInst.exe is the best 'Software First' option there is...
DPInst is the Core of SAD

as far as how you took my comments... if you would have substituted your second reply with the third...
My time here is free but that does not mean you (anyone) have a right to waste it, and if i feel that you (someone) are...

I don't normaly apologize (In fact I don't think I ever have on this forum)... But I like your style... I am sorry.

I like the 2002 space age best

Apparently you did not read what i wrote....

SAD does what you want... it installs all the drivers in the packs automatically

Run DriverPacks BASE and select SAD... not only is it possible but i have already told you how.

Create a SAD Disc or network repository and run DP_Inst_Tool.cmd it automatically installs drivers.

SAD does what you want... Try it before you ASSUME i did not understand you.

The KEY is paying attention...

I also told you how to address the IE issue...

I also told you using RIS will eliminate going to the machine at all

Please attempt the solutions offered FIRST, then report back if you have questions.

Here is your answer in case you don't want to read all the stuff below - DriverPacks BASE SAD feature.

The best solution is RogueSpears AutoImage which will allow you to do a RIS install.
That eliminates the CD and related space issues altogether.

Batch scripting software installs is effective but clumsy, I would suggest you take a look at Windows Post Installer (WPI).
Since you already have the switches required to automate the install, adding them to the interface would be a breeze.
It is a ery powerful tool that allows multiple configurations, will auto continue if a reboot is required and is just pretty darned slick.

DriverPacks BASE has a feature called SAD (Stand Alone Drivers) this feature will allow you to create either a network repository or a CD with all of the DriverPacks. That will cure your driver issues, however I would like to point out if you used RIS with DriverPacks then your drivers would simply be installed with the OS an eliminate the need to use SAD.

I personaly carry a DVD and a USB to IDE converter. You can either hang a DVD on the machine (It is always a good idea to open the case so you can verify that the CPU fan has not become a dust bunny nest. ) or use the USB option if the box supports boot to usb. a DVD is 20 dollars and a USB to IDE is even less.

The RVMIntegrator and nLite can both add IE to your install quite easily. There are several IE7 AddOns for RVMI and many RVMI addons can be added with nLite.

if you cant answer simple questions like telling us the version number.
And it is obviously not the most recent as you said - don't lie to us - we know better.

(or providing your base log which is almost always required for support) I will close this thread.

modifying the presetup file is also not supported, and your version above is not valid at all and won't even be called.

Post your log.

Moved to other

What version of DriverPacks BASE are you useing?

It says in the news artical about the slogan (in the news forum)

We are not very formal around here it directly ties to your response so not really OT. IMHO

Cincy is not an available area for the radio... but I will keep an "ear" out for the webcasts.

Thanks for Posting you have helped to make DriverPacks better for everyone.

Have a great day!

This is because if you only slipstream textmode drivers then the Plug and Play drivers are not available to WinPE or Windows (Since you did not include them) so it will BSOD. Some drivers don't need thier PnP counterparts, these will work fine (Like IDE drivers). I recomend useing mass text and regular mass as a set.

If you only select mass textmode no OEM folder is created.
(it is not neccessary to select custom for the finisher. if no packs are selected the finisher will not be added )

The simple answer is "You can't add DriverPacks and not end up with an OEM folder"
UNLESS... You don't plan on supporting mass storage drivers that will require their PnP counterparts.

FORGET THE CAT!

EVERYTHING YOU NEED IS IN THE INF... got it?

you might as well ask if you can tell if the driver is suitable from an MD5 checksum...

We have several drivers that match on PCI\VEN_8086&DEV_2829 (super generic match)
i was not able to find a specific match to either
PCI\VEN_8086&DEV_2829&SUBSYS_022F1028 or
PCI\VEN_8086&CC_0106 in the pack

We will see what we can do...
Normaly a link is considered polite, but the name of the file and site works just as well! Thanks!
R166200 here!

I bet I know where you could find a few hundred thousand people you could get to give you a good reference