Search options (Page 48 of 159)

Well, if you add the drivers to the install.wim with DISM then you're going to have all the drivers remain even after install...significant bloat.
The method I prefer (to minimize the driverstore bloat) is to only integrate dpms & Chipset and use my SAD2 script post-install.  Using dpinst.exe ensures that only the drivers that are needed are installed and the script cleans up after itself.  I'm still planning on getting DriverPacks Finisher to work in an NT6 environment.

Moved to Third Party DriverPacks
So it's Ricoh AND O2micro?

Yes.  In fact a VPS script would actually extend the functionality quite a bit.  But batch-script is easy, and these would make a good learning tool for those willing to look.

Since this is a DriverPacks support site, and you didn't use DriverPacks, then you're not in the right place.
But we'll try to help anyway.

So you're saying that the factory restore disc for your notebook doesn't work on the notebook it came with?
Make sure you have all external devices disconnected from the notebook prior to the install.
If you still have the error, then that's a hardware problem.  Especially with the blue screens and crashes you were having previously.  You should contact HP for possible warranty work.  If it's covered under warranty, the repair will be free.

When do you get the error?  Is it before or after you select the drive on which to install Vista?

The .exe drivers you downloaded are meant to be executed from within the Vista desktop, AFTER a successful installation.  They can be extracted and integrated into the CD itself, but that is NOT a noob-friendly procedure.

That would be great Rick, thanks!
On my Acer netbook I get both Synaptic AND Elantech utilities installed...and neither work.
This setup works great for XP but not Win7.
Back to the drawing board...

Link?

LOL, spam magnet!

I'm updating this pack now, but that file is going to cause problems in Vista/Win7 because it's meant for Server 2k8.

Hmmm, any idea where it's coming from?  I'll have to dig around.
Strange, in my new Vertex2 SSD Win7-64 install there's not a trace of any silicon-image control panel.

Ah, that's because I stupidly deleted the i386 folder.  Fixed in my local copy of DriverPack Chipset 11.06

No specific examples.  KTD is not recommended because of the increased file size bloat and the extra registry entries required.  It's ONLY beneficial for those users who swap hardware nearly every day (testers).

Updated first post with fixed scripts.  Fixed drivers-x86, was missing image #5 (Ultimate).  Updated setupcomplete.cmd to include both x86 & x64 items (Thanks dolivas!)