Bâshrat the Sneaky

You've got a too long OemPnPDriversPath entry The max is 4096 chars. Tips to avoid this: use 'D' instead of 'Drivers' use 'C' instead of 'Chipset' use 'E' instead of 'Ethernet' etc... You get the point And yes... please remove your key.

****!! Congratz epic! That looks CLEAN, a think I've been looking for... but never found the 'ultimate' one. It seems yours is Any chance I can use it? Or test it for you?

1) Only use the nvatabus.sys driver for the chipsets that support nvraid. And hope that it will work then. 2) Make sure the nvatabus.sys driver gets installed AFTER setup, because it works fine then (well it does here). I still have to do some testing and then I'll need some beta-testers (with nForce based mobo's of course)

I'm working on the solution for the BSOD. As I already posted in the general discussion topic, the problem was being caused by the nVidia driver... More specificly: the nvatabus.sys driver. I'm working on a fix, in fact a work-around, because the problem lies in the driver, not in my implementation. So ... GET MAD at nVidia! (I am, why shouldn't you )

I need to know: -your chipset -your soundcard -your graphics card

By editing the .inf file, the WHQL signing will become obsolete!

Check out this post by me, with all info about the BSOD and fatal error we're getting when using DP MassStorage. (this also explains why not everyone got the error)

Well... It seems it DOES matter! I keep getting a BSOD when I list ALL PCI ID's: PCI\VEN_10DE&DEV_0065= "MCP2" PCI\VEN_10DE&DEV_00D5&REV_A2= "CK8" PCI\VEN_10DE&DEV_00D5&REV_F2= "CK8B" PCI\VEN_10DE&DEV_00D5&REV_A4= "CK8" PCI\VEN_10DE&DEV_00D5&REV_F4= "CK8B" PCI\VEN_10DE&DEV_00D5&REV_A5= "CK8" PCI\VEN_10DE&DEV_00D5&REV_F5= "CK8B" PCI\VEN_10DE&DEV_00D5&REV_A6= "CK8" PCI\VEN_10DE&DEV_00D5&REV_F6= "CK8B" PCI\VEN_10DE&DEV_008E&REV_A2= "MCP2SS" PCI\VEN_10DE&DEV_008E&REV_A3= "MCP2SS" PCI\VEN_10DE&DEV_0085= "MCP2SP" PCI\VEN_10DE&DEV_00E5= "CK8SSP" PCI\VEN_10DE&DEV_00EE= "CK8SSS" PCI\VEN_10DE&DEV_00E3= "CK8SSS" PCI\VEN_10DE&DEV_0055= "CK804SSS" PCI\VEN_10DE&DEV_0054= "CK804SSS" PCI\VEN_10DE&DEV_0053= "CK804SSP" PCI\VEN_10DE&DEV_003E= "MCP04SSS" PCI\VEN_10DE&DEV_0036= "MCP04SSS" PCI\VEN_10DE&DEV_0035= "MCP04SSP" PCI\VEN_10DE&DEV_0267= "MCP51S" PCI\VEN_10DE&DEV_0266= "MCP51S" PCI\VEN_10DE&DEV_0265= "MCP51P" , but when I only use the ones you posted PCI\VEN_10DE&DEV_008E = "MCP2" PCI\VEN_10DE&DEV_0085 = "MCP2" PCI\VEN_10DE&DEV_00D5 = "MCP2" PCI\VEN_10DE&DEV_00EE = "MCP2" PCI\VEN_10DE&DEV_00E3 = "MCP2" PCI\VEN_10DE&DEV_00E5 = "MCP2" I DON'T get this error. Many of you may think: "Hey, no problem, if it works, it's ok!", but the problem is: using such a limited number of HardwareID's IS a problem! That way setup will simply use the default/regular IDE drivers, thus NOT the nvatabus driver. At first I thought this was being caused by the idecoi.dll file, but it seems that the problem just lies in the driver itself: nvatabus.sys. Just search on the net for keywords like "nvidia boot nvatabus.sys", and you'll find plenty complainting.... Or take a look at the Drivers forum at nForcersHQ Take for example this topic. He doesn't even install it from textmode setup, and still it's failing to work properly! UNBELIEVABLE bad drivers, nVidia! Shame on you! Note: I'm talking about DP MassStorage here An example of someone else for whom slipstreamed nVidia IDE drivers result in a BSOD: topic EDIT: forgot the conlcusion The conclusion: DON'T slipstream the nvatabus.sys driver, this will result in a BSOD. However, I'm not very sure if it's required to get the nvraid working? Anyway, I _think_ that the driver will get installed afterwards, if you simply include it in the PnP drivers!

You did NOT use the MassStorage drivers????????????? Unbelievable! :'( :'( Please post your hardware specs!

I know I should have written 'search every line', but I see you found out yourself

Please do not yet use DP MassStorage. That's causing this error!

That's even better than the -ms switch I think SiMoNsAyS could adapt his guide to this method. Not, SiMoNsAyS?

Did YOU register without a credit card? Cause I really can't. To activate my account I have to add a credit card number....

I know. But you *DO* need a credit card to verify your PayPal account, so also if I want to receive money... I tried before, and it didn't work without a credit card.

You CAN download the drivers. For the moment you don't have to click the ads Just after viewing the TOS, the download links will have appeared on the previous page

PayPal also works with checking accounts so no credit card needed ← But you NEED a credit/debit card to receive money. I already registered with my bank account... BTW... WTF is a checking account

Search for the line DEL /Q txtsetup.oem and delete that line or REM it out. No longer required... My mistake.

@Salvo2002: yes, currently the site is being automated. The problem should be gone now, though. @everyone: I've decided to use the 'trial & error' method to find the DriverPack MassStorage bug... Add each driver seperately and verify if it works. Currently I've done the 3wares and they work so far. I will post the progress in the first post. (will be removed when solved of course)

@lilweirddude: no prob! @S0mE0nesMiNd1: did it EVER cross your mind that the sites hosted don't consume very much bandwidth? My DriverPacks require a HUGE bandwidth. E.g. DriverPack Sound V5.01: +-3500 * +-40 MB = 140 GB of bandwidth. Now tell me, do you think any of the sites hosted uses that much?

HUH? The txtsetup.oem file is no longer used... So you must have used a older version of the DP BASE. (the 'error txtsetup.oem not found' when running RUN_ME.cmd has nothing to do with the 'error(18) at line 47')

I've found one more error in the txtsetup.sif file: the a320raid entries were not completely correct. I tested with the new version with correct entries, and still a BSOD... :'(

@ACEOFNOS & RogueSpear: thank you The only thing that keeps me from adding PayPal is a creditcard... Creditcards aren't that common in Europe as they are in the U.S., I'm afraid! However, I think I'll be able to very soon!

They're already back online But the problem is... now I ain't got _any_ revenue... So I will have to find other ways to keep this project running. Probably I will have to obligate purchases, maybe obligated for all (very low price then) or obligated for the pro-users. What do you guys think of that?

Not difficult... You'll have to do something like this: START /WAIT ati_catalyst_setup.exe /switches REGEDIT /S new_GUI_Run_Once_entries.reg shutdown.exe -r -t00 I hope you understand it.

Well... thanks Rendrag... I don't think I could say it better... maybe a small addition: to install the related apps you could use a 'conditional installation', i.e.: if exist %SystemRoot%\system32\audigy_driver_file.sys START /WAIT setup.exe /switches , this way the related apps will only get installed if this specific driver file is present