View Single Post
  #20  
Old April 22nd 17, 01:03 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Virtual XP won't start

Paul wrote:
Roger Mills wrote:


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro laptop
and she uses the Virtual XP Machine on it. Her data is all on an
external USB drive, so we're not desperate to get at the data on the
virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then
cloned onto an SSD. I think the HDD is still intact in a cupboard back
at home. I'm tempted to copy all of the virtual machine files from
that onto the SSD, on the assumptions that the files on the SSD have
somehow got corrupted. Do you think that might work?


The issue with cloning the contents of the VHD file, is
"activation". I've occasionally attempted to move OSes protected
by activation, and was met by the OS "freezing", even though
it had drivers suitable to finish booting. To my mind,
the experiment is worth doing, but without an absolute
guarantee you'll benefit from it.

The idea of moving the OS to physical level, is in the
hope it's more visible during boot (i.e. Safe Mode, F8,
enable Boot Logging, or whatever). Just so you can get
a hint as to what is busted.

While Windows Virtual PC is "inflating" the .vsv file when
the VM runs, you don't have an interface to watch. That's
because Terminal Services (the chosen display method)
is not available until the thing is running. If you were
to run the same VM on VPC2007, and it wasn't using
Terminal Services, you might get to see more of the
boot sequence.

These are the only ideas that come to mind. Having watched
it start, I cannot think of anything else to try (due to
the lack of visibility during the boot phase).

The WinXP Mode VM, also runs on VMWare. VMWare had a special
deal with Microsoft, where they agreed to enforce the usage
requirement (could only boot the VM is Win7Pro or better
was the Host), so that's another way to do it. Only a single
version of VMWare supported this. So if say, VMWare today
was Version 7, maybe it was Version 4 or so that supported
WinXP Mode guests. I'm not a VMWare user, so haven't
tried that, and I don't even have a VMWare setup here.

And the purpose of any experiment, is "observation" and figuring
out what subsystem on WinXPMode is busted. As the current running
environment is "useless" for debugging.

I had high hopes you had a hibernating machine, and simply
deleting the .vsv would be enough... Oh, well.

Paul


Well forget this. It seems to start a brand new WinXP Mode
machine, and doesn't just "import" the VHD you've already got.

http://www.duxburysystems.com/docume...ots/vmware.htm

Even though you can get the player, it's not going to help.

http://www.oldapps.com/VMware_player...=6994?download

Paul
Ads