Don't know.


You could set your system time ahead 2 months then run memturbo to find out.

Here's another sheet which shows Win9x CPU/memory usage while using MemTurbo:



You can see that some physical memory (red) is held back (around the first horizontal line above zero... which is called "target RAM"). The computer stays very stable for hours and everything works suprisingly fast, no exzesive page swaps as before - I like it.
However you see the virtual memory (yellow) is increasing. I expect when I continue file sharing for days (without reboot), the limit is reached and we running out of resources again. If you wanna share for days without reboot the best idea might be to switch over to Win2000/XP.... or wait for the Xolox Linux version...

Attached Images

gnutella_resource2.gif (10.8 KB, 376 views)

my problem is when ive had other apps running, close them..and then go to Xolox.. my resources drop down to 0%...and i can't do anything.

When i open xolox on a fresh restart of my system, and have memturbo going.. then I can use it.

When seeing the sheets/comments I made above, you shouldn't wonder.
The heap management of Win9x/ME is leaking. When starting Xolox/Bearshare you first see the CPU is running high and allocates a high amount of RAM. If there is not enough RAM, programs do not work (happens to e.g. Irfanview) or the system becoms very slow due to exzesive page swapping. My advice: Spend your computer more RAM (it's very cheap at the moment) or upgrade Windows to Win2000/XP (if you really need to - never change a running system).

Heh..

if 320 MB of ram isn't enough memory for a single application then i'm looking for another program..

It's NOT a application programm, it's a Win9x/ME problem.

Another app = same problem. Did you see above I tested more than Xolox. As long as you reboot every 1-2 days you can work without ANY problems at all (windows isn't famous for long uptimes, hehe). Should be okay for normal user, but if this does not satisfy yourself, upgrade Windows (don't forgot to backup all your private stuff).

I'm curious why people are saying that xolox is stable on win2k? Because I seem to have problems with it getting into a state where it says "Connecting..." infinitely and can't seem to make new connections at all. I tried to break it out of its lockup by clicking "Pause download" and then it got stuck saying something like "Pausing download...". The right click menu for pause/cancel download was then greyed out and I couldn't do anything else. Existing downloads seem to continue downloading as long as the connection isn't broken. This has happened a couple times, I think always after Xolox has been running 36+ hours.

I am using ZoneAlarm.

I don't seem to be getting any huge memory leak, though performance monitor seems to be showing Xolox's working set as very slowly increasing. Overall I still show 146400k of free physical memory, 392672k total, 195250k system cache. CPU is hovering around 10%.

Xolox and Zone Alarm don't mix. Doesn't matter the OS youre using. You have to turn off ZA if youre going to use Xolox or find another firewall. Gnucleus works better with ZA..IMO

This freeware program has helped me avoid those nasty Xolox low resource crashes.

http://www.jfitz.com/software/RAMpage/index.html


Things are running much smoother for me now.

It's also happening in Windows XP. 512Meg, Athlon 1.33 - After some time (varying from 15 Minutes to 8 hours) the system resources are low and the CPU is at about 100%. It's impossible to close the program. I usually shut down the connection and then xolox causes an exception.

No memturbo but Norton Firewall.