DUX COMPUTER DIGEST

 

Site Search

Site Info

Home » Forums » Forum Archives » Operating Systems » Topic # 18

Reclaiming System Resources ( or 'flushing' memory )
Stevelee Jul-10-00 07:27 PM
Hi Larry, and anyone else who reads this.
I am hoping that you can help me on this one.
A few of the PC's that belong to friends and colleagues seem to regularly run out of system resources and refuse to open files due to lack of available memory etc., while others never seem to have this problem.
This leads me to two questions :-
1. Why are some PC's affected this way and not others - is there a setting within the OS somewhere that can be toggled on or off, and that causes the memory to be 'flushed' correctly when a program is closed?
2. Is there a way of manually quickly reclaiming these resources without resorting to rebooting? ( I seem to recall from my old Amstrad CPC days that there was a command in its BASIC OS that enabled you to clear the memory of any redundant data that had built up and was clogging things up.)
Best Regards,
Steve Lee.

1. RE: Reclaiming System Resources ( or 'flushing' memory )
lbyard Jul-10-00 08:10 PM
In response to message 0
Steve, Windows and modern apps do a much better job of cleaning-up after themselves… you can bring-up the Task Manager with Ctrl-Alt-Delete and shut down programs. But you better be sure you know what you are shutting-down. A lot of times when Windows complains it does not have enough memory, it really is running-out of disk space. Check C:\>windows\temp and Temporary Internet files, etc. If you are running Win 98 use Start, Programs, Accessories, System Tools, System Info, Tools, System Configuration Utility, Startup Programs, to see what garbage is starting-up when Windows does. Or Start, Settings, Start Menu Programs, Advanced, Programs, Startup… Don’t disable anything you don’t understand. Buy more memory. They should have 32 Mbytes or more. Rec. 64 Mbytes; 128 is nice. Larry

2. RE: Reclaiming System Resources ( or 'flushing' memory )
Stevelee Jul-10-00 08:37 PM
In response to message 1
Hi Larry.
Thanks for your very (!)quick response - much appreciated.
The machines it happens on mainly are one with 32 Mb, and two with 64 Mb. Disk space I am not sure of, but I suspect that they all have a few hundred Mb left, if not a Gb or two. I shall check on that aspect. They are all running Win95 - I haven't yet come across a Win98 one that exhibits these symptoms.
I have checked what apps. are running in the background, and the answer is not many in two of the cases, quite a few ( 7, I believe it was ) in the other - a 64 Mb machine.
I take it that there is no way to manually clear the memory, as far as you know?
Best Regards,
Steve Lee.

3. RE: Reclaiming System Resources ( or 'flushing' memory )
lbyard Jul-11-00 00:34 AM
In response to message 2
One does not clear the memory. One kills tasks that are using memory. Larry

4. RE: Reclaiming System Resources ( or 'flushing' memory )
mthyng Jul-12-00 02:42 AM
In response to message 2
Give this shareware program a try.

http://www.memturbo.com/

Free for 30 days, then you have to register or uninstall. There are other freeware programs like this out there.


5. RE: Reclaiming System Resources ( or 'flushing' memory )
Stevelee Jul-13-00 05:21 AM
In response to message 4
Hi.
Thanks for the suggestion, mthyng. I am trying the program out and it is looking promising so far.
Thanks a lot,
Best Regards,
Steve.

6. RE: Reclaiming System Resources ( or 'flushing' memory )
bobj3 Aug-25-00 07:41 PM
In response to message 0


The following was posted to the Windows 98 Annoyances Discussion Forum

Subject: re: Memory not released after closing applications


I can tell you right now 64 Mb's of RAM is plenty for most thing's and contrary to what some people would have you believe more is not necessarily better. Lot's of RAM is nice if you run some big programs but for the most part your average user has easily 50% of their system resources free (and usually closer to 80%) It's not so much how much RAM you have as how efficiently it's being used. Window's doesn't do the greatest job of handling memory to begin with, but to make matters worse......because so much RAM is available programmers seem to be getting lazier in how they handle it with their programs.

One of the problems that causes slow down's is window's poor handling of the swapfile. There's a tweak I found on this site that I use and find it helps a lot to avoid too much slow down by forcing windows to use the RAM before going to a swapfile. Just open your system.ini scroll down to the <386Enh> section and add the line:
ConservativeSwapfileUsage=1
This is a nice little tweak because it forces windows and other programs to use RAM first and the swapfile second. It may not seem like much but if you consider that RAM is still faster than a swapfile......and with less swapping the programs in the swapfile in and out of memory it has to help. I like to listen to music a lot while I work and I use winamp......which is a memory hog. Prior to using this tweak it used to stutter and pause whenever I was doing something memory intensive......it doesn't since I used that tweak.
Bj


7. RE: Reclaiming System Resources ( or 'flushing' memory )
Stevelee Aug-25-00 08:31 PM
In response to message 6
Hi Bj.
Thanks a lot for your suggestion - I will give it a try as soon as I can.
I'll try and remember to post a message when I have tried it out.
Thanks again,
Steve.

8. RE: Reclaiming System Resources ( or 'flushing' memory )
MrStroker2 Mar-30-01 04:02 PM
In response to message 7
I just changed that setting on my windows ME lets see if it helps?..thank you mike

| Home | Guides | How to | Reviews | Online Store | FAQ | Forums | Forum Archives |
| Links | News | Newsletter | About Dux | Advertising | Contact Info | Privacy |