Vista - 32-bit machines don't work on 64-bit OS?

I just set up a new computer with 64-bit Vista and copied some existing
virtual machine files from my old 32-bit XP computer. VPC won't open them,
with an error about possibly a "wrong version".

Is this a 32-bit/64-bit issue? Or anything that I can fix without rebuilding
the virtual machines from scratch? Thanks!

-Doug

"douglasl" <douglasl@xxxxxx> wrote in message
news:B3C6C83A-7BEB-47B1-802A-08F37ED0A13F@xxxxxx

My guess is it is the VM additions. These are drivers, which would be 32
bit drivers from your old computer, that won't work with your new 64 bit OS.
I would try un-installing the VM additions in the 32 bit OS, then try them
again in 64 bit Vista.

On Sun, 15 Feb 2009 19:47:00 -0800, douglasl
<douglasl@xxxxxx> wrote:
did you move the VMs while they were in a Saved State or shut down? If
you moved them over in a Saved State this will happen. You should be
able to delete the saved state file, .vsv and boot the VM then.

Otherwise, go back to the original machine, completely shut down (turn
off) the VMs and recopy them.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

Actually the additions are identical between the 64-bit and 32-bit
versions of VPC. (The additions only run in the VM and the VM is
32-bit only...)

I have no idea why he might be getting a "wrong version" error, I've
never seen that. I'd have to see just where he's getting that message
and if there is any other text to it.

--
Bob Comer



On Sun, 15 Feb 2009 23:09:07 -0500, "Bob Campbell" <bob@xxxxxx>
wrote:

"Robert Comer" <bobcomer-removeme-@xxxxxx> wrote in message
news:3uphp4tnuqohuoo5384efp39dv1hs5ulrd@xxxxxxWell, like I said, I was guessing! :-)

But yeah, now that you mention it, that makes sense.

Nevermind!

"douglasl" <douglasl@xxxxxx> wrote in message
news:B3C6C83A-7BEB-47B1-802A-08F37ED0A13F@xxxxxx
1) Did you shut the virtual machines down completely before copying them
i.e. didn't leave them in a saved state?

2) Did you have VPC 2004 or 2007 on the XP host?

3) On the Vista host machine, did you definitely install the version of VPC
2007 SP1 specifically targeted at 64-bit hosts?

4) Is the CPU on the Vista host machine substantially different from the CPU
on the XP host machine i.e. AMD etc...?


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

No prob. <g>

I think Steve has it right, the saved state issue. No way to go
across machines like that.

--
Bob Comer



On Sun, 15 Feb 2009 23:31:31 -0500, "Bob Campbell" <bob@xxxxxx>
wrote:

"Bob Campbell" <bob@xxxxxx> wrote in message
news:ZYSdnccpSaZ3ewXUnZ2dnUVZ_uWdnZ2d@xxxxxx
Not possible... The VM Additions are added to the OS running in the guest
and, as such, can only ever be 32-bit - the host OS is irrelevant...

If Steve's thought about the guests being in saved state and not shut down
properly is not the problem, then the only other thing I can think of is
that the CPU on the Vista host is substantially different from that on the
XP host - I've known that to cause issues in the past, but I don't recall
ever seeing a message complaining of a wrong version...


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

I'm sure it's the Saved State issue, although I can't go fix it right this
instant. In fact I think the error message hinted at that possibility, but I
was too frazzled to put 2 + 2 together.

The pressure of moving the Significant Other's entire home-based business to
a new computer, to a recurring chorus of "I KNOW something's not going to
work!", had overwhelmed me. :-)

Thanks!

-Doug

On Mon, 16 Feb 2009 06:32:02 -0800, douglasl
<douglasl@xxxxxx> wrote:
If it is just the "saved state" then you can just erase the vsv file
and then start the guest. It would be as if you had pulled the power
line on the running machine, no more.

But if you are using undo disks, then maybe these are not compatible
and in this case you should be more careful because if you erase the
associated vud file you lose everything since the last commit you have
done....

--

Bo Berglund (Sweden)