I've stopped using RogueSpear's .NET addon since he stopped future updates to it.  I now use this one with great success.
http://www.ryanvm.net/forum/viewtopic.p … mp;start=0

2,827

(30 replies, posted in DriverPack Graphics)

OK, tenchi103 was doing some testing for me through email and confirmed his problem is fixed using my modified mobility.inf with Catalyst 9.3.1. 
So, I'll try to update DriverPack Graphics A \AM from 9.3 to 9.3.1 but it's going to take me a whole lot of work to transcribe all those HWIDs over.
Damn! sad
I don't know where I'm going to find the time to fix this.
This will definitely need to go into a new release 9.07.1 once beta testing is complete.
abdou, tenchi103...are you two up for some beta testing? smile

If you can, post the DPsFnshr.log split between two posts.  Also post the portion of the setupapi.log (search for: VEN_1002&DEV_9591)

2,829

(4 replies, posted in DriverPack Sound)

We're working on it!

2,830

(60 replies, posted in Vista / 7 DriverPack Graphics A)

No need.  It's just the right size! smile

2,831

(24 replies, posted in DriverPack Graphics)

If you download the standard nvidia drivers, then extract them to a folder and run setup.exe they'll work fine.  But if you go through device manager and click "update driver" using the "have disk" method those same drivers will fail.  Nvidia designed them that way I guess.  Your guess is as good as mine.  Hopefully nvidia will release some drivers that actually work soon.

Incidentally, I have two D630 notebooks at work that I need to re-image and neither have nvidia chipsets.  Odd neutral

You need to have one or the other, but not both.
Can you post your DPsFnshr.log please?  It's big, so split it into two posts.

2,833

(24 replies, posted in DriverPack Graphics)

I don't know why nvcuvenc.dll is failing.  I can't spot anything out of the ordinary and all the entries are the same as nv4_disp.inf (which is what my card uses.

You've found the NvCplSetupInt bug I fixed. smile  You have to change one of the destinationdir from 01 to 11 to fix that copy bug.  Nvidia really needs to do their homework with their .infs!  Lately they're garbage.

2,834

(24 replies, posted in DriverPack Graphics)

Well this is interesting.  Notice this entry in the nvdm.inf

[nv_CplInstaller_addreg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Run",NvCplDaemon,%REG_SZ%,"RUNDLL32.EXE %11%\NvCpl.dll,NvStartup"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Run",NVHotkey,,"rundll32.exe nvHotkey.dll,Start"

Notice that the reg entry "Run" for nvhotkey is missing the directory (%11%) that contains it, like the line above it?  It should read:

[nv_CplInstaller_addreg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Run",NVHotkey,,"rundll32.exe %11%\nvHotkey.dll,Start"

But why this doesn't fail on your other notebook is beyond me.  What HWID does it have?
Incidentally, nvdm.inf is the ONLY .inf that contains that reg entry.
Can you unpack DriverPack Graphics A, edit nvdm.inf to correct that line, repack and retest?

Sorry for your lack of sleep. smile

2,835

(24 replies, posted in DriverPack Graphics)

I forgot that I modified the nvdm.inf (and the other mobility .infs) to fix the installer bug introduced by Nvidia (bastards!) with 185.85.  That's why you see the "not signed" errors.
Strange that you get the error during ROE.  That shouldn't happen.  The drivers actually get installed between T-36 and T-34 of XP setup.  ROE 987 is when DriverPacks Finisher runs and it has nothing to do with installing drivers.  All DriverPacks Finisher does in execute any additional installers for control panels and the like.  DriverPack Graphics A\g\n1 has no installer entries for DriverPacks Finisher, only a single registry entry which can be safely ignored.

It's possible that there's other issues going on during first logon.

Welcome to DriverPacks.net
Did you use DriverPacks in your XP install? 
This is a DriverPacks support forum.

2,837

(24 replies, posted in DriverPack Graphics)

That Quadro HWID is directly supported by DriverPack Graphics A 9.06 and the nvdm.inf is untouched from nvidia 185.85. 
Odd.
Have you checked the hashes on the DriverPacks?
At what point in setup do you get the nvhotkey.dll failure?
Have you looked in setupapi.log for the specific error? (search for VEN_10DE&DEV_042B)

This should have been implemented in the latest release candidate.  We should be going public with it as soon as some more testers report in with successes.
Can you post your affected HWIDs?

2,839

(8 replies, posted in Software)

See if the system will boot in "Safe" mode.  Hold (or repeatedly mash) the F8 key after the BIOS.

2,840

(1 replies, posted in Software)

Did you modify your "driver.cab" in any way (nlite/etc.)?
Does this problem manifest itself after using DriverPacks or without?  This is a DriverPacks support forum you know. wink
Welcome to DriverPacks.net! smile

Weird! neutral
How does it react during a clean XP install with DriverPacks integrated?

Try this please.

DP_Graphics_B_wnt5_x86-32_90701
*link removed after test*
MD5: 9031fa42949548dfd8274202bed33d03
Size: 78.7 MB

Well I looked, and DriverPack Graphics B \I4\igxp32.inf has your HWIDs.  I had edited it to remove duplicates (and broke driver signing in the process).
That may be why it doesn't work for you if you haven't disabled driver signing.
I'll have a look at those Dell drivers...
*Edit,
They're from 2006.  I'm not going to replace I4 for those.  I'll replace my edited .inf with the original one.  Can you test that one after I upload?

2,844

(18 replies, posted in Other)

The dp_inst_tool has nothing to do with the Windows hw detection at first boot.  You're seeing the normal Windows setup post-install at first login.  Any hardware not installed after image extraction will have the hw wiz popup.
If your install uses winnt.sif, then to make it valid you need the following entries:

[Data]
  AutoPartition=0
  MsDosInitiated=0
  UnattendedInstall="Yes"

And to make DriverPacks work without the driver signing popups, you need these entries:

[Unattended]
  DriverSigningPolicy=Ignore
  NonDriverSigningPolicy=Ignore

If you don't use a winnt.sif file, then I don't know.  I'm not a sysprep guy. smile

Are you seeing the hw wiz DURING the dp_inst_tool or BEFORE dp_inst_tool is executed?  That's critical to know.

2,845

(18 replies, posted in News)

ATI updated their legacy driver to 9.3.1 over the weekend.

2,846

(2 replies, posted in DriverPack Sound)

Would you have a USB device connected during setup?  I suppose there's room in DriverPack Sound B.

Geez, do you really think we'd release a utility that didn't work? wink
I'll admit that Vista-Tool 1.0 is confusing to use.  It took me a long time to get things right, but once you got it...you got it. smile
There is a guide you know...

2,848

(5 replies, posted in Feedback and Support - DriverPacks Base)

tusk wrote:

left with...excel sheets

GOTCHA! wink
You've been using 'nightly' builds you little sneaker! smile
Excel files and 'changelog' files are all removed from final builds.  They only exist in nightly/beta testing builds and they are not deleted on purpose.

2,849

(30 replies, posted in DriverPack Graphics)

That shouldn't really make a difference, but you never know! smile

2,850

(16 replies, posted in Windows 7 Discussion)

Ordered mine from BestBuy since it was free shipping/tax-free.  1x Pro, 1x Home Premium.