Bâshrat the Sneaky

Well... please tell us what exact method you used... Else we cannot help you...

Hehe Well I WOULD have noticed it when I'd be updating the driver files

Did you check DeviceManager if your devices were installed properly? Because some utilities won't be installed by just installing the drivers... (E.g. nvmixer)

With only comparing and logical thinking (and wasting alot of time), I came to the EXACT same conclusion as you, mark49! 6.53 (5.18 WHQL) (IDE\WinXP)=> will be used on all nForce 1/2/3 systems 6.66 (5.34 WHQL) (IDE\WinXP\sata_ide & IDE\WinXP\sata_raid) => will be used on nForce 4 AMD Edition systems 7.13 (5.35 WHQL) (IDE\WinXP\sata_ide & IDE\WinXP\sata_raid) => will be used on nForce 4 Intel Edition systems Since ALL drivers are now signed, Windows XP will NOT use its default drivers and thus your extra HWIDs solution is no longer required. If setup will still use the default driver, I will add that solution too. Problems should be over now! (But.. how many times have I yelled that phrase now already? ) @RogueSpear: though nVidia's nForce deliver great performance, I couldn't agree more! I'd always buy extra controllers (if I had the money: I will use a nForce 2 RAID 1 setup as a server soon...).

I'm sure RyanVM is working on that!

Sorry for the late reply guys! This is all VERY interesting... I think your findings will be VERY useful, mark49! You've proved yourself to be very intelligent once again. I'm now working on a working approach for the nForce mass storage controllers. One thing is sure: I WILL use the 5.10 driver for the nForce 1/2/3 series, the 6.66 driver for the nForce 4 AMD Edition chipsets and the 7.13 driver for the nForce 4 Intel Edition chipsets, no more merging of drivers. Though this will imply some more interventions in the txtsetup.sif & dosnet.inf files, this has the highest chance of working. I will report back to you when I've completed a part of the new approach.

Not everyone uses a DVD... and... when you use M2 there's no difference, but when you use M1, there is a SIGNIFICANT difference! And I 7zip all control panels that need to be called by a command line to install properly, just to keep order!

This project has died, I suppose?

A) I found your original post in which you mentioned which motherboard you were using, so I found this myself. Though I find it very strange that you have to use an Adaptec BIOS... Whatever, I downloaded the driver SuperMicro offers on their website and guess what... Though the version number claimed on the website seems to be the same as the one I'm using. But after downloading and comparing both drivers, it seems SuperMicro's is newer! I'll include the updated driver SuperMicro offers. B) Did this one get installed properly?

Are you sure you did connect it properly?

Maybe you should read all subforums' names again... Or use the search function. (Hint: that's exactly what we're doing here! )

Distribution of non-freeware is not allowed in any case. Distribution of freeware is allowed in some cases. Sharing methods for silent installations is allowed in all cases (on condition you don't include your serial number, of course).

Hmm... Nice dissection But you didn't notice one thing... which is that you are missing one entry in your cmdlines.txt! I.e.: [COMMANDS] "UaMusic.CMD" "UserAcc.exe" "REGEDIT /S regtweaks.reg" "REGEDIT /s MenuOrder.reg" ==>"BTS_DPs_ROE.cmd"<== "RunOnceEx.cmd" That should solve it! P.S.: Why in the world would START /WAIT not work.... P.S. 2: I'll change the temp folder from %TMP% to %SystemDrive%\TMP, that should also solve that other problem of you!

Don't you think this installation problem is probably related to the development?

I'd suggest you go ask on a driver developer board, since we only INSTALL (slipstream) drivers here, we don't develop them...

Try my DriverPack MassStorage in the mean time... That's your best option.

You *DO* know 2.6~2.7V is the default voltage, right? 3.3V is still acceptable, but 4.03V.... I'd NEVER do that!

Without reading everything in detail, this is my guess: disconnect the USB cable modem during setup, connect it AFTER you're logged in. EDIT: or put a router in between. EDIT2: and this is also incorrect: [GuiUnattended] & nbsp

In fact there ARE no big advantages except for that you're running a 64 bit OS on a 64 bit CPU, which IS faster, but not by much (yet).

How much bandwidth do you need? ATM I have *some* (that's /slightly/ understated) bandwidth in spare, I could offer you some until you find a final solution. Contact me if you're interested.

All 3 of them are working for sure now! But how is your problem going?

You should know that the OemPnPDriversPath is limited to 4096 characters, if you initiate setup through winnt.exe/winnt32.exe it's even limited to 1024 characters! My point is: don't put it to deep in your folder structure! And yes, you're on the right path EDIT: forgot to say: this is method 1 in the DPs BASE. (But the DPs BASE only works for CD-based installations!)

Is your problem solved now?

Sorry, forgot about your problem, will handle it tomorrow!

I can confirm the nForce APU control panel is working, though I am using GUIRunOnce instead of RunOnceEx. 1) Please confirm-the presence of $OEM$\BTS_DPs_ROE.cmd. 2) Please post your cmdlines.txt file (use CODE tags this time!).