Bâshrat the Sneaky

Correct. And more specificly, I mean the lines in the "operating sytems" section.

OemPnPDriversPath in winnt.sif/riprep.inf Windows 2000 & XP: 4096 bytes Same, but setup started by winnt.exe/winnt32.exe (not booted from CD, but started through DOS/from previously installed Windows): Windows 2000 & XP: 2048 bytes DevicePath key in the registry (REG_EXPAND_SZ): Windows 2000 & XP: 64000 bytes Which implies: no need to worry! As for that UIU crap: if they edit their driver's .inf files, that breaks WHQL signing. LOL. Such a professional product... Like that I could reduce the size of the DriverPacks, at the cost of the WHQL signing. The same thing for renaming the .inf files: that voids the WHQL signing. As for their integration method: you can do it that way with my DriverPacks too, and very easily Just extract all DriverPacks to C:\D, then run SetDevicePath.exe C:\D, et voila. To remove them, simply delete C:\D and then run SetDevicePath.exe again, without any parameters.

It's working and implemented in DriverPacks BASE V6.04, though with one minor limitation: it must contain any of the following keywords in order to qualify for a /usepmtimer switch: 2000, 2K, XP, 2003, 2K3. That's won't be a problem for 99% of the users, I think.

offtopic: Why are you so obsessed with Windows 2000? Most 2K fanatics became 2K3 fanatics, but you obviously did not. What's the story?

.inf? .sys, I assume?

Do you mean the 'Welcome to XP'-thingie? That's called OOBE-experience, I believe.

Ryan rules

Request implemented, topic closed.

Yes, if you didn't use DriverPack MassStorage on that disc, NEVER I mean then, that problem shouldn't exist. You never slipstreamed DP MassStorage into that particular disc? And did you use nLite? Did you modify txtsetup.sif/dosnet.inf manually?

What was the exact problem? Because the HWID IS listed in D\G\N\1\nv4_disp_go.inf...

Any news about this issue?

Well, he's wrong: the .NET FW is only required for ATI's CCC, not for the driver itself. Could you please post the EXACT BSOD error code?

In that new package, there are only driver updates for mass storage and ethernet drivers, which are not included in DriverPack Chipset, but in DP MassStorage and DP LAN. You will see updates there, not here. Topic closed.

You can re-use your previous UWXPCD with DriverPacks integrated. But if you removed some things with nLite after that, you WILL get into trouble (because the DriverPacks BASE makes its own backup of txtsetup.sif...). And why would you want an unbootable CD? Is it so much work to just slipstream (or update) the DriverPacks, start nLite, select your UWXPCD directory and then do nothing else but create an ISO? IMHO that works very easily and fast...

eh... do you have 2 accounts here, razormoon (or RJARRRPCGP)?

I'd recommend method 2 as well. I'll add an FAQ entry about this... @5eraph: actually method 1 may still be slower than method 2: -m1: time necessary for searching .inf files from CD/DVD (= very slow) -m2: time necessary for decompressing (= relatively slow) + time necessary for searching .inf files from HDD (= very fast) The actual difference in time would not be so large, I think, and even more often in the advantage of method 2. Not 100% sure about that though (I'm not benchmarking it continuously...). EDIT: I added it to the tutorial.

Yes, but then you'll have to insert that CD whenenever a driver is needed, but you're aware of that. Another thing to note: if you're using a newer 'DriverPacks-CD' than the one for which you executed SetDevicePath (minutes, days, or months earlier), some folders might no longer exist and (probably) many may have been added!

Did you use nLite or something else and then upgraded to the newest DriverPacks?

It's harmless It's just an installer... Topic closed.

Why aren't you just installing from the CD? Why do you start setup from Windows 98? Just asking, I'm interested why you would want to do it that way.

Actually, this one is 1.2.2.2 vs 1.2.2.0 previously. AMD just didn't update it in the .inf file...

Fixed right away Stupid tiny buggie... P.S.: it's strongly PROHIBITED on this forum to speak/write Latin Watch your language next time! (Latin is a sucky language, certainly those texts written by people who strived for fame in literature...)

Obviously this will keep on working. The reason for this being Dutch all of a sudden is simple: I had to update the driver, but AMD's installer doesn't allow any extracting of any kind. Therefore, I had to run the setup on my brother's pc, which is running Windows XP English, BUT as you may know or not know, language settings are chosen by the keyboard layout, NOT by the OS' language. And voila... If you could supply me with the English version, I'll add them... But as I said, it won't hurt.

Probably. Hopefully. Expect updates tomorrow

Done with them! In June, I'll have the VERY LAST series of exams in highschool . University will be so much more interesting... My expected results: English: was easy Latin: I was very lucky... could have been killed... but had the easiest texts to translate, so also a very good result math: also not so difficult, which means I expect for this exam too a good result Conclusion: Extremely high scores tomorrow? We'll see