>-----Original Message-----
>I follow the defrag then run eraser with zero-bit
>since the Connectix days) but recently ran into a
>Host 1 has a WinXPpro guest with vhd at 15+G
>Host 2 has a Win2Kpro guest with vhd at 15+G
>I've never compacted a vhd that big, but didn't think I
>problems. Well, after the compact process on both boxes
>same size - still sitting at 15+G. Inside the guest the
>2G. Both vhd's are set to be dyamically expanding and
>Disk Wizard it does report that they are still
>There's a little voice in the back of my head that is
>about going over that initial 16384MB vhd size when I
>expanding vhd. I'm sure I'm missing something very
>be appreciated :)
>.
>

> Well, just for a sanity check, look at Question 5.11 (a &
> b):
> http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
>
> Also, you need to not use Undo drives while running
> eraser.
>
> Scott
>
> >-----Original Message-----
> >I follow the defrag then run eraser with zero-bit
> process (and have been
> >since the Connectix days) but recently ran into a
> problem. Here is my setup:
> >Host 1 has a WinXPpro guest with vhd at 15+G
> >Host 2 has a Win2Kpro guest with vhd at 15+G
> >I've never compacted a vhd that big, but didn't think I
> would run into
> >problems. Well, after the compact process on both boxes
> the vhd's are the
> >same size - still sitting at 15+G. Inside the guest the
> HD use is less than
> >2G. Both vhd's are set to be dyamically expanding and
> when I run the Virtual
> >Disk Wizard it does report that they are still
> dynamically expanding.
> >There's a little voice in the back of my head that is
> whispering something
> >about going over that initial 16384MB vhd size when I
> created the dynamically
> >expanding vhd. I'm sure I'm missing something very
> simple - any ideas would
> >be appreciated :)
> >.
> >
>

>-----Original Message-----
>Thanks for the quick reply, but, sanity has not come :)
>following the same steps as in the Q5.11, as well as not
>I'm tempted to create a new vhd and fluff it out to
>set a "proof" baseline, then fluff it out to the 15+G
>compact it again. Doesn't solve the problem, but it'll
>questions.
>
>
>"Scott Baker" wrote:
>
>> Well, just for a sanity check, look at Question 5.11
>> b):
>>
>>
>> Also, you need to not use Undo drives while running
>> eraser.
>>
>> Scott
>>
>> >-----Original Message-----
>> >I follow the defrag then run eraser with zero-bit
>> process (and have been
>> >since the Connectix days) but recently ran into a
>> problem. Here is my setup:
>> >Host 1 has a WinXPpro guest with vhd at 15+G
>> >Host 2 has a Win2Kpro guest with vhd at 15+G
>> >I've never compacted a vhd that big, but didn't think
>> would run into
>> >problems. Well, after the compact process on both
>> the vhd's are the
>> >same size - still sitting at 15+G. Inside the guest
>> HD use is less than
>> >2G. Both vhd's are set to be dyamically expanding
>> when I run the Virtual
>> >Disk Wizard it does report that they are still
>> dynamically expanding.
>> >There's a little voice in the back of my head that is
>> whispering something
>> >about going over that initial 16384MB vhd size when I
>> created the dynamically
>> >expanding vhd. I'm sure I'm missing something very
>> simple - any ideas would
>> >be appreciated :)
>> >.
>> >
>>
>.
>

>Thanks for the quick reply, but, sanity has not come :) I verified that I'm
>following the same steps as in the Q5.11, as well as not using undo drives.
>I'm tempted to create a new vhd and fluff it out to about 4G, compact it to
>set a "proof" baseline, then fluff it out to the 15+G and see if I can
>compact it again. Doesn't solve the problem, but it'll answer a few
>questions.
>
>
>"Scott Baker" wrote:
>
>> Well, just for a sanity check, look at Question 5.11 (a &
>> b):
>> http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
>>
>> Also, you need to not use Undo drives while running
>> eraser.
>>
>> Scott
>>
>> >-----Original Message-----
>> >I follow the defrag then run eraser with zero-bit
>> process (and have been
>> >since the Connectix days) but recently ran into a
>> problem. Here is my setup:
>> >Host 1 has a WinXPpro guest with vhd at 15+G
>> >Host 2 has a Win2Kpro guest with vhd at 15+G
>> >I've never compacted a vhd that big, but didn't think I
>> would run into
>> >problems. Well, after the compact process on both boxes
>> the vhd's are the
>> >same size - still sitting at 15+G. Inside the guest the
>> HD use is less than
>> >2G. Both vhd's are set to be dyamically expanding and
>> when I run the Virtual
>> >Disk Wizard it does report that they are still
>> dynamically expanding.
>> >There's a little voice in the back of my head that is
>> whispering something
>> >about going over that initial 16384MB vhd size when I
>> created the dynamically
>> >expanding vhd. I'm sure I'm missing something very
>> simple - any ideas would
>> >be appreciated :)
>> >.
>> >
>>

>-----Original Message-----
>Save yourself some time and buy a copy of Ghost and use
>Less steps, less work, and a lot less time.
>
>On Fri, 8 Oct 2004 10:19:01 -0700, "Mon account"
><(email address - cut out)> wrote:
>
>>Thanks for the quick reply, but, sanity has not
>>following the same steps as in the Q5.11, as well as
>>I'm tempted to create a new vhd and fluff it out to
>>set a "proof" baseline, then fluff it out to the 15+G
>>compact it again. Doesn't solve the problem, but it'll
>>questions.
>>
>>
>>"Scott Baker" wrote:
>>
>>> Well, just for a sanity check, look at Question 5.11
>>> b):
>>>
>>>
>>> Also, you need to not use Undo drives while running
>>> eraser.
>>>
>>> Scott
>>>
>>> >-----Original Message-----
>>> >I follow the defrag then run eraser with zero-bit
>>> process (and have been
>>> >since the Connectix days) but recently ran into a
>>> problem. Here is my setup:
>>> >Host 1 has a WinXPpro guest with vhd at 15+G
>>> >Host 2 has a Win2Kpro guest with vhd at 15+G
>>> >I've never compacted a vhd that big, but didn't
>>> would run into
>>> >problems. Well, after the compact process on both
>>> the vhd's are the
>>> >same size - still sitting at 15+G. Inside the guest
>>> HD use is less than
>>> >2G. Both vhd's are set to be dyamically expanding
>>> when I run the Virtual
>>> >Disk Wizard it does report that they are still
>>> dynamically expanding.
>>> >There's a little voice in the back of my head that
>>> whispering something
>>> >about going over that initial 16384MB vhd size when
>>> created the dynamically
>>> >expanding vhd. I'm sure I'm missing something very
>>> simple - any ideas would
>>> >be appreciated :)
>>> >.
>>> >
>>>
>
>Steve Jain, Microsoft MVP for Virtual PC for Windows
>Website: http://www.essjae.com
>*** All posts are provided AS-IS, no warranty, no QoS ***
>.
>