Ahem, resource meters are not all that they are cracked up to be either.
Have you tried to write one? There are so many variances between machines
that it takes a whole lotta lovin to get them right. I have written one
which works 'reasonably' well for my ProRem software. It never comes up on
the Main PC even if its memory drops down to hundreds of K, but on the
Notebook, if you sneeze at it, it changes colour.
Thats sort of why I mentioned the Ramboost program, if for nothing else, it
gives a very good indicator of what is going on with system RAM.
BTW Pat, who told you to use 64Mb of fixed swapfile?, there is a formula; I
believe if you are using fixed it should be around 4 x RAM.
But here is anothers opinion quote 'Over ride the Win95 virtual memory
settings. Win95 gives the impression that it knows best, but it has been
proven that it doesn't. A general rule is to set the Virtual Memory setting
to three (3) times the system memory, i.e. system memory = 32Meg, Virtual
Memory = 100Meg.
If Win95 is not constrained it will eventually cache into Virtual Memory all
of the software that is you regularly use. An example of this was a 486DX40
was taking 50 seconds to load Word, and after setting the Virtual Memory
this was reduced to 5 seconds. The machine would also boot up and shut down
much faster after the changes had been made.'
Cheers,
Al+
> > I have to agree with Alistair and Aaron's comments on this.
> > Win95/98 is not
> > the problem,
>
> Oh yeah? I regularly see the resource meter yellow and red on my PC with
> just a small number of applications open. It used to be much worse in
> Windows 3.1, we used to run an Access database that exported its data to
> excel, with just those two programs running the meter would regularly dip
> into the red at which point the system crashed.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
