Bâshrat the Sneaky

HWIDs please. Check my sig for a tool.

Correct. Question answered, topic closed.

Yes, you'll have to update to the latest DriverPacks BASE. You always should have the latest BASE!

OK. Then you'll have to have some more patience until after my exams, then I'll have the time to finish the HWID-based work-around system. And once more: I cannot add support for nForce 3 ethernet without removing support for nForce 4 ethernet! And AFAIK, there are more nForce 4 users than nForce 3. PLUS this bug does not apply to ALL nForce 3 motherboards.

looks like windows setup itself know which inf file is needed Yes indeed.

Just to let everyone know: I won't reply very much (probably close to nothing) till next thursday, because of a small exam period. Tuesday: English (why do I mention this one? piece of cake) Wednessday: Latin (OMFG ... if I'll get a good score on this one, it will be thanks to either pure improvisation or extreme luck) Thursday: math (shouldn't be a problem) Thanks for your understanding. P.S.: after this I'll have plenty of time, so you can expect work-arounds for AMD X2 CPU's, nVidia nForce 3 ethernet and others Bâshrat the Sneaky

That's a different mobo, I suppose? Or is the problem just solved?

Just keep all of them

It had already been mentioned. And people would (well, they *should*) know that the months are wrong, thanks to the version system (6.03 means the third month of 2006).

Could you give me the COMPLETE BSOD error code (everthing after the 'STOP')?

Very well, topic closed then.

This isn't a bug Those are the drivers that ship on the Windows XP CD by default and for which there are updated drivers in DP MassStorage . And in the DriverPacks BASE I've programmed this routine: 1. remove ALL slipstreamed DriverPacks, which includes the .sys files in the I386 folder; 2. restore the original files; 3. slipstream the DriverPacks, and possibly DP MassStorage (which would overwrite all these files). EDIT: Topic closed.

DriverPack LAN V6.03.2 Changelog: V6.03.2 (22 Mar 06) -Fixed: work-around for nVidia nForce 3 ethernet (experimental; I doubt it will work, but it's worth the try). -Updated: D-Link DFE-530TX, DFE-520TX, DFE-530TX+ (rev. F) driver from 04/26/2000,2.52 to 05/17/2005,3.46.0.0431. -Updated: D-Link DFE-530TX+ driver from 08/23/2001,5.397.0823.2001 to 03/26/2002,5.503.326.2002. Download

Check this topic. EDIT: Topic closed.

Request implemented, topic closed.

Hi Bâshrat the Sneaky. I've tried to install with only Chipset, Lan and MassStorage and I've got BSOD. In another try I've put everything without Chipset, Lan and MassStorage and then I was able to do install successfully. I will try to do all packs without chipset and post results. My blue screen is different from the one in the linked post. In my blue screen there is no info about driver, only acess violation and anddress, If I would have had the driver name in my BCOF then I will be able to figure out which pack caused the problem, but Unfortunatelly I don't have the name of the driver. Thanks Bâshrat the Sneaky, for looking into this. Very well, but then I'll need the EXACT BSOD error code (everything after 'STOP'), if you want to get this solved

You cannot use nLite to slipstream a driver that's also slipstreamed by DriverPack MassStorage. Then the driver file will get overwritten by the one of DriverPack MassStorage. Then I can only think of ONE more test scenario: create a new UWXPCD without the DriverPacks (or at least without DriverPack MassStorage) and slipstream your driver with nLite. Don't forget to use nLite BEFORE the DriverPacks, if you still want to use them.

Can't you contact the author and kindly ask to add support for more colors in a program update? I'd think he'd seriously consider it...

@Tristimulus: this is an nVidia driver bug: nVidia GPU + nVidia nForce 4 chipset gives you that BSOD, which is caused by nv4_mini.sys by the way. Nothing I can do to solve it. More information here.

99% chance that it's a corrupt ISO.

Exactly what I'm using. i6comp.exe should do the job in 99% percent of the cases. I remember there's a GUI for these CLI tools too...

Yes, changed that in UpdateChecker V60342

@Houz74: changed that in UpdateChecker V60342 @all: ok, problem solved: topic closed.

PM sent.

Fixed version has been released! Let me now if the problem is truly solved.