lock please - fixed it.

[dmk11]

I have a HD with my WinXP.

I just got 2 60gb HD with Promise Fasttrack controller.

put both HD on the promise, defined an array, everything is good so far.

booted to WinXP (on my old HD) and XP can't see the array whatsoever. Latest driver of the promise card is installed on WinXP and it can see the card fine from device manager.. but I don't see the HD. Not even under disk management tool built-in..

So I booted to a win98 bootdisk and ran FDISK. FDISK only sees it as a 48gb HD. at any rate, I made a 10gb primary partition and then formatted it /s. I even tried booting to it and it works, got me to the DOS prompt.

Then I boot again with my old HD WinXP. and WinXP still can't see this raid array and not the 10gb partition i just made.

what am i doing wrong?? I thought once you define the raid array, winxp should just treat it as one new big HD.

 

[dmk11]

New Info

When I put both HDs on the same IDE channel on the RAID card, WinXP detected it! I jumpered both HDs as "cable select".

Then I tried moving it back to one HD on one channel. WHen I jumpered the HD as Master, no array detected. When I jumpered as cable select, RAID controller sees it ok, but WinXP don't. When I remove all the jumpers (Master - Single), RAID controller sees it but once again, WinXP doesn't.

Conclusion: WinXP sucks...

Tricks you can suggest to me to unsuck WinXP?

 

[Willoughbyva]

I'm not much on RAID stuff, but if you list the Promise card and the drivers you are using someone might be able to help you. Might also want to list your system specs.

 

[dmk11]

Originally posted by: Willoughbyva
I'm not much on RAID stuff, but if you list the Promise card and the drivers you are using someone might be able to help you. Might also want to list your system specs.

I'm using Promise FastTrack using newest BIOS 2.00.0.24 and newest WinXP driver 2.00.0.26.
my system is a Dell 4550, P4 2.4ghz, 256mb
2 HDs in RAID is WD 60gb 7200rpm ATA100
The HD I have WinXP on is a WD 200gb 7200rpm 8mb.

UPDATE:
I fixed it. It takes me removing the drivers on WinXP and reinstalling it. weird.