>I am using a virtual PC for a development project and running Office XP
>Professional because that version of Office is what I am developing against
>per my client's requirements.
>
>At home, I work with Virtual PC 2007 on Vista and when I am on the road I
>use Virtual PC 2004 on Windows Server 2003.
>
>Each time I move my virtual machine from one host (VPC 2007) to the other
>(VPC 2004), I have to re-activate Office XP. This could become a serious
>problem pretty quick if I run out of activations and have to reactivate by
>phone twice every day!
>
>Can anyone provide any help or suggestions on how to prevent this behavior?
>

> On Wed, 18 Apr 2007 11:36:01 -0700, Dale <(email address - cut out)am>
> wrote:
>
> >I am using a virtual PC for a development project and running Office XP
> >Professional because that version of Office is what I am developing against
> >per my client's requirements.
> >
> >At home, I work with Virtual PC 2007 on Vista and when I am on the road I
> >use Virtual PC 2004 on Windows Server 2003.
> >
> >Each time I move my virtual machine from one host (VPC 2007) to the other
> >(VPC 2004), I have to re-activate Office XP. This could become a serious
> >problem pretty quick if I run out of activations and have to reactivate by
> >phone twice every day!
> >
> >Can anyone provide any help or suggestions on how to prevent this behavior?
> >
>
> Do you move the vhd file or do you also move the vmc file?
> The vhd file just contains the disk data and should not matter, but
> the vmc file contains stuff like serial numbers, NIC MAC address and
> such, which are used to identify hardware.
>
> I suggest that you move the two files to a 2.5" USB2 disk drive and
> then you attach that to both PC:s. Moving from one to the other is
> then a matter of plugging in the USB disk into the proper PC before
> firing up VPC.
> Using the USB drive for the vhd file also will most likely speed up
> your virtual machine. :-)
>
> Then of course you shuld alsoinstall VPC2007 on the other host so thta
> you have a homogenous environment.
>
>
> Bo Berglund
> bo.berglund(at)nospam.telia.com
>

> On Fri, 20 Apr 2007 16:02:01 -0700, Dale wrote:
>
> > [Quoted Error Message]
> > The virtual machine "NS5DevelopmentPC" can't be started because it is being
> > used by another program, or marked as read-only.
> >
> > To start this virtual machine, stop using the virtual machine in another
> > program, or ensure that it is not marked read-only.
> > [/Quoted Error Message]
> >
> > The only way I am able to get past this message is to create a new virtual
> > PC using the VHD. That's the same results I was getting moving the files
> > from the local hard drive of one host PC to the other host originally and is
> > the reason why I can't re-use the vmc file on both hosts.
>
> This is a permissions issue. You either need to fix the permissions or run
> VPC elevated.
>
> --
> Paul Adare
> MVP - Windows - Virtual Machine
> http://www.identit.ca
> "The English language, complete with irony, satire, and sarcasm, has
> survived for centuries without smileys. Only the new crop of modern
> computer geeks finds it impossible to detect a joke that is not clearly
> labeled as such."
> Ray Shea
>

> [Quoted Error Message]
> The virtual machine "NS5DevelopmentPC" can't be started because it is being
> used by another program, or marked as read-only.
>
> To start this virtual machine, stop using the virtual machine in another
> program, or ensure that it is not marked read-only.
> [/Quoted Error Message]
>
> The only way I am able to get past this message is to create a new virtual
> PC using the VHD. That's the same results I was getting moving the files
> from the local hard drive of one host PC to the other host originally and is
> the reason why I can't re-use the vmc file on both hosts.