Re: [hlds] Client crash question

[Richard Eid]

How to check your paged pool memory

   1. Download and extract Process
Explorer
   .
   2. Run Process Explorer. Press CTRL + i to bring up the System
   Information window.
   3. Run the game in a window.
  - Go to Steam's My games menu.
  - Right-click on the problematic game.
  - Select Properties > General > Set launch options.
  - Add -sw to the launch options.
  - Launch the game.
   4. *Watch the System Information > Kernel Memory (K) > Paged Physicalvalue.
   * If the value exceeds 150MB, you are using too much paged pool memory.

That's from:
https://support.steampowered.com/kb_article.php?ref=5034-EIPV-6426

Sorry for another e-mail...I just wanted to point out how exactly you should
be troubleshooting this issue.  The portion that I bolded(if formatting
makes it through the mailing list) is what you should be looking at.


-Richard Eid


On Sat, Oct 4, 2008 at 3:42 PM, Richard Eid <[EMAIL PROTECTED]> wrote:

> I wouldn't trust Task Manager's numbers.  Use Process Explorer instead.
>
> http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
>
> When you get it installed, press Ctrl-I to bring up System Information.
> It'll show you the real values of what's in use.  2MB seems extremely low
> for PPM usage.  If you have time, post a screenshot of your System
> Information window.
>
> Also, in that HL2.net post, what value did you choose to use?
>
> -Richard Eid
>
>
>
> On Sat, Oct 4, 2008 at 3:28 PM, Saint K. <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> I've tried the register edit, unfortunately its not working. I have
>> checked
>> the task manager for pool page memory usage, but everything is really low,
>> all together it will barley top 2MB.
>>
>> Cheers,
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
>> Sent: Saturday, October 04, 2008 7:59 PM
>> To: Half-Life dedicated Win32 server mailing list
>> Subject: Re: [hlds] Client crash question
>>
>> The following link should explain it all.  It seems that there is actually
>> a
>> limit(and since Vista SP1, a limit can actually be set, if desired), but
>> not
>> to the degree that previous versions of Windows have.  For our purposes
>> here, in running the servers and the actual game, those of us using Vista
>> needn't worry about PPM limits.  The PPM "limit" is equal to that of the
>> available kernel-mode virtual address space.
>>
>> As for Saint K., I'd still give the earlier link I posted a shot...the one
>> at halflife2.net.  It's worked for countless numbers of people, and you
>> describe a situation where you could easily run into problems directly
>> related to it.
>>
>> Oh, that link...
>>
>> http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits
>> _windows_vista
>>
>>-Richard Eid
>>
>>
>> On Sat, Oct 4, 2008 at 11:26 AM, localhost <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > Not sure how you're using the word "paging" and you've also got a pretty
>> > important typo in your first sentence.
>> > On 32-bit OS, each process can have up to 2gig of virtual memory, and
>> the
>> > kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the
>> kernel
>> > only takes 1 gig, and _if the process has the correct flag saying it can
>> > use memory over 2gig_ (large address aware iirc), it can then use up to
>> 3.
>> >
>> > On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process
>> has
>> > large address aware set, it can address up to 4 gigs of memory.  If not,
>> > still 2.
>> >
>> > As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
>> > reduce the PPM size, and (unless you have large address aware programs
>> that
>> > need the virtual memory, have no beneficial effect)
>> >
>> >
>> > On Sat, 4 Oct 2008 02:13:51 -0500, "Luke Lewis" <
>> [EMAIL PROTECTED]>
>> > wrote:
>> > > Actually the /3Gb switch enables 32 bit operating systems to page
>> memory
>> > > above 3Gb of memory rather that memory is physical or virtual. In 32
>> bit
>> > > operating systems client services or programs once they have paged
>> above
>> > > 2GB
>> > > per instance will crash. The 3GB switch for 32 bit operating systems
>> > allow
>> > > programs to use up to 3GB of memory addressing per instance in fact
>> with
>> > > 3-4
>> > > GB installed into the machine you should see equal virtual memory with
>> > > physical memory in most cases. In default configuration Windows will
>> > > allocate 2GB for the operating system and 2GB max for all other
>> > operations
>> > > such as services or programs. With the PAE switches, especially the
>> > > /userva=
>> > > switch you can allow the operating system to issue 3GB of
>> paging/physical
>> > > memory to each running instance allowin

Re: [hlds] Client crash question

[Richard Eid]

I wouldn't trust Task Manager's numbers.  Use Process Explorer instead.

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

When you get it installed, press Ctrl-I to bring up System Information.
It'll show you the real values of what's in use.  2MB seems extremely low
for PPM usage.  If you have time, post a screenshot of your System
Information window.

Also, in that HL2.net post, what value did you choose to use?

-Richard Eid


On Sat, Oct 4, 2008 at 3:28 PM, Saint K. <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I've tried the register edit, unfortunately its not working. I have checked
> the task manager for pool page memory usage, but everything is really low,
> all together it will barley top 2MB.
>
> Cheers,
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
> Sent: Saturday, October 04, 2008 7:59 PM
> To: Half-Life dedicated Win32 server mailing list
> Subject: Re: [hlds] Client crash question
>
> The following link should explain it all.  It seems that there is actually
> a
> limit(and since Vista SP1, a limit can actually be set, if desired), but
> not
> to the degree that previous versions of Windows have.  For our purposes
> here, in running the servers and the actual game, those of us using Vista
> needn't worry about PPM limits.  The PPM "limit" is equal to that of the
> available kernel-mode virtual address space.
>
> As for Saint K., I'd still give the earlier link I posted a shot...the one
> at halflife2.net.  It's worked for countless numbers of people, and you
> describe a situation where you could easily run into problems directly
> related to it.
>
> Oh, that link...
>
> http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits
> _windows_vista
>
>-Richard Eid
>
>
> On Sat, Oct 4, 2008 at 11:26 AM, localhost <[EMAIL PROTECTED]> wrote:
>
> >
> > Not sure how you're using the word "paging" and you've also got a pretty
> > important typo in your first sentence.
> > On 32-bit OS, each process can have up to 2gig of virtual memory, and the
> > kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the
> kernel
> > only takes 1 gig, and _if the process has the correct flag saying it can
> > use memory over 2gig_ (large address aware iirc), it can then use up to
> 3.
> >
> > On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process
> has
> > large address aware set, it can address up to 4 gigs of memory.  If not,
> > still 2.
> >
> > As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
> > reduce the PPM size, and (unless you have large address aware programs
> that
> > need the virtual memory, have no beneficial effect)
> >
> >
> > On Sat, 4 Oct 2008 02:13:51 -0500, "Luke Lewis" <[EMAIL PROTECTED]
> >
> > wrote:
> > > Actually the /3Gb switch enables 32 bit operating systems to page
> memory
> > > above 3Gb of memory rather that memory is physical or virtual. In 32
> bit
> > > operating systems client services or programs once they have paged
> above
> > > 2GB
> > > per instance will crash. The 3GB switch for 32 bit operating systems
> > allow
> > > programs to use up to 3GB of memory addressing per instance in fact
> with
> > > 3-4
> > > GB installed into the machine you should see equal virtual memory with
> > > physical memory in most cases. In default configuration Windows will
> > > allocate 2GB for the operating system and 2GB max for all other
> > operations
> > > such as services or programs. With the PAE switches, especially the
> > > /userva=
> > > switch you can allow the operating system to issue 3GB of
> paging/physical
> > > memory to each running instance allowing Windows to only use 1GB. Hence
> > > the
> > > reason all 32 bit windows operating systems only paging 4GB max.
> > Depending
> > > on USB devices and how memory are mapped on those most installations of
> > 32
> > > bit (non-server) O/S's only will see a max of about 3.5GB with 4
> > > installed.
> > > The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb
> > > most
> > > people find the need to fine tune that usage in increments of 512, but
> > can
> > > be fine tunes in 16-32-64 bit increments if the program you are using
> > > recognizes this. Here is another link a bit more relavent(?) to Vista
> and
> > > explains the paging situation with 32 vs 64 bit O/S and covers some
> > server
> > > 2003 instances.
> > >
> > >
> >
> >
>
> http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders
> > > tanding-pool-resources.aspx
> > >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
> > > Sent: Saturday, October 04, 2008 1:23 AM
> > > To: Half-Life dedicated Win32 server mailing list
> > > Subject: Re: [hlds] Client crash question
> > >
> > > In this case, physical RAM has little to do wit

Re: [hlds] Client crash question

[Saint K.]

Hi,

I've tried the register edit, unfortunately its not working. I have checked
the task manager for pool page memory usage, but everything is really low,
all together it will barley top 2MB.

Cheers,

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
Sent: Saturday, October 04, 2008 7:59 PM
To: Half-Life dedicated Win32 server mailing list
Subject: Re: [hlds] Client crash question

The following link should explain it all.  It seems that there is actually a
limit(and since Vista SP1, a limit can actually be set, if desired), but not
to the degree that previous versions of Windows have.  For our purposes
here, in running the servers and the actual game, those of us using Vista
needn't worry about PPM limits.  The PPM "limit" is equal to that of the
available kernel-mode virtual address space.

As for Saint K., I'd still give the earlier link I posted a shot...the one
at halflife2.net.  It's worked for countless numbers of people, and you
describe a situation where you could easily run into problems directly
related to it.

Oh, that link...
http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits
_windows_vista

-Richard Eid


On Sat, Oct 4, 2008 at 11:26 AM, localhost <[EMAIL PROTECTED]> wrote:

>
> Not sure how you're using the word "paging" and you've also got a pretty
> important typo in your first sentence.
> On 32-bit OS, each process can have up to 2gig of virtual memory, and the
> kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the kernel
> only takes 1 gig, and _if the process has the correct flag saying it can
> use memory over 2gig_ (large address aware iirc), it can then use up to 3.
>
> On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process
has
> large address aware set, it can address up to 4 gigs of memory.  If not,
> still 2.
>
> As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
> reduce the PPM size, and (unless you have large address aware programs
that
> need the virtual memory, have no beneficial effect)
>
>
> On Sat, 4 Oct 2008 02:13:51 -0500, "Luke Lewis" <[EMAIL PROTECTED]>
> wrote:
> > Actually the /3Gb switch enables 32 bit operating systems to page memory
> > above 3Gb of memory rather that memory is physical or virtual. In 32 bit
> > operating systems client services or programs once they have paged above
> > 2GB
> > per instance will crash. The 3GB switch for 32 bit operating systems
> allow
> > programs to use up to 3GB of memory addressing per instance in fact with
> > 3-4
> > GB installed into the machine you should see equal virtual memory with
> > physical memory in most cases. In default configuration Windows will
> > allocate 2GB for the operating system and 2GB max for all other
> operations
> > such as services or programs. With the PAE switches, especially the
> > /userva=
> > switch you can allow the operating system to issue 3GB of
paging/physical
> > memory to each running instance allowing Windows to only use 1GB. Hence
> > the
> > reason all 32 bit windows operating systems only paging 4GB max.
> Depending
> > on USB devices and how memory are mapped on those most installations of
> 32
> > bit (non-server) O/S's only will see a max of about 3.5GB with 4
> > installed.
> > The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb
> > most
> > people find the need to fine tune that usage in increments of 512, but
> can
> > be fine tunes in 16-32-64 bit increments if the program you are using
> > recognizes this. Here is another link a bit more relavent(?) to Vista
and
> > explains the paging situation with 32 vs 64 bit O/S and covers some
> server
> > 2003 instances.
> >
> >
>
>
http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders
> > tanding-pool-resources.aspx
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
> > Sent: Saturday, October 04, 2008 1:23 AM
> > To: Half-Life dedicated Win32 server mailing list
> > Subject: Re: [hlds] Client crash question
> >
> > In this case, physical RAM has little to do with PPM.  Surely, 64-bit
> > Vista
> > makes a difference with RAM sizes above 4GB, but he's not running out of
> > physical RAM, he's running out of PPM.  In XP and earlier, you'll want
to
> > try to keep the PPM usage below 150,000, which you can observe using
> > System
> > Information in Process Explorer.  With Vista, you really don't have to
> > worry
> > about it.
> >
> > -Richard Eid
> >
> >
> > On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis <[EMAIL PROTECTED]>
> > wrote:
> >
> >> Vista does indeed suffer from the 4GB barrier that Windows XP has,
> > unless
> >> you use the 64bit version of either operating system or use a server
> >> operating system. Note this is an article from 2005 so obviously Vista
> >> isn't
> >> inside thi

Re: [hlds] Client crash question

[Richard Eid]

4GB limit on what?  Maybe I missed something there.  I thought we were
talking about PPM and not Memory Management as a whole.  Or has the
conversation expanded?

-Richard Eid


On Sat, Oct 4, 2008 at 2:54 PM, Luke Lewis <[EMAIL PROTECTED]> wrote:

> Ok you're saying exactly what I was saying so thanks? And Richard thanks
> for
> the link, but it only shows that Vista still has the 4GB limit. Either way
> thanks for the link it did provide me with some knowledge. Either way I
> guess this is pointless now lol. Thanks Richard for your input!
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of localhost
> Subject: Re: [hlds] Client crash question
>
>
> Not sure how you're using the word "paging" and you've also got a pretty
> important typo in your first sentence.
> On 32-bit OS, each process can have up to 2gig of virtual memory, and the
> kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the kernel
> only takes 1 gig, and _if the process has the correct flag saying it can
> use memory over 2gig_ (large address aware iirc), it can then use up to 3.
>
> On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process has
> large address aware set, it can address up to 4 gigs of memory.  If not,
> still 2.
>
> As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
> reduce the PPM size, and (unless you have large address aware programs that
> need the virtual memory, have no beneficial effect)
>
>
>
>
> __ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3495 (20081004) __
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> Sent Via http://www.gorillazsouth.com mail server.
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Re: [hlds] Client crash question

[Luke Lewis]

Ok you're saying exactly what I was saying so thanks? And Richard thanks for
the link, but it only shows that Vista still has the 4GB limit. Either way
thanks for the link it did provide me with some knowledge. Either way I
guess this is pointless now lol. Thanks Richard for your input!

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of localhost
Subject: Re: [hlds] Client crash question


Not sure how you're using the word "paging" and you've also got a pretty
important typo in your first sentence.
On 32-bit OS, each process can have up to 2gig of virtual memory, and the
kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the kernel
only takes 1 gig, and _if the process has the correct flag saying it can
use memory over 2gig_ (large address aware iirc), it can then use up to 3.

On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process has
large address aware set, it can address up to 4 gigs of memory.  If not,
still 2.

As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
reduce the PPM size, and (unless you have large address aware programs that
need the virtual memory, have no beneficial effect)


 

__ Information from ESET NOD32 Antivirus, version of virus signature
database 3495 (20081004) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 




Sent Via http://www.gorillazsouth.com mail server.


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Re: [hlds] Client crash question

[Richard Eid]

The following link should explain it all.  It seems that there is actually a
limit(and since Vista SP1, a limit can actually be set, if desired), but not
to the degree that previous versions of Windows have.  For our purposes
here, in running the servers and the actual game, those of us using Vista
needn't worry about PPM limits.  The PPM "limit" is equal to that of the
available kernel-mode virtual address space.

As for Saint K., I'd still give the earlier link I posted a shot...the one
at halflife2.net.  It's worked for countless numbers of people, and you
describe a situation where you could easily run into problems directly
related to it.

Oh, that link...
http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits_windows_vista

-Richard Eid


On Sat, Oct 4, 2008 at 11:26 AM, localhost <[EMAIL PROTECTED]> wrote:

>
> Not sure how you're using the word "paging" and you've also got a pretty
> important typo in your first sentence.
> On 32-bit OS, each process can have up to 2gig of virtual memory, and the
> kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the kernel
> only takes 1 gig, and _if the process has the correct flag saying it can
> use memory over 2gig_ (large address aware iirc), it can then use up to 3.
>
> On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process has
> large address aware set, it can address up to 4 gigs of memory.  If not,
> still 2.
>
> As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
> reduce the PPM size, and (unless you have large address aware programs that
> need the virtual memory, have no beneficial effect)
>
>
> On Sat, 4 Oct 2008 02:13:51 -0500, "Luke Lewis" <[EMAIL PROTECTED]>
> wrote:
> > Actually the /3Gb switch enables 32 bit operating systems to page memory
> > above 3Gb of memory rather that memory is physical or virtual. In 32 bit
> > operating systems client services or programs once they have paged above
> > 2GB
> > per instance will crash. The 3GB switch for 32 bit operating systems
> allow
> > programs to use up to 3GB of memory addressing per instance in fact with
> > 3-4
> > GB installed into the machine you should see equal virtual memory with
> > physical memory in most cases. In default configuration Windows will
> > allocate 2GB for the operating system and 2GB max for all other
> operations
> > such as services or programs. With the PAE switches, especially the
> > /userva=
> > switch you can allow the operating system to issue 3GB of paging/physical
> > memory to each running instance allowing Windows to only use 1GB. Hence
> > the
> > reason all 32 bit windows operating systems only paging 4GB max.
> Depending
> > on USB devices and how memory are mapped on those most installations of
> 32
> > bit (non-server) O/S's only will see a max of about 3.5GB with 4
> > installed.
> > The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb
> > most
> > people find the need to fine tune that usage in increments of 512, but
> can
> > be fine tunes in 16-32-64 bit increments if the program you are using
> > recognizes this. Here is another link a bit more relavent(?) to Vista and
> > explains the paging situation with 32 vs 64 bit O/S and covers some
> server
> > 2003 instances.
> >
> >
>
> http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders
> > tanding-pool-resources.aspx
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
> > Sent: Saturday, October 04, 2008 1:23 AM
> > To: Half-Life dedicated Win32 server mailing list
> > Subject: Re: [hlds] Client crash question
> >
> > In this case, physical RAM has little to do with PPM.  Surely, 64-bit
> > Vista
> > makes a difference with RAM sizes above 4GB, but he's not running out of
> > physical RAM, he's running out of PPM.  In XP and earlier, you'll want to
> > try to keep the PPM usage below 150,000, which you can observe using
> > System
> > Information in Process Explorer.  With Vista, you really don't have to
> > worry
> > about it.
> >
> > -Richard Eid
> >
> >
> > On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis <[EMAIL PROTECTED]>
> > wrote:
> >
> >> Vista does indeed suffer from the 4GB barrier that Windows XP has,
> > unless
> >> you use the 64bit version of either operating system or use a server
> >> operating system. Note this is an article from 2005 so obviously Vista
> >> isn't
> >> inside this list but this is what I'm referring to.
> >>
> >> http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
> >>
> >> -Original Message-
> >> Sent: Thursday, October 02, 2008 9:02 PM
> >> Subject: Re: [hlds] Client crash question
> >>
> >> Vista doesn't have the same Paged Pool and Non-Paged Pool limits that
> >> previous Microsoft operating systems do.  Unless I'm mistaken, there is
> > no
> >> upper limit in Vista

Re: [hlds] Client crash question

[localhost]

Not sure how you're using the word "paging" and you've also got a pretty
important typo in your first sentence.
On 32-bit OS, each process can have up to 2gig of virtual memory, and the
kernel takes the other 2.  On a 32 bit OS with the /3gb switch, the kernel
only takes 1 gig, and _if the process has the correct flag saying it can
use memory over 2gig_ (large address aware iirc), it can then use up to 3.

On a 64-bit OS, the /3gb switch isn't necessary.  Instead, if a process has
large address aware set, it can address up to 4 gigs of memory.  If not,
still 2.

As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will
reduce the PPM size, and (unless you have large address aware programs that
need the virtual memory, have no beneficial effect)


On Sat, 4 Oct 2008 02:13:51 -0500, "Luke Lewis" <[EMAIL PROTECTED]>
wrote:
> Actually the /3Gb switch enables 32 bit operating systems to page memory
> above 3Gb of memory rather that memory is physical or virtual. In 32 bit
> operating systems client services or programs once they have paged above
> 2GB
> per instance will crash. The 3GB switch for 32 bit operating systems
allow
> programs to use up to 3GB of memory addressing per instance in fact with
> 3-4
> GB installed into the machine you should see equal virtual memory with
> physical memory in most cases. In default configuration Windows will
> allocate 2GB for the operating system and 2GB max for all other
operations
> such as services or programs. With the PAE switches, especially the
> /userva=
> switch you can allow the operating system to issue 3GB of paging/physical
> memory to each running instance allowing Windows to only use 1GB. Hence
> the
> reason all 32 bit windows operating systems only paging 4GB max.
Depending
> on USB devices and how memory are mapped on those most installations of
32
> bit (non-server) O/S's only will see a max of about 3.5GB with 4
> installed.
> The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb
> most
> people find the need to fine tune that usage in increments of 512, but
can
> be fine tunes in 16-32-64 bit increments if the program you are using
> recognizes this. Here is another link a bit more relavent(?) to Vista and
> explains the paging situation with 32 vs 64 bit O/S and covers some
server
> 2003 instances.
> 
>
http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders
> tanding-pool-resources.aspx
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
> Sent: Saturday, October 04, 2008 1:23 AM
> To: Half-Life dedicated Win32 server mailing list
> Subject: Re: [hlds] Client crash question
> 
> In this case, physical RAM has little to do with PPM.  Surely, 64-bit
> Vista
> makes a difference with RAM sizes above 4GB, but he's not running out of
> physical RAM, he's running out of PPM.  In XP and earlier, you'll want to
> try to keep the PPM usage below 150,000, which you can observe using
> System
> Information in Process Explorer.  With Vista, you really don't have to
> worry
> about it.
> 
> -Richard Eid
> 
> 
> On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis <[EMAIL PROTECTED]>
> wrote:
> 
>> Vista does indeed suffer from the 4GB barrier that Windows XP has,
> unless
>> you use the 64bit version of either operating system or use a server
>> operating system. Note this is an article from 2005 so obviously Vista
>> isn't
>> inside this list but this is what I'm referring to.
>>
>> http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
>>
>> -Original Message-
>> Sent: Thursday, October 02, 2008 9:02 PM
>> Subject: Re: [hlds] Client crash question
>>
>> Vista doesn't have the same Paged Pool and Non-Paged Pool limits that
>> previous Microsoft operating systems do.  Unless I'm mistaken, there is
> no
>> upper limit in Vista for Paged Pool memory.  So it does matter what OS
> you
>> are on.
>>
>>-Richard Eid
>>
>>
>>
>>
>> __ Information from ESET NOD32 Antivirus, version of virus
>> signature
>> database 3494 (20081003) __
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>> Sent Via http://www.gorillazsouth.com mail server.
>>
>>
>> ___
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> http://list.valvesoftware.com/mailman/listinfo/hlds
>>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
> 
> __ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3494 (20081003) __
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
> 
> 
> __ Information from ESET NOD32 Antivirus,

Re: [hlds] Upcoming MOD Dedicated Servers

[Luke Lewis]

When I clicked on the extra copies what I'm seeing is just my single extra
copy of HL2.

-Original Message-
Sent: Saturday, October 04, 2008 1:55 AM
Subject: Re: [hlds] Upcoming MOD Dedicated Servers

just got in the beta, doesnt do this for me, so is possibly an issue to do
with the transition process?

On Sat, Oct 4, 2008 at 3:49 PM, Joshua Handelsman-Woolf <[EMAIL PROTECTED]
> wrote:

> Odd, I'm seeing that too. Could it be the bootstrapper beta?
>
> DontWannaName! wrote:
> > When I installed Synergy and any other new mod from Steam, it shows that
> I have "2 extra copy" under the gifts column in Steam. Im running the new
> Steam Bootsrapper beta that came out today if anyone wants to try the new
> geo location algorithm to dl from servers faster, you'll find it there. I
> clicked the 2 extra copy link and besides it not being propper English it
> showed no extra copy, just my other extra copies :P
> >
> > Sincerelly,
> > DWN
 

__ Information from ESET NOD32 Antivirus, version of virus signature
database 3494 (20081003) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 




Sent Via http://www.gorillazsouth.com mail server.


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Re: [hlds] Client crash question

[Luke Lewis]

Actually the /3Gb switch enables 32 bit operating systems to page memory
above 3Gb of memory rather that memory is physical or virtual. In 32 bit
operating systems client services or programs once they have paged above 2GB
per instance will crash. The 3GB switch for 32 bit operating systems allow
programs to use up to 3GB of memory addressing per instance in fact with 3-4
GB installed into the machine you should see equal virtual memory with
physical memory in most cases. In default configuration Windows will
allocate 2GB for the operating system and 2GB max for all other operations
such as services or programs. With the PAE switches, especially the /userva=
switch you can allow the operating system to issue 3GB of paging/physical
memory to each running instance allowing Windows to only use 1GB. Hence the
reason all 32 bit windows operating systems only paging 4GB max. Depending
on USB devices and how memory are mapped on those most installations of 32
bit (non-server) O/S's only will see a max of about 3.5GB with 4 installed.
The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb most
people find the need to fine tune that usage in increments of 512, but can
be fine tunes in 16-32-64 bit increments if the program you are using
recognizes this. Here is another link a bit more relavent(?) to Vista and
explains the paging situation with 32 vs 64 bit O/S and covers some server
2003 instances.

http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders
tanding-pool-resources.aspx

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid
Sent: Saturday, October 04, 2008 1:23 AM
To: Half-Life dedicated Win32 server mailing list
Subject: Re: [hlds] Client crash question

In this case, physical RAM has little to do with PPM.  Surely, 64-bit Vista
makes a difference with RAM sizes above 4GB, but he's not running out of
physical RAM, he's running out of PPM.  In XP and earlier, you'll want to
try to keep the PPM usage below 150,000, which you can observe using System
Information in Process Explorer.  With Vista, you really don't have to worry
about it.

-Richard Eid


On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis <[EMAIL PROTECTED]> wrote:

> Vista does indeed suffer from the 4GB barrier that Windows XP has, unless
> you use the 64bit version of either operating system or use a server
> operating system. Note this is an article from 2005 so obviously Vista
> isn't
> inside this list but this is what I'm referring to.
>
> http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
>
> -Original Message-
> Sent: Thursday, October 02, 2008 9:02 PM
> Subject: Re: [hlds] Client crash question
>
> Vista doesn't have the same Paged Pool and Non-Paged Pool limits that
> previous Microsoft operating systems do.  Unless I'm mistaken, there is no
> upper limit in Vista for Paged Pool memory.  So it does matter what OS you
> are on.
>
>-Richard Eid
>
>
>
>
> __ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3494 (20081003) __
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> Sent Via http://www.gorillazsouth.com mail server.
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

__ Information from ESET NOD32 Antivirus, version of virus signature
database 3494 (20081003) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

__ Information from ESET NOD32 Antivirus, version of virus signature
database 3494 (20081003) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 




Sent Via http://www.gorillazsouth.com mail server.


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds