Xolox on Win ME sucks up resources
 

Got Xolox a few days ago, now when ever starting my Win ME machine, it's dropped as low as 4% remaining resources just after startup.

I've run MSCONFIG and taken Xolox out of startup, but it still happens. I get resource errors after just a few minutes of use. I've got MSCONFIG and startup stipped to almost nothing, yet I still have in some cases less than 25% resources available running on MS Messenger and Xolox.

What gives?

Q. How do I stop XoloX from launching at startup?
A. During install you had the option to have XoloX launch during start up or not. If you would like to stop XoloX from launching at startup simply go to Start > Programs > Startup and delete the XoloX Icon.

http://www.xolox.nl/client/support/faq.html#general

It sounds like a Memory issue to me, if MS Messenger and Xolox can’t be run at the same time. How much RAM do you have? It’s best to have at least 128M of RAM just to run Xolox at peak efficiency.
I use a Windows ME too. I have found that a memory defrag program like MemTurbo, RamPage, RAMbooster, or others makes WinME run a lot better. I have 768M of RAM now, and I still use MemTurbo to keep my system running smoothly. Most of the available memory recovery (RAM defrag) programs are free, and the ones that aren’t should be.

I've never had a problem on windows XP, although both XoloX and Kazaa have had peaks on mine

Highest RAM usage I've ever seen from Kazaa: 218mb
Highest RAM usage I've ever seen from XoloX : 91mb

Normally both stay behaved and under 20mb.

Windows ME has a memory leak that shows up under cretin conditions, like running a P2P, or a full system virus scan. Xolox may not use more than 91mb at peak usage, but WinME will waste all the RAM you have (causing your system to grind to a halt) unless you have a memory defrag program.

:rolleyes: Speaking of Defrag… I neglected to mention that a fresh defrag of your HD will free some resources and help Xolox (or any P2P) run better.

I've gotta get XP
 

I have Win ME and Xolox does use alot of resoruces. Even with a memory optimization tool I find Xolox using most of the resources on a AMD 1800+ with 512 MB RAM.