> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
> thought 7.01 patch fixed this. =A0Today I upgraded my G5 from 1.5 Gig of R=
> to 3.5 Gig. =A0I went into VPC afterwards to bump up my memory settings fo=
> some of my Virtual machines and noticed that the maximum I can set them to=
> is 512 Meg and no higher. =A0So I increased my XP Pro environment to 512 M=
> and booted. =A0Once booted to the desktop I did a VPC Properties and it sa=
> that my machine was running OSX 10.4.9 which I am actually running 10.4.11=
> and that my total system RAM was 2 Gig.
>
> Like I stated above I remember hearing about a RAM limit initially when VP=
> 7 came out but I thought it was taken care of. =A0Only 512 Meg is not a sh=
> stopper but I do have plenty more RAM available to VPC. =A0Anybody know mo=
> of what's going on than what I just found out? =A0 =A0 =A0

> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
> thought 7.01 patch fixed this. Today I upgraded my G5 from 1.5 Gig of RAM
> to 3.5 Gig. I went into VPC afterwards to bump up my memory settings for
> some of my Virtual machines and noticed that the maximum I can set them to
> is 512 Meg and no higher. So I increased my XP Pro environment to 512 Meg
> and booted. Once booted to the desktop I did a VPC Properties and it said
> that my machine was running OSX 10.4.9 which I am actually running 10.4.11
> and that my total system RAM was 2 Gig.
>
> Like I stated above I remember hearing about a RAM limit initially when
> VPC
> 7 came out but I thought it was taken care of. Only 512 Meg is not a show
> stopper but I do have plenty more RAM available to VPC. Anybody know more
> of what's going on than what I just found out?

>I thought the 2GB limit for NT was the size of the hard drive partition, not
>memory.
>
>"Paul Power" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>On Jan 16, 9:52 pm, Fred Horvat <(email address - cut out)> wrote:
>> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
>> thought 7.01 patch fixed this. Today I upgraded my G5 from 1.5 Gig of RAM
>> to 3.5 Gig. I went into VPC afterwards to bump up my memory settings for
>> some of my Virtual machines and noticed that the maximum I can set them to
>> is 512 Meg and no higher. So I increased my XP Pro environment to 512 Meg
>> and booted. Once booted to the desktop I did a VPC Properties and it said
>> that my machine was running OSX 10.4.9 which I am actually running 10.4.11
>> and that my total system RAM was 2 Gig.
>>
>> Like I stated above I remember hearing about a RAM limit initially when
>> VPC
>> 7 came out but I thought it was taken care of. Only 512 Meg is not a show
>> stopper but I do have plenty more RAM available to VPC. Anybody know more
>> of what's going on than what I just found out?
>
>
>The 2 GB RAM limit that you read about was for Windows NT Workstation
>4.0
>
>VPC never had any more than 512MB. A word of advice.....do not set
>your RAM to the max of 512MB. It will actually slow the performace of
>your virtual machine. Optimal performance levels can be achieved by
>using the formula: 50% of actual physical RAM to a maximum of 384MB.
>
>The 2GB reading that your system is reporting is total 'virtual
>mamory', a combination of disk space and RAM for quick access to
>required files.

>I follow you on the 512Meg limit but not the 2 Gig limit.
>
>> The 2GB reading that your system is reporting is total 'virtual
>> mamory', a combination of disk space and RAM for quick access to
>> required files.
>
>I have a total of 3.5 Gig of real RAM. So the 2Gig limit is imposed by VPC
>then?
>

> Well yes there is a 2 gig limit on any hard drive formatted as FAT16 (DOS)
> whether it is in DOS, NT, 95, or 98. But if you format it as NTFS The
> limit
> is much higher.
>
>
> On 1/22/08 4:44 PM, in article O7iC1$(email address - cut out),
> "Colin
> Barnhorst" <(email address - cut out)> wrote:
>
>> I thought the 2GB limit for NT was the size of the hard drive partition,
>> not
>> memory.
>>
>> "Paul Power" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> On Jan 16, 9:52 pm, Fred Horvat <(email address - cut out)> wrote:
>>> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
>>> thought 7.01 patch fixed this. Today I upgraded my G5 from 1.5 Gig of
>>> RAM
>>> to 3.5 Gig. I went into VPC afterwards to bump up my memory settings for
>>> some of my Virtual machines and noticed that the maximum I can set them
>>> to
>>> is 512 Meg and no higher. So I increased my XP Pro environment to 512
>>> Meg
>>> and booted. Once booted to the desktop I did a VPC Properties and it
>>> said
>>> that my machine was running OSX 10.4.9 which I am actually running
>>> 10.4.11
>>> and that my total system RAM was 2 Gig.
>>>
>>> Like I stated above I remember hearing about a RAM limit initially when
>>> VPC
>>> 7 came out but I thought it was taken care of. Only 512 Meg is not a
>>> show
>>> stopper but I do have plenty more RAM available to VPC. Anybody know
>>> more
>>> of what's going on than what I just found out?
>>
>>
>> The 2 GB RAM limit that you read about was for Windows NT Workstation
>> 4.0
>>
>> VPC never had any more than 512MB. A word of advice.....do not set
>> your RAM to the max of 512MB. It will actually slow the performace of
>> your virtual machine. Optimal performance levels can be achieved by
>> using the formula: 50% of actual physical RAM to a maximum of 384MB.
>>
>> The 2GB reading that your system is reporting is total 'virtual
>> mamory', a combination of disk space and RAM for quick access to
>> required files.
>>
>

> The 2GB reading that your system is reporting is total 'virtual
> mamory', a combination of disk space and RAM for quick access to
> required files.
> On Jan 16, 9:52 pm, Fred Horvat <(email address - cut out)> wrote:
>> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
>> thought 7.01 patch fixed this.  Today I upgraded my G5 from 1.5 Gig of RAM
>> to 3.5 Gig.  I went into VPC afterwards to bump up my memory settings for
>> some of my Virtual machines and noticed that the maximum I can set them to
>> is 512 Meg and no higher.  So I increased my XP Pro environment to 512 Meg
>> and booted.  Once booted to the desktop I did a VPC Properties and it said
>> that my machine was running OSX 10.4.9 which I am actually running 10.4.11
>> and that my total system RAM was 2 Gig.
>>
>> Like I stated above I remember hearing about a RAM limit initially when VPC
>> 7 came out but I thought it was taken care of.  Only 512 Meg is not a show
>> stopper but I do have plenty more RAM available to VPC.  Anybody know more
>> of what's going on than what I just found out?      
>
>
> The 2 GB RAM limit that you read about was for Windows NT Workstation
> 4.0
>
> VPC never had any more than 512MB. A word of advice.....do not set
> your RAM to the max of 512MB. It will actually slow the performace of
> your virtual machine. Optimal performance levels can be achieved by
> using the formula: 50% of actual physical RAM to a maximum of 384MB.
>
> The 2GB reading that your system is reporting is total 'virtual
> mamory', a combination of disk space and RAM for quick access to
> required files.

> I thought the 2GB limit for NT was the size of the hard drive partition, not
> memory.
>
> "Paul Power" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> On Jan 16, 9:52 pm, Fred Horvat <(email address - cut out)> wrote:
>> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
>> thought 7.01 patch fixed this. Today I upgraded my G5 from 1.5 Gig of RAM
>> to 3.5 Gig. I went into VPC afterwards to bump up my memory settings for
>> some of my Virtual machines and noticed that the maximum I can set them to
>> is 512 Meg and no higher. So I increased my XP Pro environment to 512 Meg
>> and booted. Once booted to the desktop I did a VPC Properties and it said
>> that my machine was running OSX 10.4.9 which I am actually running 10.4.11
>> and that my total system RAM was 2 Gig.
>>
>> Like I stated above I remember hearing about a RAM limit initially when
>> VPC
>> 7 came out but I thought it was taken care of. Only 512 Meg is not a show
>> stopper but I do have plenty more RAM available to VPC. Anybody know more
>> of what's going on than what I just found out?
>
>
> The 2 GB RAM limit that you read about was for Windows NT Workstation
> 4.0
>
> VPC never had any more than 512MB. A word of advice.....do not set
> your RAM to the max of 512MB. It will actually slow the performace of
> your virtual machine. Optimal performance levels can be achieved by
> using the formula: 50% of actual physical RAM to a maximum of 384MB.
>
> The 2GB reading that your system is reporting is total 'virtual
> mamory', a combination of disk space and RAM for quick access to
> required files.
>

>That's what I thought in my original posting but it appears that I can run
>VPC with over 2 Gig but it only thinks I have 2 Gig and worse only allows me
>512Meg to a virtual machine.
>

> There were problems a while back with G5's with 2GB or more installed
> with VPC 7.0.
>
> 7.0.1 fixed it
>
>
>
> On Tue, 22 Jan 2008 14:44:20 -0700, "Colin Barnhorst"
> <(email address - cut out)> wrote:
>
>> I thought the 2GB limit for NT was the size of the hard drive partition, not
>> memory.
>>
>> "Paul Power" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> On Jan 16, 9:52 pm, Fred Horvat <(email address - cut out)> wrote:
>>> I remember reading a while back about a RAM limit of 2 Gig for VPC but I
>>> thought 7.01 patch fixed this. Today I upgraded my G5 from 1.5 Gig of RAM
>>> to 3.5 Gig. I went into VPC afterwards to bump up my memory settings for
>>> some of my Virtual machines and noticed that the maximum I can set them to
>>> is 512 Meg and no higher. So I increased my XP Pro environment to 512 Meg
>>> and booted. Once booted to the desktop I did a VPC Properties and it said
>>> that my machine was running OSX 10.4.9 which I am actually running 10.4.11
>>> and that my total system RAM was 2 Gig.
>>>
>>> Like I stated above I remember hearing about a RAM limit initially when
>>> VPC
>>> 7 came out but I thought it was taken care of. Only 512 Meg is not a show
>>> stopper but I do have plenty more RAM available to VPC. Anybody know more
>>> of what's going on than what I just found out?
>>
>>
>> The 2 GB RAM limit that you read about was for Windows NT Workstation
>> 4.0
>>
>> VPC never had any more than 512MB. A word of advice.....do not set
>> your RAM to the max of 512MB. It will actually slow the performace of
>> your virtual machine. Optimal performance levels can be achieved by
>> using the formula: 50% of actual physical RAM to a maximum of 384MB.
>>
>> The 2GB reading that your system is reporting is total 'virtual
>> mamory', a combination of disk space and RAM for quick access to
>> required files.

> XP runs fine with 512 and 98 and 2000 I run well under 512. The couple of
> Linux Distros I run I have under 512 and all run well. Only Vista I'd
> like
> to run over 512 but that's not possible so 512 will have to do.
>
> Thanks
>
>
> On 1/23/08 7:14 PM, in article (email address - cut out),
> "Steve Jain" <(email address - cut out)> wrote:
>
>> On Wed, 23 Jan 2008 18:28:40 -0500, Fred Horvat <(email address - cut out)>
>> wrote:
>>
>>> That's what I thought in my original posting but it appears that I can
>>> run
>>> VPC with over 2 Gig but it only thinks I have 2 Gig and worse only
>>> allows me
>>> 512Meg to a virtual machine.
>>>
>>
>> There is a hard limit in VPC, the max you can assign to a VM is 512MB,
>> regardless of the host's RAM. The overhead of managing all that RAM
>> in an emulated environment causes a big performance hit.
>>
>> VPC simply ignores more than 2GB, which resolves the >2GB problems
>> that occured in VPC 7.00
>

> On Wed, 23 Jan 2008 18:28:40 -0500, Fred Horvat <(email address - cut out)>
> wrote:
>
>> That's what I thought in my original posting but it appears that I can run
>> VPC with over 2 Gig but it only thinks I have 2 Gig and worse only allows me
>> 512Meg to a virtual machine.
>>
>
> There is a hard limit in VPC, the max you can assign to a VM is 512MB,
> regardless of the host's RAM. The overhead of managing all that RAM
> in an emulated environment causes a big performance hit.
>
> VPC simply ignores more than 2GB, which resolves the >2GB problems
> that occured in VPC 7.00

> You might as well run Vista Home Basic now that MS has changed the EULA to
> permit the home editions to be virtualized. You can load it by not entering
> a PK. That will allow you to install the edition of your choice on the
> 30-day trial. There is workaround to extend even that. Some of the folks
> in the Vista newsgroups can point you to the workaround if you don't already
> know about it. I see little point in running the other editions given the
> ram limit. A lot of their additional features won't work well or at all in
> a VPC7 vm anyway even if you could up the ram.
>
> "Fred Horvat" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> XP runs fine with 512 and 98 and 2000 I run well under 512. The couple of
>> Linux Distros I run I have under 512 and all run well. Only Vista I'd
>> like
>> to run over 512 but that's not possible so 512 will have to do.
>>
>> Thanks
>>
>>
>> On 1/23/08 7:14 PM, in article (email address - cut out),
>> "Steve Jain" <(email address - cut out)> wrote:
>>
>>> On Wed, 23 Jan 2008 18:28:40 -0500, Fred Horvat <(email address - cut out)>
>>> wrote:
>>>
>>>> That's what I thought in my original posting but it appears that I can
>>>> run
>>>> VPC with over 2 Gig but it only thinks I have 2 Gig and worse only
>>>> allows me
>>>> 512Meg to a virtual machine.
>>>>
>>>
>>> There is a hard limit in VPC, the max you can assign to a VM is 512MB,
>>> regardless of the host's RAM. The overhead of managing all that RAM
>>> in an emulated environment causes a big performance hit.
>>>
>>> VPC simply ignores more than 2GB, which resolves the >2GB problems
>>> that occured in VPC 7.00
>>
>