Vista - Installed Virtual PC 2007 and 'lost' a hard drive

I installed a Virtual PC 2007 on the WinXP 64 bit partition of a Mac Pro
computer. On the WinXP 64 before the installation I had C: and D: hard
Drives for 2 physical hard drives (500 gig each). After the sucessful
installation of Virtual PC, the D: hard drive does not work even though it is
reported. The Disk Management (computer management-storage) reports the C:
drive and 3 partitions with no volume information, but with different
statuses: Healthy (EFI System Partition), Healthy (unknown partition) and
Healthy (GPT Protective Partition). I cannot 'roll back' my changes without
affecting the D: hard drive (warning in the system restore procedure). How
can I get the drive D: to function with my data intact and the Virtual PC
working.
Virtual disk information: Dynamically expanding virtual hard disk size
130,557 MB. The total drive space on D: is 500 Gigabytes and drive C: is
another 500 gigabytes.
Virtual Hard Disk version 5.3
The virtual machine file is on drive C: (the boot drive)
Any suggestions?

"Gum" <gum@xxxxxx> wrote in message
news:FED8F970-5484-4A89-8398-02AA2121D132@xxxxxx
Not much help, I'm afraid, but I'm struggling to imagine how installing
Virtual PC could be responsible for this. Virtual PC is just an application,
like Word or Excel. It doesn't do anything at all with the host's boot
sector or partition sector, and it doesn't create new disk partitions.
Ah - have you installed Virtual PC 2004 instead of Virtual PC 2007...? I
can't recall now, but I'm not sure that ever worked properly on 64-bit XP,
especially running on a Mac...

There is a version of VPC 2007 SP1 which, although still a 32-bit
application itself, has 64-bit virtualisation drivers:
http://www.microsoft.com/downloads/d...displaylang=en

That's what you should be installing on a 64-bit host OS. However, I can't
guarantee that this will work on 64-bit Windows running on a Mac - it might,
but I've never tried it. Maybe one of the more experienced MVPs (Bob, Steve)
can confirm this...?
What do you mean by "the virtual machine file"...? The installation of VPC
itself doesn't actually create any virtual machines - you do that through
the VPC console...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

I am also struggling to imagine that although it appears that the drive
problem coincided with the installation. It could be another problem since
in every session is accompanied by windows download fixes and reports on
previous fixes sent to Microsoft. The Mac Pro is based on an intel with a
double quad chip (8 cores) so it is pretty well Windows oriented. My
installation is Virtual PC 2007 and the installation appears to be a 32 bit
installation on this 64 bit machine as it is located in the Program Files
(x86) directory. I couldn't imagine having installed the 32 bit version when
I have a 64 bit version of Virtual PC 2007 on CD. The virtual PC 2007
virtual machine works pretty well and it is easy to set up and configured as
a 32 bit machine.
My reference to the Virtual Machine File is really 2 files comprising the
Virtual machine settings and the 32bit WinXP Hard Disk image.

"Mark Rae [MVP]" wrote:

"Gum" <gum@xxxxxx> wrote in message
news:7BC94591-DEAF-4589-B3FC-A66AB3AA1BF9@xxxxxx
So where are you seeing "Virtual Hard Disk version 5.3"...?
As explained, all versions of Virtual PC are 32-bit applications regardless
of whether they come with the 64-bit virtualisation driver or not:
http://vpc.visualwin.com/ngfaq.aspx#18


--
Mark Rae
ASP.NET MVP
http://www.markrae.net