Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
Orf Bartrop <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Sat, 3 Apr 2004 13:29:39 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
Could it be that recovering every 30 mins is recovering memory but there
is only a minimal amount to recover. If you added all these 30 min
recovery bits together then you may end up with 100 Mb over 24 hours. In
other words it is working as required.

I am assuming that FreeRAM will recover RAM every 30 mins or if the RAM
drops below 128 Mb it will recover as soon as the CPU limit allows.

On rereading your message I am left wondering how you are determining
the 100 Mb leakage after 24 hours if FreeRAM is not picking it up. Are
you comparing the free RAM at bootup with the RAM after 24 hours? If so,
the difference may not be leakage. Windows seems to put some things in
virtual memory that one would think should remain in actual memory if
there is room. Perhaps when these programs/data are required they are
put in real memory and that is where they stay. Also, after running some
programs they may leave certain data in memory  in case you rerun the
program or they rerun automatically. Antivirus, firewalls, spy detector
programs could fall into this category.

Orf

Tom Mayer wrote:

>I have the interval set at 30 minutes, the lower RAM limit set at 128MB, and
>the CPU do not start limit set at 15%. Even when I force an "auto free", it
>normally results in little or no increase in physical RAM. Over a 24 hour or
>less period I normally encounter an approximate 100MB memory leakage which
>FreeRAM XP Pro is not preventing/recapturing.
>
>I have sent a follow up message on this subject that might interest you.
>
>Thank you for your input.
>
>Tom Mayer
>
>
>
>In the FreeRAM XP Pro settings (right click icon) under "Memory" you can
>determine when RAM is to be freed. I have mine set to automatically
>recover RAM when RAM goes below 32 MB (I have 512 Mb). It can be set at
>any figure or can be done on a time basis such as every 30 minutes. Also
>there is a setting that stops FreeRAM XP Pro running if the CPU is above
>a certain figure.
>
>Suggest you have a look and change the settings to suit your requirements.
>
>Orf Bartrop
>
>               The NOSPIN Group Promotions is now offering
>              Mandrake Linux or Red Hat Linux CD sets along
>             with the OpenOffice CD...  at a great price!!!
>             http://freepctech.com/goodies/promotions.shtml
>
>
>

             PCSOFT maintains many useful files for download
                     visit our download web page at:
                  http://freepctech.com/downloads.shtml

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV