Same BS with no drivers found when hitting F6 during XP Pro install

computer

Platinum Member
Nov 5, 2000
2,735
2
0
I despise 3rd party controllers. It's always some BS with XP not seeing the HD's on them. This is a Gigabyte GA-8I945P-Pro. No SATA HD's are installed. (The only SATA device is a Plextor 712SA). The two HD's are IDE and are on the GigaRAID VIA IDE connectors and are NOT setup as RAID, they are set as IDE in the BIOS. WD1600JB is the boot drive....well, I'm TRYING to get it the boot drive that is!

Since the WD CD saw the WD1600JB with no problem, and partitioned/formatted it, I though maybe so would XP. But as I expected it can't see the drive. So, I went to the VIA folder on the Gigabyte CD and found the "DriverDisk" folder which is BS. I tried both folders in it (PIDE and RAID) and put the TXTSETUP.OEM file on the floppy both times, hit F6, and I get this crap: File: \RAID\winxp\viamraid.sys caused an unexpected error (1024) at line 2108 in d:\xpclient\base\root\setup\oemdisk.c Yes, Google is full of others with the same problem and of course, no answers!

So I then went to the Gigabyte site and got what they allege "ITE GigaRAID IT8212F (Preinstall driver, press F6 during Windows* setup to read from floppy) " and it's the same crap! Also, as you'd expect from a mobo manufacturer's website, that * you see in the text above has no reference to it!! So who knows what the hell it's for.

I tried a slipstreamed XP + SP2 CD I made and with it I get txtsetup.oem caused an unexpected error (1024) at line 1747 in d:xpsprtm\base\root\setup\oemdisk.c, so it's basically the same thing.

So can anyone PUH-LEEZE tell me how the hell are you supposed to get XP on this HD??
Thanks.
 

o1die

Diamond Member
Jul 8, 2001
4,785
0
71
Check your bios settings. Enable everything pertaining to raid and ide, and check your boot order settings. I installed my raid driver, even though I don't use raid, and my board posts faster. Maybe you don't need the via driver for your ide, or you failed to copy the entire file to the floppy.
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Thanks for the reply. It (GigaRAID) controller is enabled, and it's set to IDE mode or ATA mode, whatever the non-RAID mode is.

This phenomenal. Now, I'm getting File \WINXP\iteraid.sys caused an unexpected error (4096) at line 2108 in d:\xpclient\base\root\setup\oemdisk.c and "Press any key to continue". F*** this ****.

It MUST have a driver. Like I said, without it XP can't install because it doesn't see any HD's. Boot order is OK, although I'm not sure how that would matter as long as it's booting from the optical drive for the XP CD.
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Earlier it DID go through the setup, but stopped at an error that it couldn't read file from the disk, but didn't say which disk. The file was ITERAID.inf which is on the floppy, but I don't know if it was trying to read from it, or from the HD once it was copied to it. I restarted and did it again, and that's when it gave that last error I mentioned in my last post.
 

tcsenter

Lifer
Sep 7, 2001
18,828
490
126
I despise 3rd party controllers. It's always some BS with XP not seeing the HD's on them. This is a Gigabyte GA-8I945P-Pro. No SATA HD's are installed. (The only SATA device is a Plextor 712SA). The two HD's are IDE and are on the GigaRAID VIA IDE connectors and are NOT setup as RAID, they are set as IDE in the BIOS. WD1600JB is the boot drive....well, I'm TRYING to get it the boot drive that is!
First, there are no VIA controllers on the board so trying to use viamraid.sys or other VIA drivers will yield predictable results (it no worky).

Second, your board uses Intel 945P/ICH7R chipset. The board has one IDE connector supporting two ATA/IDE devices through the Intel ICH7 labeled IDE1. Plug your hard drives there, not through IDE2/3 (which is the ITE 8212F GigaRAID controller). Disable everything RAID in BIOS, or select IDE/ATA mode for any RAID controllers, since it seems you do not want a RAID setup at this time.

Ideally, you shouldn't need any drivers for the ITE controller to install XP, but you might have to use a floppy disk for the Intel SATA controller to properly support your Plextor. You can download the Intel Floppy Creation Utility for Intel® Matrix Storage Manager, which will create a floppy to use with the F6 prompt.

Am I correct to infer that a RAID setup isn't your objective at this time?
 

Juno

Lifer
Jul 3, 2004
12,574
0
76
i had same problem.

you need to install drivers during windows setup. press f6 then it'll appear if you want to install drivers (just to make sure your floppy drive with sata drivers on disk is in use), choose S or enter to install drivers. After it is installed, you'll see your SATA hard drives on the list.
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Yes, I didn't want to use RAID. I didn't mean to say "VIA". ;)

I found the problem, and it was this crappy floppy drive media reader combo on MY OWN PC where I was making the floppy. The media reader portion of it is great, but the floppy portion of it has NEVER worked properly. Only certain brands of floppies will read in it, and, it says many times that it can't format the media, or media not present, etc. This time, it gave no complaints and it formatted & put the controller drivers on the floppy with not a single complaint! However it somehow screwed up the floppy. I did it on another PC and I had no problems.

BTW, It's a Mitsumi FA404 floppy/media reader combo, so I warn others to stay away from these for floppy drive use.
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Originally posted by: jewno
i had same problem.

you need to install drivers during windows setup. press f6 then it'll appear if you want to install drivers (just to make sure your floppy drive with sata drivers on disk is in use), choose S or enter to install drivers. After it is installed, you'll see your SATA hard drives on the list.

Hmm, I never got an email regarding your reply and I just now saw it. Thanks, but like I mentioned, that's what I did. ;) I went through that whole process and that's when it gave the error. I mentioned in my last post (above) what the problem was.