Forum Home
Press F1
Thread ID: 22398	2002-07-20 04:21:00	Gigabyte GA7VRXP & RAID troubles...	Erin Salmon (626)	Press F1

Post ID	Timestamp	Content	User
63730	2002-07-20 04:21:00	Hi, Never before had problems with this board, but now I can't get the RAID array up and running so WinXP can detect it. The system is an AthlonXP 2200+, 1.5GB DDR, 2x 60GB 7200rpm ATA133 HDDs, with the GA7VRXP motherboard... According to gigabyte, I need to copy the fasttrack and ideraid controller drivers from the MB CD to a floppy drive, which I have done, but Windows XP's setup program reads the files, and mis-labels the controllers as being for SCSI drives, and calls them the wrong thing. This then generates an error. DOS detects the drives as a singel 120GB partition, as it was set up, but windows will not... Any ideas? Thanks, Erin	Erin Salmon (626)
63731	2002-07-20 05:53:00	XP will likely always see the controller as a SCSI controller. With earlier Fasttrak controllers and windows 2000 I've had to remove a line from one of the windows driver INF files, to prevent it from detecting the controller as the wrong sort of device (a regular IDE controller with 2 disks, not a SCSI device with one array disk). Are you pressing F6 during the setup process to give XP the drivers on the floppy? If so then it sounds likt the drivers on the floppy may be wrong or out of date perhaps.	BIFF (1)
63732	2002-07-20 06:47:00	Hi, That was the conclusion I was coming to. Yes, I am pressing F6, but when it gets the drivers from the floppy disk, it calls them: WinXP Promise MBFasttrak something something... And: WinXP Promise SBFasttrak something something... The Manual on the CD has names for the drivers which are different from these, and do not have the MB/SB bits... Does anyone have the correct driver files? Thanks, Erin	Erin Salmon (626)
63733	2002-07-20 22:08:00	Have you downloaded the latest from the Gigabyte website, rather than using the ones on the CD? If so did it work?	BIFF (1)
63734	2002-07-21 01:31:00	Hi, The only applicable drivers on the website are for windows, once it has been loaded. At least, they were the only ones I could find. Is there a shortcut around this that could be made by say, installing Windows 98 first, then upgrading? Or installing windows on another HDD, then copying it across? Thanks, Erin	Erin Salmon (626)
63735	2002-07-21 02:55:00	I'd grab this file: ftp.gigabyte.com.tw When unzipped I'd take the contents of the Ideraid\Driver\WinXP\ folder (3 files) and put them onto the root of the floppy disk. Press F6 as before, give it the disk and it should describe the driver as WinXP FastTrak133-Lite controller Fingers crossed! :) Hope this helps	BIFF (1)
63736	2002-07-21 04:05:00	Hi, Followed those instructions to the line Biff, but the files did exactly the same thing the oens on my CD did... Specifically, the floppy has a selection of drivers, and the Windows XP ones are as follows: WinXP Promise MBFasttrak Lite (TM) Controller WinXP Promise SBFasttrak Lite (TM) Controller Both give the same error: File \WinXP\Fasttrak.sys caused an unexpected error (18) at line 2108 in d:\xpclient\base\boot\setup\oemdisk.c. Press any key to continue. Firstly, how does "MBFasttrak Lite" differ from "SMFasttrak Lite"? If I were to give anyone the two files mentioned in the error, would you be able to do the necessary tinkering? Or is something else wrong? Remember that the drive shows up fine as 120GB in DOS, but WindowsXP's Setup doesn't like it... What's next? Thanks, Erin	Erin Salmon (626)
63737	2002-07-21 04:29:00	I think the "SCSI" identification comes because the RAID system was designed for "real computers". The easy way to handle that in an IDE world was to make IDE disks on RAID controllers look like SCSI drives. Try telling the BIOS that there is NO installed disk. XP is probably wanting to install on the first IDE drive, if the BIOS says there is one. But it can't find it, because the controller "knows" it's a SCSI. If the BIOS says there isn't one, it might look for a SCSI. Sound plausible?	Graham L (2)
63738	2002-07-21 04:43:00	Hi, Is there a possibility that Windows is throwing a tantrum because I am using an OEM copy? What do you think the oemdisk.c file has to do with this? That file is located on the Windows XP CD... Any catch? I'll give your suggestion a go Graham... :) Erin	Erin Salmon (626)
63739	2002-07-21 04:48:00	OEM versions are usually designed to be installed on a new, clean disk. They won't load on a disk which has got Windows already. They have the idea that people might acquire the disks cheap, and use them as upgrades. No-one would do that, would they? ;-)	Graham L (2)
1 2