> Karl E. Peterson wrote:
>> The thread, "Moving virtual pc images from one pc to another", has caused me to
>> question something I thought I understood. It seems if you move a VMC/VHD pair,
>> then point to the VMC as a new "existing" virtual machine in VPC, everything
>> works
>> just fine. Without actually needing to get into the VMC to update the absolute
>> path to the VHD. Looks like VPC is using the relative path when the absolute
>> path isn't current? Oddly enough, even if the relative path to the VHD works,
>> the absolute path in the VMC isn't updated to reflect this. Are there any
>> published "rules" to which path is used when? And why isn't VPC updating the VMC
>> file?
>
> Yes, I have wondered about this also. As far as I can tell, you have analyzed
> the situation correctly: if the absolute path is bad, VPC uses the relative one,
> and the VM still works. I agree that VPC should at least offer to repair the
> paths.

> The thread, "Moving virtual pc images from one pc to another", has caused me to
> question something I thought I understood. It seems if you move a VMC/VHD pair,
> then point to the VMC as a new "existing" virtual machine in VPC, everything works
> just fine. Without actually needing to get into the VMC to update the absolute path
> to the VHD. Looks like VPC is using the relative path when the absolute path isn't
> current? Oddly enough, even if the relative path to the VHD works, the absolute
> path in the VMC isn't updated to reflect this. Are there any published "rules" to
> which path is used when? And why isn't VPC updating the VMC file?

> Karl E. Peterson wrote:
>>I suppose the "acid test" would be what VPC would use if both the absolute and
>>relative paths pointed to valid but different VHDs? IMO, it's putting itself in a
>>position to have to decide in that situation, and it shouldn't be doing that.
>
> I *know* what it will use in this case: The full path!
> This is why it is not good to make copies of a guest on the same host
> by copying vmc and vhd files into a new folder. When you start the new
> guest it will actually use the old vhd file!
> Create new guest for a copied vhd and point it to the copied vhd in
> the wizard and all is well and dandy.

>David Wilkinson wrote:
>> Karl E. Peterson wrote:
>>> The thread, "Moving virtual pc images from one pc to another", has caused me to
>>> question something I thought I understood. It seems if you move a VMC/VHD pair,
>>> then point to the VMC as a new "existing" virtual machine in VPC, everything
>>> works
>>> just fine. Without actually needing to get into the VMC to update the absolute
>>> path to the VHD. Looks like VPC is using the relative path when the absolute
>>> path isn't current? Oddly enough, even if the relative path to the VHD works,
>>> the absolute path in the VMC isn't updated to reflect this. Are there any
>>> published "rules" to which path is used when? And why isn't VPC updating the VMC
>>> file?
>>
>> Yes, I have wondered about this also. As far as I can tell, you have analyzed
>> the situation correctly: if the absolute path is bad, VPC uses the relative one,
>> and the VM still works. I agree that VPC should at least offer to repair the
>> paths.
>
>I suppose the "acid test" would be what VPC would use if both the absolute and
>relative paths pointed to valid but different VHDs? IMO, it's putting itself in a
>position to have to decide in that situation, and it shouldn't be doing that.

> The thread, "Moving virtual pc images from one pc to another", has caused me to
> question something I thought I understood. It seems if you move a VMC/VHD pair,
> then point to the VMC as a new "existing" virtual machine in VPC, everything works
> just fine. Without actually needing to get into the VMC to update the absolute path
> to the VHD. Looks like VPC is using the relative path when the absolute path isn't
> current? Oddly enough, even if the relative path to the VHD works, the absolute
> path in the VMC isn't updated to reflect this. Are there any published "rules" to
> which path is used when? And why isn't VPC updating the VMC file?
>
> Thanks... Karl
> --
> ..NET: It's About Trust!
> http://vfred.mvps.org
>

>> The thread, "Moving virtual pc images from one pc to another", has caused me to
>> question something I thought I understood. It seems if you move a VMC/VHD pair,
>> then point to the VMC as a new "existing" virtual machine in VPC, everything works
>> just fine. Without actually needing to get into the VMC to update the absolute path
>> to the VHD. Looks like VPC is using the relative path when the absolute path isn't
>> current? Oddly enough, even if the relative path to the VHD works, the absolute
>> path in the VMC isn't updated to reflect this. Are there any published "rules" to
>> which path is used when? And why isn't VPC updating the VMC file?
>>
>> Thanks... Karl
>> --
>> ..NET: It's About Trust!
>> http://vfred.mvps.org
>>
>
> Create the vmc just the way you want it. then just delete the absolute path from the vmc file leaving only the relative path. This seems to work for me.