Bâshrat the Sneaky

You are trying to use these drivers for SBS 2003, right? You should have read on the website the DriverPacks are designed for Windows XP only. In most cases they will also support Windows 2000 and in several cases Windows 2003, but not in all. That's why it's not working for you. I'd suggest you read the article "Building Your Own DriverPack", I think it might be useful for you. Question answered, topic closed.

This is one of the many features that will be implemented in the future, but don't expect them too fast.For the moment, you'll have to keep on doing these things manually. I'd say: keep tracking these forums once every while and you'll see when the time has come! 'Question' solved, the concept in this request was already in the todo-list, topic closed.

A solution has been posted in the DriverPacks BASE V5.10.5 topic, a fixed version of the DriverPacks BASE is about to be released. Problem solved, topic closed.

Thanks, Fencer128. That's indeed the topic you should check if you're stuck with my DriverPacks. Topic closed.

LittlBUGer and Nakatomi2010, what NVRAID BIOS versions do you have? And congratulations, LittlBUGer!

Open the Readme.htm included in the DriverPacks BASE. From there you can go to the pages for each DriverPack, which include a COMPLETE list of all drivers, the devices they support and of course in which folder a driver is located.

Added to my todo-list. In the next update of DP Sound A/B (depending on what chip), your driver will be included. (Assuming it's not yet included, of course.)

I can tell you every driver existing on this miserable planet will be included. But currently every driver has to be added manually and a webcam DriverPack just makes not sense then. I'd suggest you create a small DriverPack with the drivers you need and use that for now.

Odd Any progress?

Is it a multiboot disc? Please attach your I386\txtsetup.sif.

Where did you get that "Trying to integrate (drivername)... Success" command prompt?

Thx, but I already noticed it. Also released: the new 6.80 driver for dual 16x motherboards!

Remove 'WPI.cmd' from your cmdlines.txt. The rest looks fine.

Eh Nakatomi2010? What's that code? Google doesn't find anything for it... I've got ONE LAST request: please redo the slipstreaming of the DriverPacks with the original DriverPacks BASE and just copy the nvcchflt.sys file (cab compressed of course) into the I386 folder. That's how I did it when DriverPack MassStorage's nVidia nForce mass storage controller driver was at 6.53 (5.18) and it worked just fine. Only... this might give us the ability to KEEP the nForce 4 SATA- & SATARAID-specific drivers.

Arghhhhhhhh /me slaps himself in the face I *DID* include the 6.53 (5.18) mass storage driver in the 123 folder! I thought I had included the 5.10 (4.46) mass storage driver, since that is what I did first! It also seems the nForce 4 Intel Edition drivers are not NECESSARY, though the 7.13 seems to be alot newer. But look what I found! Amazing , huh? Checking out this driver now...

@Nakatomi2010: hmm... WTF.... forgot about that... the 6.53 is an nForce 4 driver... of course that works :| But what about the nForce 4 Intel Edition-based motherboards? Forgot about that: please tell me what bios version you have! That is also of great importance! @alhaddar: Nakatomi2010's problem is a problem that exists for MANY and yours only for you and one other person. That means your problem currently has a lower priority. Sorry! But this weekend I'll have plenty of time!

Check my sig... So... you REMOVED the nForce 4 drivers and it installs correctly? What's the name of the mass storage controller in Device Manager?

Which was the last DriverPack that DID work? I haven't updated the driver so this issue amazes me. Nor did a driver update occur in which there was a driver conflict!

Hm, then you must be starting WPI through a batch file that runs WPI but does not wait for WPI to end? Please post the details on how you run WPI. As well as which method you chose to run BTS_DPs_finish.cmd (GUIRunOnce/RunOnceEx).

This time you're not being complete. I *did* reference all files that are required, but: the 6.53 driver is an exception. It's the only driver in which that additional file, 'nvcchflt.sys' exists. Two more things: 1) is this an nForce 3 chipset? Whatever the answer, please give me the exact name of the motherboard, as well as the HWIDs. 2) Please retry ONCE more, but DON'T remove the drivers for nForce 4 this time. Your answers to 1 and 2 will confirm (narrow down to) the 6.53 (5.18) driver being the only truly working driver.

Please try REPLACING the files in the I386 folder, as I asked!

No these references MUST be there! It's more probable you slipstreamed RyanVM's UpdatePacks AFTER my DriverPacks! The file portcls.sys is slipstreamed to the I386 folder by the DriverPacks BASE!

It's correct that you have to download the DriverPacks manually. About your second question: that's been asked sooo many times, for example here just one day ago. Still working on the HDA problems...

hehe well, as a first try: just CAB nvatabus.sys and nvraid.sys and copy them into the I386 dir, overwriting the older ones (or back them up) and retry!

Basically that is the same method I'm using, only I'm mixing up drivers to get support for all nForce setups. Since you don't bother trying, I'll send you this weekend (or perhaps already tomorrow) a special edition of the DriverPacks BASE and DriverPack MassStorage, in which those older versions are incorporated. (I have the driver, you don't have to send it!) Could you test it this weekend or do you need it sooner (i.e., can you only try it at work?)