Both drives are SATA 1.5 drives. Both drives are boot drives. Their differ only in drive speed (5400 vs 7200 rpm).
Drive 1 has dual boot options to RHEL 5.1 or Other OS (default is Other OS if timed out). If other OS is chosen (or timed out), it then load Windows OS loader to allow multi-boot options to either WinXP Pro (default if timed out) or Windows Server 2003 Enterprise Edition X64 w/SP2. All OSes are in English, no localization.
RHEL 5.1 is the latest, up-to-date RedHat Enterprise Linux Server (RHEL)as of today 13 Jan 2008 (Western solar calendar/Gregorian calendar). This is NOT a free Linux distro. This is not the free Fedora Linux distro either. I have other means to mount UNIX drives in Windows and I can mount and read Windows partitions on RHEL 5.1. I can see, read, and write data from RHEL onto my Windows partitions as long as the partitions are from the same SATA drive.
Drive 2 has default boot to Windows Vista Ultimate. It has remaining spaces that I want to use as DataStores for my Vmware Virtual machines, which runs on VMware WorkStation which in turn runs on RHEL 5.1 on drive 1. Furthermore, I want to be able to share data in my DATA1 partition in drive 1 with my DATA2 partition in my second drive (both are formatted to NTFS 3.1 and is compatible across XP Pro, W2K3, and Vista)
Right now if I booted to any aforementioned Windows version, Windows sees only the drive it's booted from. It can't sees the 2nd drive. This is at the hardware level, not at the OS level. It has nothing to do with mounting partition. It has to do with with the SATA interface as implemented by Dell which I am currently still in learning mode. I had no problem with a similar setup on another NB when both drives are ATA drives; just with the case where both drives are SATA.
I've tried searches on Dell website and googled but can't find much relevant info on this subject, and on the internal working of the SATA controller.
The SATA drives comes with a jumper, which according to Seagate is used only for servicing only. I've tested the 2 cases:
a. Both drives without jumper.
b. Drive 1 (int) w/o jumper and drive 2 (expansion bay) with jumper.
The tests were unsuccessful in making Windows on one drive sees the other hard drive; even with a rescan.
Thank you very much.
Regards.