From what Scott described to me last night, it sounds like he was trying, franticly (remember how some karaoke singers can be
), to resolve the problem. He rebooted the system and was planning on going into WINDOWS SAFE MODE and the system wouldn't reboot into Windows.
Next, he rebooted again and this time ended up in the CMOS. At this point he tried to restore the default settings using the listed option. He tried the optimized and the default.
Where I think he got into trouble, and I don't have the RAID card or the Shuttle, is that these default settings do not identify the raid controller as the PRIMARY boot drive.
What I wasn't sure of was this:
1. Are any of the drives connected to an IDE controller that is BUILT onto the motherboard, or
2. Is the raid controller plugged into a PCI slot
If the former, then the CMOS issue should have worked. If the latter, maybe not.
After we tinkered with it for a while, I downloaded the Shuttle manual and reviewed it rather rapidly. Couldn't find any immediate suggestions EXCEPT to list the second boot device (After the floppy) as the SCSI controller (Thereby making it the RAID Device).
Discussion:
Would windows begin to boot and give the options of Safe, last known configuration, etc. if the system was not correctly set up in the CMOS? Maybe, maybe not.
I think he may have done something to WINDOWS and now it won't reboot. Does the Shuttle system ship with a restore disk? Have you considered building a restore disk? Bryan, PM me if you want some ideas on developing that, in a situation like this it might be useful.
The easiest solution I think we may come across is a repair of Windows, however, Scott may loose the functionality of HOSTER for a short spell and have to reload JUST the program. His songs should be reserved elsewhere on the HDD.
ALL that being said, isn't the theory behind RAID that the two drives are identical in case of failure? Wouldn't this be a failure that may need to be addressed?
Just adding my knowledge of the situation and some direction