TeraByte Unlimited

The option to disable the automatic reboot is in the Windows Safe Mode menu. You should then be able to tell what the error is.

Tap F8 on startup and choose to disable automatic reboot, that will show the
BSOD.

If you don't get that far to see a BSOD with automatic reboot enabled
(reboot right when windows come together), it can be a virus in the MBR,
boot to BootIt, cancel setup, go to partition work, view mbr, win7 mbr,
apply.

Also, sometimes when you enable RAID in the BIOS then the windows driver
goes to sync stuff, it messes things up. You can restore with the RAID
configured (I presume you must have had the RAID drivers installed otherwise
windows would BSOD as well).


"GordonM" wrote in message news:[email protected]...

Unfortunately, "last known good configuaration" is no better than the other
options (they all behave in the same way). The boot process doesn't get as
far as the Welcome screen and just goes back to the beginning. I am going
to try a "repair". I hope this works with a RAID confguaration, I don't see
why it shouldn't.

Is there any history of IFW causing this sort of thing (I had just installed
2.62)? I suspect that this was a coincidence.

Gordon

I have decided not to use RAID for the time being. In fact, it may be unnecessary for what I am trying to achieve. The only critical application is the mail server, and it may be adequate to make a daily (or more often) copy of the whole application folder (with the risk of losing a small amount of mail), which includes the IMAP mail store, to another drive (the mail server is a portable app, so I can quickly tranfer it to another machine). I have been doing this daily copy for some time though, since starting to run my own SMTP server, I was looking for ways of increasing reliability. There is also another downside of RAID in that, for most implementatations, it seems impossible to monitor the health of the individual drives in the array. Hence, advance warnings of impending failures are not available.

GordonM