Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Virtual PC / May 2008

Tip: Looking for answers? Try searching our database.

Using VMs created in WPC2004 in VVPC2007

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Turner - 17 May 2008 17:55 GMT
Are there any "gotchas" waiting to get me if I try to open a VM created in
VPC2004 in VPC2007? The VM in question is a Win95 machine, which I believe
is no longer supported in 2007.

The VM additions are already installed on the virtual Win95 machine.
Colin Barnhorst - 17 May 2008 18:19 GMT
You may need to turn of hardware virtualization in the Settings for the vm.

> Are there any "gotchas" waiting to get me if I try to open a VM created in
> VPC2004 in VPC2007? The VM in question is a Win95 machine, which I believe
> is no longer supported in 2007.
>
> The VM additions are already installed on the virtual Win95 machine.
Bo Berglund - 17 May 2008 19:17 GMT
>Are there any "gotchas" waiting to get me if I try to open a VM created in
>VPC2004 in VPC2007? The VM in question is a Win95 machine, which I believe
>is no longer supported in 2007.
>
>The VM additions are already installed on the virtual Win95 machine.

Before you close the guest for the last time in VPC2004 do the
following:
1) Uninstall the additions, they are not compatile to VPC2007
2) Shut it down all the way, saved states are not compatible either
3) If you have undo disks enabled I'd do a commit too because I don't
know if the undo disks might not also have changed between VPC2004 and
VPC2007.

Then when you start it up in VPC2007 as one of your first things,
install the additions from VPC2007.
In some cases additions are not available from VPC2007 (DOS, Win95),
in these cases I'd not do step 1 above because then the VPC2004
additions will at least be better than nothing.

I have a mix of 2004 and 2007 guests and I have both VPC2004 and
VPC2007 installed on my PC and can start either one depending on what
guest I want to run. If you want you can do the same. Just reinstall
VPC2004 after you have installed VPC2007 and specify a different
target folder for VPC2004 than the one suggested.
Since VPC2007 won't install if VPC2004 is on the system you have first
to uninstall VPC2004...

About the "not supported" issue:
Suppoorted does not mean "will not work" it just means that Microsoft
will not support you over the phone if you run into problems with an
unsupported guest in VPC2007. If it ran in VPC2004 it will run in
VPC2007 too.
Colin Barnhorst - 17 May 2008 20:20 GMT
He should be OK with the vmadds installed on a Win95 vm.  Since there is not
a replacement for those adds in VPC 2007 or VPC 2007 SP1 he might want to
try the vm as is first.  I have a test box I use that for but that is
probably not necessary as long as he makes a copy of the vm first so he can
get back to a good copy if needed.

>>Are there any "gotchas" waiting to get me if I try to open a VM created in
>>VPC2004 in VPC2007? The VM in question is a Win95 machine, which I believe
[quoted text clipped - 29 lines]
> unsupported guest in VPC2007. If it ran in VPC2004 it will run in
> VPC2007 too.
Karl E. Peterson - 19 May 2008 20:54 GMT
>>The VM additions are already installed on the virtual Win95 machine.
>>
> Before you close the guest for the last time in VPC2004 do the
> following:
> 1) Uninstall the additions, they are not compatile to VPC2007

Why do you say that?  I've sure had no problems.  In fact, I've installed the old
additions under the new VPC.
Signature

.NET: It's About Trust!
http://vfred.mvps.org

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.