>I just installed Longhorn beta3 in a VPC2007 guest.
>The strange thing is that I would have believed that VirtualPC should
>consume the 512 Mb RAM I had given it but TaskManager just reports 8
>Mb RAM usage. How could this be?
>
>And the Longhorn guest runs really slow even with the VMAdditions
>installed, in fact my whole PC runs slow now when it is started.
>
>This is not the same experience as I had with Win2003 Enetrprise
>server as a guest it runs just fine...
>
>Any explanations?
>
>Host= XP-Pro SP2 with 1 Gb RAM
>
>/Bo
>
>Bo Berglund
>bo.berglund(at)nospam.telia.com

> On Fri, 25 May 2007 02:14:42 -0700, Steve Jain
> <(email address - cut out)> wrote:
>
>>
>>As far as memory used, that is correct behavior regardless of host.
>>Task Manager will not report the VM's memory usage under the Virtual
>>PC.exe file, it will only show as an increase in PF usage.
>
> Right, the PF usage is way up at the ceiling....
>
>>Longhorn may be running slowly simply due to the fact it is still in
>>beta.
>
> I specifically did not download the checked build in order to get a
> bit of a speed increase. But probably they still have code in there
> that slows it down, I guess.
>
> On a side note:
> When downloading the iso file I couldn't get the MS download manager
> to actually do the download. Tried several times with the resume, but
> to no avail.
> Finally I found out why:
> The iso file to download is named:
> en_windows_server_longhorn_beta_3_enterprise_standard_and_datacenter_x86_24938.iso
>
> And I tried to download to my preferred location:
> H:\Downloads\OperatingSystems\Windows\LongHorn_Beta3\
>
> By moving the download to:
> H:\Downloads\
> the download manager was able to start working.
>
> Should there not be a warning message that tells you that the combined
> path to the file is too big for download manager (140 chars)? I assume
> that this was the cause of course.
> And why did they invent this stupidly long file name in the first
> place at MSDN? 82 characters in the name alone!
> Go figure....
>
>
>
> Bo Berglund
> bo.berglund(at)nospam.telia.com

> On Fri, 25 May 2007 02:14:42 -0700, Steve Jain
> <(email address - cut out)> wrote:
>
>>
>>As far as memory used, that is correct behavior regardless of host.
>>Task Manager will not report the VM's memory usage under the Virtual
>>PC.exe file, it will only show as an increase in PF usage.
>
> Right, the PF usage is way up at the ceiling....
>
>>Longhorn may be running slowly simply due to the fact it is still in
>>beta.
>
> I specifically did not download the checked build in order to get a
> bit of a speed increase. But probably they still have code in there
> that slows it down, I guess.
>
> On a side note:
> When downloading the iso file I couldn't get the MS download manager
> to actually do the download. Tried several times with the resume, but
> to no avail.
> Finally I found out why:
> The iso file to download is named:
> en_windows_server_longhorn_beta_3_enterprise_standard_and_datacenter_x86_24938.iso
>
> And I tried to download to my preferred location:
> H:\Downloads\OperatingSystems\Windows\LongHorn_Beta3\
>
> By moving the download to:
> H:\Downloads\
> the download manager was able to start working.
>
> Should there not be a warning message that tells you that the combined
> path to the file is too big for download manager (140 chars)? I assume
> that this was the cause of course.
> And why did they invent this stupidly long file name in the first
> place at MSDN? 82 characters in the name alone!
> Go figure....
>
>
>
> Bo Berglund
> bo.berglund(at)nospam.telia.com

>
>As far as memory used, that is correct behavior regardless of host.
>Task Manager will not report the VM's memory usage under the Virtual
>PC.exe file, it will only show as an increase in PF usage.
>Longhorn may be running slowly simply due to the fact it is still in
>beta.