Hello,

I have an Intel C2D E6600 CPU installed on an Asus P5W DH Deluxe
motherboard. I recently installed Vista Home Premium (32bit) with a hard
drive configuration of one Western Digital 10k SATA drive (for system and
application files) and two Seagate 320gig SATA2 drives. I had a spare SCSI
Fujitsu 10K 36gig drive (I connected it to a LSI SCSI adapter), so I thought
that I would configure a dual boot system with Windows XP and Vista - one OS
on each 10K drive. I did not have much success with getting the dual boot
function to work. However, I was able to install Vista on the 10K Fujitsu
SCSI drive and, provided the Fujitsu was set as the boot drive in the
motherboard's bios, I was able to boot into Vista. If I set the 10K SATA
drive as the boot device in the bios, I was also able to then boot into XP.

When running Vista with this configuration, I noted that the Windows
Experience Index was rated at 5.6. I guess if I persevered with this
configuration I would have been able to get the dual boot function to work
(I had used VistaBoot Pro). Anyway, I thought that if both drives were on
the same interface, dual booting would be easier to achieve. So I took out
the 10K SATA drive and replaced it with a 36gig (10K) IBM SCSI drive
configured off the same SCSI PCI adapter. Both drives have seperate SCSI
IDs and are on the same channel with an active terminator at the end of the
connecting SCSI cable. I was able to install Win XP on the replacement
drive (IBM SCSI) and eventually was able to get the PC to dual boot to Vista
and XP (Vista being the default OS).

Now after all that rambling, I was surprised to see that the Windows
Experience Index, with this configuration, drop to 4.7(being the primary
hard disk reading)! Considering that both drives are 10K drives as well as
being SCSI (which I though was the faster interface compared to IDE and
SATA), I am stumped as to why this is so.

Would the installation of the PCI SCSI card itself which slows down the boot
process have anything to do with this drop in performance?

Thank you,

Shane