Possibly; however, the three different systems had different MoBo chip
sets using, in particular, three different SATA RAID0 drivers. I suspect
it is connected to the presence of an extended partition on the drive or
drive array and the arrangement of boot and system disks for each OS. I
have only had it occur with Windows XP and Vista dual boot with both OSs
on the same drive or array.
I did test multiple times with different arrangements using different
partitioning utilities including those on the XP or Vista CD/DVD.
However, I did not do the full set of formal factorial tests and analysis
that would be necessary to isolate the problem.
Tom
MSMVP 1998-2007
Thanks for the info. My setup is is single SATA and single EIDE;
obviously non-raid. All of this action take place on the SATA drive.
XP (primary partiton) and a couple of data (non-OS) logical partiitons
were cloned from and old IDE drive to the SATA
using Acronis TrueImage version 10
then the old EIDE was removed from the system
I tested the SATA drive as it was and all appeared normal.
I then created a partition of unallocated space (another logical
drive)
using XP's disk manager and proceeded to install Vista into it.
All went normally. The only oddity was what looked like garbage on
the screen
right before Vista's boot loader menu. Using the "pause" button on
the keyboard
I was able to freeze and see the messages. It wasn't garbage, it was
an error
talking about incorrect CHS values. (Maybe because of Trueimage?)
I updated the BIOS in attempt to fix it but to no avail.
I then ran Vista's fixboot and fixmbr and problem solved.
I really don't want to have XP and Vista in separate primary
partitions.
I always thought only one primary could be "active" and the other
"hidden"
Is this what you did?