Bâshrat the Sneaky

Well, that device is supported by the VIA Vinyl driver indeed. It seems it doesn't hurt at all. Please create a new topic from the moment you're experiencing problems because of this. Request implemented, topic closed.

Request implemented, topic closed.

Request implemented, topic closed.

****.... so easy... just gotta see it About that SET /P CHOICE=" " command: note that there ARE spaces between those quotes! I use this code to create an offset from the left border of the CMD window, so you can clearly see what you're entering. Problem (really) fixed in DPs BASE V6.02.5... Topic closed.

Problem solved, topic closed.

Why isn't TeamSpeak good enough? BTW, TeamSpeak 2 seems to be much better.

Then it's impossible that it isn't working anymore: I haven't TOUCHED the nVidia mass storage drivers!

On which of the mass storage controllers are you installing Windows XP?

Do you mean it STILL stutters, even after you apply either of the fixes???

Then that plugin's entries must be hard coded! Those are indeed work-arounds. I'll contact the author.

Check the MX_*.inf file

Erm... WTF! Does everybody have this problem? Could you verify that WatchDriverSigningPolicy.exe is running?

Eh? AutoRun DURING setup?

Check the included .pdf file, it contains a complete tutorial

@lightsout: checked it immediately and unfortunately you're right... Update this weekend. (I *DID* process the new driver, but just forgot somehow to copy the new driver files... ) @Nakatomi2010: I DO know that. Check DP MassStorage's changelog for an explanation That HWID is assigned to the ati3112r driver. That was the same driver that was used before V6.02 of DP MassStorage for ALL Si3112r devices, but is now only kept for compatibility reasons (for ATI chipset based motherboards). But I've already built in a work-around, I don't understand why it doesn't work... EDIT: setup worked fine UNTIL the reboot where setup really starts? (The reboot after the file copying process?)

That HWID is supported by the custom Mobility driver (in DriverPack Graphics A). It didn't get installed? Or didn't you try it yet?

This problem is solved in DriverPack Graphics A V6.02.1, which will be released tomorrow.

Request implemented, topic closed.

Request implemented, topic closed.

HWID please...

I like Fatality's minimalism. And of course that sexy ... ehm... wallpaper

Silent application installations do not require other approaches or something like that when you want to install them through WPI (or through XPlode/RunOnce/RunOnceEx/whatever).

The font of yout start menu is different from the font in your task bar and it SUCKS. Is this a custom setting of you or was it like that by default? (Is this beta alot better than the 5270 build? Didn't have the chance yet to install that one...)

Ehm yes... of course it will work. The answer to the order can be found in the FAQ: Please search better next time

OK, final conclusion: I'll need to detect AMD X2 CPU's and then update the boot.ini file with the /usepmtimer switch. I'll look into the best possible way to do that now.