Firstly, THANKS for all you do! I would have never gotten this far with out your awesome posts.
I just set up a raid 0 system with 2 xWD Caviar Black 640 gb hd's. Spec's as follows:
Vista premium 64
AMD Phenom Quad Core 9550 2.2 GHz
Asus m3a78-emh hdmi mATX motherboard
8gb DDR2 800Mhz PC6400 - 2GB x 4
Sata 20x DVD
Fantom 1TB eSata external HD through jmicron esata - raid adaptor
System works perfectly unless Fantom (G drive is hooked up and turned on. When Fantom drive is on the boot hangs when it is looking for the boot drive. Seems like it is wanting to find boot info on that drive. If I start the system first and then attach the Fantom drive via USB (plug and play) everything works fine.
Did I miss something in the bios? and is it in the mobo bios or the raid bios? Maybe a conflict between the jmicron bios and mobo bios? I realy need to get this working through the esata board.
ALSO, I tried to partition the raid array down to c: = 80 gbs with remainder going to secondary volume (F Windows would not let me shrink the c: drive down to less than 1 gig? How can I get it down to 80 or 100 gigs?
Yes, I am a nooB and thanks in advance!
More about :partitioning external back raid system
I believe your guess that the machine is trying to boot from the Fantom drive is correct. In the BIOS of your motherboard, under "Boot/Boot Device Priority" see if it gives you the option of specifying _which_ hard drive to boot from. If it doesn't, you may need to connect the drive after the machine has booted. Your eSata adapter should (hopefully) support AHCI which would allow you to hotplug your Fantom using the eSata interface.
As far as problem #2, your numbers don't make any sense.
Windows won't let you shrink the C: drive down to less than 1GB simply because Windows needs more than that just for itself.
80GB or 100GB should be just fine. My Windows partitions are less than half those sizes and I've never encountered a problem.
There are quite a number of "specialized" utilities that don't work on 64bit Windows installations. That's another reason, I setup dual boot systems, one of the installations being a 32bit Windows XP, just for occasions like that.