> On a machine here at my office, we have Virtual PC running for
> development. The problem is, the host machine only has 1 gig of ram, so
> we're fairly restricted on the virtual ram. When we are done with the
> virtual machine, in order to turn it off, we have to physically power off
> the host machine which is a problem in itself. However, this led to the
> vmc file becoming corrupted, and we tried to create a new one using the
> current virtual hard disk. Upon creation of the vmc settings, the vhd
> file was immediately deleted. Can anyone tell me how and why this would
> happen? Thanks
>

> Hi,
>
> I'm pretty sure I posted about the same problem a couple months ago. I
> *am* running VPC 2004 SP1, and the response that I got in this NG was that
> this was a "known problem"...
>
> Jim
>
>
> Colin Barnhorst wrote:
>> Are you running VPC with Service Pack 1 applied? The loss of a vhd right
>> after creating it sounds like a very old problem that has not appeared in
>> a couple of years now.
>>
>> "Tom Andrecht" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> On a machine here at my office, we have Virtual PC running for
>>> development. The problem is, the host machine only has 1 gig of ram, so
>>> we're fairly restricted on the virtual ram. When we are done with the
>>> virtual machine, in order to turn it off, we have to physically power
>>> off the host machine which is a problem in itself. However, this led to
>>> the vmc file becoming corrupted, and we tried to create a new one using
>>> the current virtual hard disk. Upon creation of the vmc settings, the
>>> vhd file was immediately deleted. Can anyone tell me how and why this
>>> would happen? Thanks
>>>
>>

> Are you running VPC with Service Pack 1 applied? The loss of a vhd right
> after creating it sounds like a very old problem that has not appeared in a
> couple of years now.
>
> "Tom Andrecht" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> On a machine here at my office, we have Virtual PC running for
>> development. The problem is, the host machine only has 1 gig of ram, so
>> we're fairly restricted on the virtual ram. When we are done with the
>> virtual machine, in order to turn it off, we have to physically power off
>> the host machine which is a problem in itself. However, this led to the
>> vmc file becoming corrupted, and we tried to create a new one using the
>> current virtual hard disk. Upon creation of the vmc settings, the vhd
>> file was immediately deleted. Can anyone tell me how and why this would
>> happen? Thanks
>>
>
>

> Are you running VPC with Service Pack 1 applied? The loss of a vhd right
> after creating it sounds like a very old problem that has not appeared in a
> couple of years now.
>

> In article <(email address - cut out)>, in the
> microsoft.public.virtualpc news group, <"Colin Barnhorst"
> <colinbarharst(remove)@msn.com>> says...
>
>> Are you running VPC with Service Pack 1 applied? The loss of a vhd right
>> after creating it sounds like a very old problem that has not appeared in
>> a
>> couple of years now.
>>
>
> This bug still exists in SP1.
>
> --
> Paul Adare - MVP Virtual Machines
> It all began with Adam. He was the first man to tell a
> joke--or a lie. How lucky Adam was. He knew when he said a
> good thing, nobody had said it before. Adam was not alone
> in the Garden of Eden, however, and does not deserve all
> the credit; much is due to Eve, the first woman, and Satan,
> the first consultant." - Mark Twain