Mem Issues? I've seen a bunch of complaints about XoloX chewing up memory/resources. As of this writing I've had it running over 8 hours straight UL'in and DL'in, and my current mem uses (according to Win2k Task Manager) is:
Opera.exe 21,452K (2 hours run time, w/4 pages open)
iexplore.exe 16,564K (30 min run time, w/1 instance open)
Morpheus.exe 10,356K (4 hours run time, 4 DL's, 2 UL's)
xolox.exe 9,796K (8 hours run time, 2 DL's 0 UL's)
And this is on an old wood burning P-III 550 lap top with 256MB running Windows 2000 Pro (SP2).
If I still had Lamewire or Bear Don't Share (Morpheous will soon be regedited from my system as well) they would also be above XoloX on the process tab.
Not having to go behind a "free" P2P program and remove the trojans (read cydoor, newdotnet, and the like) that the anti virus companies seem to ignore when the new definitions come out was really nice (I did go in and check after the install tho'..trust no one).
No chat, no ad windows no need to 127.0.0.1 a bunch of new servers every time I want to use it. All in all not a bad little app, not really up to the hype I read before installing it, but still better than the alternatives.
Yeah, yeah I know "But the ad's pay the bills" the Oct-Nov 2000 nosedive proved that ad's don't work no more.
My rant, like it, love it or don't read it.
P.S. xolox.exe has dropped to 5th place at 5,112K beolw vsmon.exe at 7,320K.
Paranoia is my religion. |