Okay, I've got a brand new Intel DQ35MP desktop mobo, which comes with an ICH9(DQ) with RAID capability. The SilverStone case I'm using only allows two internal HDs and I want them using RAID 0 for performance. I setup the RAID 0 volumes (coincidentally 2) in the BIOS, then I booted into the normal XP Pro install. I pressed F6 to specify that I need to load the RAID driver, which worked fine, then when prompted I pressed "S", hit "Enter" to select the floppy, then I selected the appropriate entry, which also worked fine.

Then the install continued until I get a prompt saying: "Insert the disk labeled: 'Intel Matrix Storage Management driver' into Drive A: -- Press Enter when ready". Naturally, since the driver floppy I used earlier was still in the drive (as the docs say to do), I just pressed "Enter" again.

No dice! It doesn't look like it even tried (the floppy drive's light doesn't flash or light at all). And what's all that about a floppy -- a floppy! -- with such a long label as: 'Intel Matrix Storage Management driver'? You can't label a Windows floppy that way, right? But what else could it mean? Surely not some kind of hand-written label, right?

I've tried several times and it always sticks right there and won't go forward no matter what. I've searched the Intel RAID driver page for a second floppy image but I can find only the one (identical to the one that came in the mobo box).

I'm thinking that there's an error in one of the Intel RAID install files that makes it think the XP installer system want something it shouldn't be asking for.

What's going on and how do I solve this problem?


p.s.: One thing that occurred to me is based on something I used to do in the old days of Win98SE: I copied all(?) of the files from the install CD onto the hard disk and somehow ran the install from there (I don't remember how). That way I could just copy the files to the HD manually. Can I do something like that with XP Pro (SP2)? If so, how? Where would I put the RAID driver files it wants to copy but can't?

I am familiar with RAID setup but not with that particular Intel M/B so if it follows most procedures leaving you at the mercy of only being able to install the drivers through the A:\ drive in WinXP [Addressing your p.s.], after the initial driver file loading remove the Floppy Disk, and reinsert it when it asks for it a second time, and if there are more than one set of drivers on the disk, like say the RAID drivers and also a mass Storage driver it needs both those drivers, so install both or all thats on the disk.

If it doesn't need it, it won't install it, but if its not available to the setup it stops, hope this helps you out.

If what 4ryan6 says "reinsert the F6 Disk does not work. Try down loadinf/readme for the matrix storage manager for your board on the Intel web site.
her is an alternate site that you can try:
http://downloadcenter.intel.com/De [...] 1&lang=eng

It would worth double checking what the entry is you selected for the RAID driver in Windows setup. I had a similar problem to yours, I would choose the driver and then it would ask me to insert the floppy disk a little while later. This had never happened to me before so I was stumped. I tried recopying the drivers to the floppy on another computer with no luck. On one of my retries a few hours later I noticed I had been choosing the Windows 2000 driver rather than the XP one. I chose the XP one (while cursing profusely) and setup continued without a hitch.

Thank you for your reply. Please forgive me, but I'm afraid I don't quite follow what you're saying.

The mobo came with the appropriate RAID driver floppy from Intel (I downloaded the latest and created a new floppy to see if that helped, which it didn't). So I have only the one floppy; i.e., I don't have one for the first part and another for the second part.

Here's what happens: I press F6 at the start and then a few moments later, when prompted, I carefully selected the ICH9 driver entry (there was only one entry for the ICH9R -- the others were for other chipsets). The installer read the driver files and was perfectly happy. I left the floppy in the drive. Several minutes later, it came time to copy all the driver files to the hard disk (the "second part" I just mentioned above). That's when it asked for this floppy in drive A: labeled "Intel Matrix Storage Management driver". Since the floppy was still in the drive, I just pressed "enter". When I did, it just kept asking for for the same thing, over and over again. I tried removing the floppy then re-inserting it, but it made no difference. It wanted a floppy in drive A: labeled "Intel Matrix Storage Management driver" and it was going to have it or else it was going to quit. No other options.

With that clarification, would you mind trying to rephrase your suggestion? Again, I apologize for not being able to understand quite what you were saying.

ambush;

I just read the setup too from Intel's site manual d9004204_en.pdf,

sound s like the bios is right but i noticed the 'intel management engine [MEI_AMT_allOS_330.1086_PV.zip]' as maybe one file source and the other which you have [raid intel matrix storage system driver].

Lastly you could setup the system up using one SATA then adding another using 'raid ready' controls later pg 72 of manual.

As for my self, I'm using ASUS P5K E8400 non raid. Multiple drives SATA/IDE.

Good Luck.

I did download what I have from there, but thanks for the note. I've been very careful to read every single readme file and other document relating to this situation and follow all instructions, but I still get stuck every time no matter which version of the "Intel Matrix Storage Technology RAID/AHCI Driver" floppy I use.

I'm going to relate the new information I obtained from Intel over the phone in a fresh (non-reply) post of my own as soon as I finish responding to all the replies already here.

Thanks for the tip, but I carefully chose the correct driver floppy version for 32-bit XP. Note that it works fine during the first phase and doesn't get stuck until I get to the second phase.

As I wrote in a reply just a few moments ago, I'm going to relate the new information I obtained from Intel over the phone in a fresh (non-reply) post of my own as soon as I finish responding to all the replies already here.

Latest info from Intel!

Okay, I was on the phone to Intel tech support earlier tonight for an hour or so trying to work this out. After some lengthy discussions, he decided he would walk me through the procedure over the phone to make sure I was doing what he thought I should do. It didn't go as either of us thought it would, though!

After pressing F6 and inserting the floppy with the latest version of the drivers I downloaded from Intel's site, the Intel guy had me choose some OTHER driver entry than the one I'd been selecting. The one I'd been choosing was the only one that listed the ICH9R alone, but he wanted me to select the one that said "ICH8R/ICH9R/ICH10R" instead. I did as he asked, but after a few minutes it crashed with a BSOD! So we started from the beginning again and this time he had me choose yet a different entry (one I would never have chosen on my own, since it just didn't look right to me for the chipset on this mobo) that also listed the ICH8M. I did as he asked and a few minutes later, it crashed with BSOD, too!

Then, instead of choosing the driver entry I'd always used, which was more successful because it did NOT crash, he curiously decided the fault must lie in my USB floppy drive! He sent me to the Microsoft XP hardware compatibility list and, sure enough, the Sony USB floppy drive I'd been using was not on the approved compatibility list. I still think that idea's utter BS, but I ordered one overnight that's on the approved list anyway ($50 total with overnight shipping! Yikes!). I'd wager a bunch that it doesn't make any difference at all, in which case I'm going to sue Intel in small claims court to get my money back. When the drive comes in, I'll report back on what happens.

. . .

But callahs's post sent me down a different path at Intel's site looking to make sure I had the right stuff, and I found something along that different path I hadn't seen before. At [url=http://downloadcenter.intel.com/Detail_Desc.aspx?agr=N&Inst=Yes&ProductID=2784&DwnldID=15251&strOSs=44&OSFullName=Windows*%20XP%20Professional&lang=eng]thispage, I found these words at the top: "Installs the Intel® Matrix Storage Technology (RAID) driver version 7.8.0.1012 for Intel® Desktop Boards. Download the driver and one of the following F6 Driver Diskettes (depending on your operating system):..."

Since there's ONLY F6 floppy downloads there (one for 32-bit Windows only (which I used), one for 32-bit AND 64-bit Windows, and one for 64-bit Windows only), what else is it telling me to download? It seems to me that it just means just the same RAID driver that comes with the Intel multi-driver CD for this mobo that you install once Windows is installed and running, but I suppose it's talking about something else. Any ideas?

I'm still stuck.

First a question, Did you already config your Raid 0 in Bios (You probably did, but need to verify) and make sure the driver you are loading matches this. 2nd question, your XP install - what service pack does it include - Needs at least SP1, if not 2.

I think your FFD, even though not listed is OK.

Wish I could remember back a year and a Half as I did a XP Pro install and I recieved the same promps and Had no problem using XP pro w/Sp2. Ihave the Gigabyte DQ6 and Looked at my install files. The file "Matrix storage manager" have the same files as the F6 floppy files.

Last week I loaded XP pro w/SP2 on to my new laptop (no Floopy. Whate I did was using nlite (an easy to use program free on internet) and slip streamed SP3 and the F6 floopy and then created a ISO disk image. Then burned this to a CD using the ISO mode. Worked like a charm, just skipped the F6 option during install. If you have use of a 2nd computer (I assume you do since your posting) This is a much better route any way.

Thanks for sticking with me, RetiredCheif!

Yes, I did configure two RAID 0 volumes in the BIOS and I did set the SATA mode to <RAID>. And yes, this XP Pro CD already contains SP2 (I bought it fairly recently).

I agree entirely with your belief that the fault is NOT the USB FDD. I'm going to sue Intel in small claims to get my money back if -- as I expect -- it doesn't make any difference.

I've tried nLite several times for this issue already, but I couldn't get it to work. I could really use your or someone's expert help with this. I tried some experiments that all end the same way as what follows. The next two attempts were deliberately very, very simple:

(1) Left all settings alone (in their default state, without importing any previous settings or anything else) except to add drivers (the ones in question). Result of installation with created ISO: It runs through everything without any user interaction and then aborts with an error message saying something like "Setup could not find any hard drives on your system".

(2) Left all settings alone as above except that I went into the "Unattended" option trying to find a setting that told it to NOT do an unattended setup so that I could manually specify the RAID volume where XP should be installed. No dice -- there is no such option! There IS an option labeled "GUI attended", but that's highly misleading, because what it really does in ONLY allow normal user interaction in the "final stage of the installation", which is much too late! Result: "Setup could not find any hard drives on your system".

How incredibly frustrating!

///////////I press F6 at the start and then a few moments later, when prompted, I carefully selected the ICH9 driver entry (there was only one entry for the ICH9R -- the others were for other chipsets).>>>>>>>>[So the USB Floppy Drive is actually loading the drivers]

//////////The installer read the driver files and was perfectly happy.>>>>>>>>>>[It accepts what you give it right or wrong]


//////////Intel Matrix Storage Management driver>>>>>>>>>>>[Be absolutely positive that driver is also on the Floppy Disk and initially load it too]


//////////Since the floppy was still in the drive, I just pressed "enter>>>>>>>>>>[It won't ask for anything later if you've given it everything from the beginning, I've done installs and loaded all the drivers on the disk initially and it never asked for the drivers a second time]


Even though you've been told that USB Floppy wouldn't work, how have you been able to load the initial drivers if it isn't working?


So back to my suggestion;

If you get to the first initial driver loading screen with the USB Floppy Drive, load every driver thats available on that disk, you can only select and load 1 driver in the list at a time, with I believe if I remember correctly the Press S to load additional drivers, load all the drivers initially, when the loading of the drivers is completed you exit the F6 feature and XP continues the installation remove the floppy from the floppy drive, if it asks you to reinsert it later on, its probably looking for something you didn't give it to start with.

Just because you make the drivers available to WinXPs setup by loading them, doesn't mean XP will use them all, it will use what it needs but if 1 file it needs is missing it will stop every time.

I've run into this exact same problem before and my USB external floppy is a Smartdisk also not listed with the MSFT F6 article, but loading all the drivers on the disk initially worked.

I purposely bought my USB Floppy speciffically for loading the F6 drivers on machines I worked on, that did not have a floppy drive.

USB External Floppy Drives are expensive, you can buy 3 standard Floppy Drives to 1 USB External Floppy Drive, remove the side cover and hook up a temp regular floppy would be a lot cheaper route, but if the setup requires all the files on the floppy disk, you're back in the same situation.

Try loading every file on that floppy disk from the very beginning and see what happens.

Just throwing this out there, but I also have a RAID 0 setup on my new PC. When I first built it, I threw XP on it until I could afford Vista. Now, I have a different board and chipset (eVGA 780i mobo) but I still needed to install the RAID drivers via F6 (something I didn't need to do with Vista) and as you'd expect, it asked me for the disk. I installed two different drivers as they were both marked with "Required" at the end.

It accepted the drivers, formatted the array and then proceded to install. At some point during the installation, however, it asked for the driver floppy again... but unlike your issue, it worked fine and continued on it's merry way. So it's not unusual for XP to ask for the disk a second time... but it is unusual that it would work the first time and not the second.

Did your motherboard's CD come with a utility to create the driver disk? My mobo came with a floppy already... so I didn't have to worry about creating it... but I'm wondering if the utility on the CD would work better than the ones you're downloading.

If setup is not finding your harddrive then you have a mismatch between the F6 driver loaded and chipset or the raid selection in your BIOS..
And your Bios has not enabled AHCI (This gave me a problem the 1st time.)

If we can get this straight, we can use the Floppy F6, or the nlite route.

I would start from sctatch. Remove your raid 0 array. then remake your raid 0 array.
I do not use unattended install of an operating system. start over with nlite. Recopy your installation disk (Gets read of what nlite has done) Restart nlite, find/load your xp installation. Select integrate driver. Navigate to "insert" select single driver Go to your "F6" directory and should show somethink like "iaachi" and 'iastor". select "iastor" . This should be the list to select from. For my DQ6 I select "82801 HR/HH/HO SATA Raid Controller (Desktop ICHR8R) MAKE sure chipset matches yours.

Have to go for now, but tomarrow when I boot, I take a look at my BIOS.

Yes, which is why I do NOT believe Intel when they tell me that the problem is due to the fact that my Sony USB floppy drive in not on the MS Windows XP Hardware Compatibility List. The drive seemed to be working perfectly, even though I still have the problem.

Not true. Very early on, I accidentally had the wrong floppy in the drive and it rejected it.

I am indeed absolutely positive. Intel has three and ONLY three downloads for the latest version of the F6 floppy: one for only 32-bit Windows (which is the one I used), one for both 32-bit and 64-bit versions of Windows, and one for only 64-bit version of Windows. I absolutely have the right one.

But that's the whole problem! That's what I'm complaining about! That's why I created this thread. I agree that it should NOT ask this, but it DOES anyway and it doesn't accept anything I give it, not even the same floppy that was absolutely correct in the first phase.

I agree entirely, as I said above.

I've done that every time.

Correct. There are two drivers on the floppy, and I've always selected both.

Correct. That's what I've done every time.

I've thought that many, many times, but there's nothing else suitable on the Intel site and when I called Intel they told me that I only need the F6 floppy I already have. The rest needs to be installed under Windows once the installation is complete.

But Intel's site only provides the single floppy contents I already have. Personally, I strongly feel that there's a coding error in one of the files on that floppy AS IT COMES FROM INTEL that erroneously asks the installation procedure to ask for something it SHOULD NOT.

Again, I agree with your thinking on that, but Intel won't help me until I use a USB floppy that's on the Windows HCL. I'll be able to do that sometime Wednesday, June 11. I'll connect it and call them and we'll try it again.

Thanks, Zoron, for the good info!

The mobo did indeed come with a F6 RAID floppy already created. I tried that first and got the problem I described in my OP, so I downloaded the latest version and created my own floppy with those files. When I compare the contents of the two, the number and names of the files are identical, although the dates are different as you would expect.

So I'm still stumped. I'