Thanks, NM. That did the trick.
Also, FYI, I am kind of hard headed and did not like the system refusing to
boot with a new 2nd SCSI hard drive. So I could not help trying to mess
around with it and found a "work around" for my problem. VMware considered
the new drive (which it assumed was the boot drive) to be unconfigured so it
would not even load - no way to get to the BIOS settings. But I discovered
this work around: Create two new SCSI drives. Attempt to start the VM. It
would fail with an error saying that the first of the new SCSI drives that I
added was unconfigured and the VM could not start. THen, delete that drive,
leaving the 2nd new SCSI drive that I had added. Start the VM again.
Voila! It booted just fine (from the original boot drive).. The new drive
then appeared as a new unformatted drive which I could format etc in the
Computer Management console. So, I have managed to get a 2nd SCSI drive
working, though in a very "round-about" way.
Don't ask me why it worked. I just like the product. I'm no expert in its
design.
RAB
Post by NMPost by rabI've attempted to add a hard disk to a W2K Pro guest VM but VMware
assumes that the new hard drive is the boot drive and fails to boot.
How do I configure the original virtual hard drive as the boot drive
for the guest OS. (I am running VMware v4.5.2 on a W2K Pro host.)
Thanks, RAB
Did it make it a SCSI disk? If so, make sure you pick IDE and set it to be
a Primary Slave (IDE 0:1)