Search options (Page 121 of 159)

Can you read this thread and post the requested log files?
It sounds to me like your XP source is tainted somehow, unless you didn't follow instructions.
iertutil.dll is only for IE-7.  You probably integrated ie7 somewhere along the way and it went wrong.
When integrated properly with DriverPacks BASE, driver signing policy is disabled for the duration of XP install until after you reach the desktop.  If you're seeing those prompts, you didn't do something correctly.

First, I'd disable KTD.  It's not needed anymore since we developed SAD (Stand Alone Driver disc).
Second. Don't use nlite to remove/integrate drivers, or to disable driver signing.  Let DriverPacks BASE handle that for you.
Can you  "read before you post" and post the info requested?
For that laptop, you'd want DriverPack Graphics C for the drivers, and DriverPack Graphics A for the control panel/CCC.  DriverPack Graphics A doesn't contain any drivers for that graphics card.

Please try the above and retest with a fresh source, then post the files requested if you have any other issues.
Thanks for posting.

DriverPacks only ADD TO existing drivers, NOT replace them.
In the age of DVD drives, there's no reason at all to remove drivers with nlite.  To do so is begging for trouble.

Two scans. All nightly graphics DriverPacks in work.
v3.2 pulled 4224 HWIDs
v3.2b pulled 5733HWIDs

It's a good start.
I'll have to check to see if we missed any.

*Edit
OK, first bug.
v3.2b is pulling HWIDs that are commented out with ';' so I'm showing duplicate HWIDs with blank PNPID Desc

Oh thank GOD!  I'm looking forward to testing the new tool, even if it means more work for me.

LOL, sorry, it's in the nightly.

OverFlow found a possible cause of this bug.
http://forum.driverpacks.net/viewtopic. … 467#p29467

I'm already starting to feel the crunch of "Oh God, what now" since your announcement.  Thanks for all your hard work RogueSpear!
Hopefully, others will take over where you left off with your multimode installers.  They are indispensable!

No problem.  I'm toying with an x86 build on my gateway.
One thing that really bothers me is unsigned drivers.  With these Vista DriverPacks, are unsigned drivers possible?  Because then I can support mobile graphics and other items.
One other thing that really bothers me is the lack of a DriverPacks Finisher.  There's a way to script it into SetupComplete.cmd by using discriminating code (IF exist xyz then install abc / or If not exist xyz then goto abc) etc.

But ideally, we'd build an autoit DriverPacks Finisher, just like for XP, then invoke it with SetupComplete.cmd.
Sounds simple to me, but Jeff would be the pro at this.

Easy.
1) Run DriverPacks BASE and select your source folder.
2) Click the right arrow until you get to the DriverPacks selection screen.
3) Click "select none"
4) Click "slipstream"

That's it.  Your DriverPacks are now removed from your source and your source was placed back to the state it was in prior to DriverPacks integration.

Well, vlite seems to build the iso OK most of the time, only when the install.wim isn't corrupted.  I've almost got all the updates slipped in.  Once I get a stable updated source, I'll start playing with the drivers.  It seems a huge pain to have to rebuild the image with vlite everytime though.
I hope Win7 doesn't have these issues.
*Edit
OK. All the utilities failed to create a usable .iso from the oversized source 4.46 GB (4,798,613,014 bytes)
I had to use PowerISO and open my original source .iso, delete it's contents, then drag over the modified source and save.  Success.

So that I can better understand how driver integration works, can you tell me where the tool deposits the driver folders and what structure must the DriverPacks maintain?  What files are edited?

*Edit,  One suggestion for Vista-tool.  Progress bar.
I don't think it would be too difficult to count the number of hotfixes/updates files, then use that as a total (ie, installing update 21 of 60: 34% complete).  That would be better than the zero feedback during integration would it not?  With the command prompt hidden or not I still have no idea how long the process is taking.