I get a popup box that keeps comming up when I try to close Xolox completely, it says "Xolox has caused an error in {unknown} and will now close". But the popup box won't stay closed. I have to restart to get rid of it. It mainly happens when there is an upload or download in progress (when I close Xolox).
I use Windows ME and have a cable connection. (Xolox 1.12)
How do I fix this?

750 MB Processor
320 MB RAM
30 GB Hard Drive (9 GB free)
11+ GB Shared (2000+ files)

try using MemTurbo or upgrading Windows. Did you read the other threads about low resource or dammaged memory?

MemTurbo and NetTurbo have fixed things up.
Thank You!!!


http://www.netturbo.com/downloads.html

cool man.

Windows 9x/ME heap management is bad (however I don't know why this crashs Xolox, strange). Read more details here: http://gnutellaforums.com/showthread...&threadid=3831

I'm not entirely sure that it's the heap management of Win 9x alone. 1.11 ran fine on my system. 1.12 bogged it down to a standstil. After reading the suggestions here I got myself memory Zipper plus (which basically does exatly the same thing as Memturbo). That made it better ... but not entirely. The system will still crunch slowly to a halt and sometimes even hang (though I'm not sure that's Xolox' problem).

When looking further into the whole mess, I found out that Xolox will take up 100% procent of my CPU-Time after a while. Not initially, but after two or three hours it will invariably be that way. Even if I push Xolox back to low priority (Mem Zipper can do that to tasks) Xolox will still eat up 80 to 90 percent of cpu-time and it will also have a severe impact on my downloadrate.

Mind you, I only have a humble PII/400, but pushing around a few TCP-Packets (and not doing anything else!) shouldn't have that kind of impact, should it?

Another thing I noticed is that, when I try to quit Xolox while it is still running, it recently will crash bigtime for me. Solution: first cut my internet connection THEN quit Xolox - works fine.

So - crossing my fingers and waiting for V1.13 ...

Hmm, I did some long turn meassures with my WinME box (the sheets in the other mentioned thread). I see only a high CPU consumption at the beginning, especially when indexing your shared files the very first time (just wait until it's done). Time by time it may happen that Xolox merge together downloaded partials and create the final file.... this cause a "harddisk heart attack" yet and maybe use 100% CPU for some seconds. This "bad" behaviour has allready reported.

I usually let Xolox run the whole day at office, as long as I do not play online (need fast pings) or do time critical OpenGL testings (high CPU usage). Usually I have other apps running, Winamp, mIRC, my compiler and grafix tools and a webbrowser. Make sure that you spend enough RAM for your computer. I have no big disadvantages together with Xolox... at least not more than I had with Bearshare (daily reboot).

Someone told their is a problem with a windows Packetfilter/Firewall Software, while we use a Linux-Firewall concept, I can't report problems from here.

Moak

Ctrl+Alt+Delete+Enter will end a system popup box that won't stop coming back. (No restart needed)

Also if you defrag more often, you use less RAM. Files downloaded from Xolox can end up very fragmented. Partials are especially fragmented. An average defrag for me frees 50 to 100 MEG of RAM. (I defrag once or twice a week)