Bâshrat the Sneaky

DriverPack MassStorage V6.03.1 Changelog: V6.03.1 (21 Mar 06) -Fixed: downdated DELL CERC SATA 1.5/6ch RAID Controller driver from 09/28/2005, 4.1.1.7038 to 11/06/2003, 4.1.0.7010, because the newer driver was extremely buggy. Download

Yes. That folder contains the 81.98 driver, which is causing this problem.

Hmm.... Could somebody please retry after extracting DriverPack MassStorage and deleting the folders 4A and 4AR in the D\M\N folder? Since what RyderOCZ copied into that 'Raid' folder should be exactly the same compared with what's inside the D\M\N\123 folder.

Very well, I think that's the best solution. This means Dell's latest driver is quite buggy, though!

No, it can't make any difference: the method you choose only matters to the Plug 'n Play driver installation (which is at T-37), which is after textmode setup (after the CD has booted).

Ah, I did not know that. Will be fixed in the next update.

It's been ages since I've last monitored an installation. I'll check it tomorrow (no time tonight).

You can install it at T-12 (cmdlines.txt)

This is a known bug in nVidia's ForceWare drivers. It's a driver conflict between the ForceWare and the nForce 4 chipset drivers. Nothing I can do about it, sorry. The only 'solution' is to do an installation without DriverPack Graphics A (or remove the nVidia driver manually (D\G\N\1 if I remember well)) and then install the graphics driver manually after the installation is complete.

First of all: please stop crossposting!!! This isn't related to Intel SATA RAID drivers, this is related to the error message of the corrupted file only. Solution will be discussed in this topic. Topic closed.

I don't understand how this file could possibly give you a corruption error, since it's not included in Windows XP by default and setup can thus not detect whether that file is corrupted or not. Are you all using fresh shares of Windows XP?

Please post your HWIDs and the name of the motherboard OR the brand and model name of your pc.

Goddammit that's alot of errors Happy I shall be when the day comes that all of this will be automated!

Not exactly, it should only show up to show errors. So that is what it shows, I suppose?

DriverPack MassStorage V6.03.1 Changelog: V6.03.1 (21 Mar 06) -Fixed: downdated DELL CERC SATA 1.5/6ch RAID Controller driver from 09/28/2005, 4.1.1.7038 to 11/06/2003, 4.1.0.7010, because the newer driver was extremely buggy. V6.03 (20 Mar 06) -Fixed: restored previously used Promise Ultra Controllers, since it was newer than the one I 'updated' to (yes, I'm ashamed for that). -Fixed: added missing file to QLogic QLA23xx PCI Fibre Channel Adapter driver (D\M\Q\3). -Updated: Areca PCI-X/PCI-E SATA RAID controllers driver from 03/24/2003,1.01.00 to 06/29/2005,1.02.00. -Updated: DELL CERC SATA 1.5/6ch RAID Controller driver from 11/06/2003, 4.1.0.7010 to 09/28/2005, 4.1.1.7038. Download

BTS DriverPacks BASE V6.03.4 Changelog: V6.03.4 (20 Feb 06) -Fixed: [DPB]: autocopy settings were wrong. -Fixed: [DPB]: BTS_DPs_finish.cmd: removed unnecessary copy statements and corrected some statements for the installation of the control panel for the Sigmatel HDA driver (D\S\S\U). -Fixed: [DPB]: BTS_DPs_finish.cmd: fixed installation of SiS UniVGA3 (D\G\S\1) control panel. Download Known issues -none

I will download the driver and inspect it in detail, but currently ASUS' download sites are all down...

Before I can draw any further conclusions, I need the file I386\mraid35x.sys that's included in Windows 2000 by default. Could somebody attach it?

Hi BTS, I'll check the reg changes - though I've been working off of 6.03.3 (and in fact have just downloaded 6.03.3 to check) and those INI file copy statements are still present for the ...finsh.cmd :DPSB4 section. I think they may still need deleting Cheers, Andy Ah? Well, I thought I had already released the version where it was fixed. No problem, it'll certainly be fixed in the next version then. EDIT: found it: I had already prepared DriverPacks BASE V6.03.4 and I thought I had already released it, which is not the case .

As you can see, I moved the posts to this topic... I had totally forgotten about that other topic (which is this one)! Checking that file now...

Topic continued here. Topic closed.

@flying lion: I tested it again and it's really working Please slipstream the DriverPacks again! @shaz: that's undone in DriverPack MassStorage V6.03 @offline_thk & zorro1 & madmungo: please post your HWIDs! And if possible, also the names of your motherboards. @Firemad: you must be working in an industrial environment or something, since you seem to be working with very high-end hardware . I've updated the D\M\D (Dell CERC) driver and at the same time I've added the missing file (this driver is now also WHQL signed). And I've added that missing .dll file to the driver in D\M\Q\3 (QLogic QLA23xx).

Could somebody ATTACH the original (with SP4 slipstreamed is OK too, as long as you didn't use nLite or the DriverPacks yet) txtsetup.sif file of Windows 2000?

Please post your HWIDs. Check my sig for a tool.

You should look for the HWID "PCI\VEN_1095&DEV_3114&SUBSYS_31141095", you must not include the REV ID. If you search for that HWID, you'll find a match I've got absolutely no clue what's going wrong here. I'm 99% sure that this is either caused by a hardware conflict, or by some minor, unnoticed (unnoticeable) mistake on your behalf. Could you perhaps create a new UWXPCD, with ONLY the DriverPacks slipstreamed: no nLite, no UpdatePacks, nothing. If it still doesn't work then, we can be sure that it's being caused by a hardware conflict/failure.