> In trying to get back to the condition I was in before my VPCs stopped
> loading (see my post of about 5 minutes ago), I notice that this software has
> the somewhat troubling habit of deleting VHDs when there is a problem adding
> the machine.
>
> I go through the steps of adding a new machine, selecting an existing VHD
> and, even though there's no existing shortcut, no existing directory
> containing the VMC and no other VMC with that name on the host, VPC tells me
> it can't add the machine and then deletes the VHD! What sort of crap is
> that?!? Thank GOD I had the foresight to copy the folder containing the VHDs
> somewhere safe...

> This is a known bug that is going to be fixed in the next update. It
> only happens if VPC fails to create the .VMC file (which is thankfully
> rare).
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> VBScab wrote:
> > In trying to get back to the condition I was in before my VPCs stopped
> > loading (see my post of about 5 minutes ago), I notice that this software has
> > the somewhat troubling habit of deleting VHDs when there is a problem adding
> > the machine.
> >
> > I go through the steps of adding a new machine, selecting an existing VHD
> > and, even though there's no existing shortcut, no existing directory
> > containing the VMC and no other VMC with that name on the host, VPC tells me
> > it can't add the machine and then deletes the VHD! What sort of crap is
> > that?!? Thank GOD I had the foresight to copy the folder containing the VHDs
> > somewhere safe...
>

> So, the product is called 'Virtual PC 2004' which means it was authored
> around, what, 2003? THREE YEARS LATER, someone will get round to fixing a
> bug
> which deletes the single most important file driving the product. No-one
> thought it might be apposite to release a patch/service pack/whatever in
> the
> meantime?!?
>
> Fabulous...

> I know this isn't going to make you any less upset, but Microsoft did
> release Service Pack 1 for VPC 2004. Although it does not fix the bug which
> is currently troubling you, it does contain fixes and if you are still
> running the release built in 2003, you should upgrade to SP1.
>
>
> "VBScab" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > So, the product is called 'Virtual PC 2004' which means it was authored
> > around, what, 2003? THREE YEARS LATER, someone will get round to fixing a
> > bug
> > which deletes the single most important file driving the product. No-one
> > thought it might be apposite to release a patch/service pack/whatever in
> > the
> > meantime?!?
> >
> > Fabulous...
>
>
>

> I already have SP1. The point I was making is that I just can't believe a bug
> this serious hasn't been fixed after all this time
>
> "Ronny Ong" wrote:
>
>> I know this isn't going to make you any less upset, but Microsoft did
>> release Service Pack 1 for VPC 2004. Although it does not fix the bug which
>> is currently troubling you, it does contain fixes and if you are still
>> running the release built in 2003, you should upgrade to SP1.
>>
>>
>> "VBScab" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> So, the product is called 'Virtual PC 2004' which means it was authored
>>> around, what, 2003? THREE YEARS LATER, someone will get round to fixing a
>>> bug
>>> which deletes the single most important file driving the product. No-one
>>> thought it might be apposite to release a patch/service pack/whatever in
>>> the
>>> meantime?!?
>>>
>>> Fabulous...
>>
>>

> Hi,
>
> This issue was only recently discovered.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> VBScab wrote:
> > I already have SP1. The point I was making is that I just can't believe a bug
> > this serious hasn't been fixed after all this time
> >
> > "Ronny Ong" wrote:
> >
> >> I know this isn't going to make you any less upset, but Microsoft did
> >> release Service Pack 1 for VPC 2004. Although it does not fix the bug which
> >> is currently troubling you, it does contain fixes and if you are still
> >> running the release built in 2003, you should upgrade to SP1.
> >>
> >>
> >> "VBScab" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >>> So, the product is called 'Virtual PC 2004' which means it was authored
> >>> around, what, 2003? THREE YEARS LATER, someone will get round to fixing a
> >>> bug
> >>> which deletes the single most important file driving the product. No-one
> >>> thought it might be apposite to release a patch/service pack/whatever in
> >>> the
> >>> meantime?!?
> >>>
> >>> Fabulous...
> >>
> >>
>

> I *really* don't mean to be combative so please don't take this the wrong
> way, but what kind of excuse is that?!? Exactly what testing of the code took
> place? Jeez, if software has ANY code that's going to delete what is THE
> single most important file the product uses, *surely* any sane development
> team would test all scenarios which might call that code? Frankly, I'd be
> sacked if I released code with such a substantial flaw. It beggars belief, it
> really does.
>
> "Ben Armstrong [MSFT]" wrote:
>
>> Hi,
>>
>> This issue was only recently discovered.
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> You assume all risk for your use.
>>
>> VBScab wrote:
>>> I already have SP1. The point I was making is that I just can't believe a bug
>>> this serious hasn't been fixed after all this time
>>>
>>> "Ronny Ong" wrote:
>>>
>>>> I know this isn't going to make you any less upset, but Microsoft did
>>>> release Service Pack 1 for VPC 2004. Although it does not fix the bug which
>>>> is currently troubling you, it does contain fixes and if you are still
>>>> running the release built in 2003, you should upgrade to SP1.
>>>>
>>>>
>>>> "VBScab" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> So, the product is called 'Virtual PC 2004' which means it was authored
>>>>> around, what, 2003? THREE YEARS LATER, someone will get round to fixing a
>>>>> bug
>>>>> which deletes the single most important file driving the product. No-one
>>>>> thought it might be apposite to release a patch/service pack/whatever in
>>>>> the
>>>>> meantime?!?
>>>>>
>>>>> Fabulous...
>>>>

> We did not find this issue because it requires that the creation of the
> VMC file fails. We did test to make sure that if a user specified an
> existing VHD and canceled - the file did not get deleted. We also made
> sure that we did not affect any other files that were in the folder.
>
> This was an unfortunate oversight in our test plan.