[Anti-leech] MxMoni

[p2p-sharing-rules]

I'm using MXmonie v1.28Eb.I guess this version that your talking about isn't in a zip file.
It still works for WinMXv3.53,even though it say it's for WinMX v3.3x.

There's also another antileech software called LeecHammer.

[quicksilver]

Hmm P2P , I used that for a while, need to reboot regularly as it seems to eat ram .

[p2p-sharing-rules]

Yea , from what i read it has to do with a problem within winmx.

Quote From LeecHammer FAQ:

After running WinMX and LeecHammer for long periods of time, your system becomes low on memory, unstable or locks up.

This is something I am working on minimizing, but the problem is due to internal memory leaks within WinMX itself. As a result, I cannot fix this directly. LeecHammer itself is quite efficient and requires very little memory. However, because it communicates with WinMX often and on a regular basis, it accelerates WinMX's memory problems.

Any anti-leech tool that communicates with WinMX will eventually exhibit the same problem. How long your system runs before experiencing memory problems depends on a few factors:

* How long WinMX has been running without a break.
The longer it runs without shutting it down, the more memory is drained. It is HIGHLY RECOMMENDED that you simply shut down and re-start WinMX periodically! Doing so before problems appear will keep things running smoothly. How often you should re-start WinMX depends on how active and large your upload queue has been.
* The size of your queue.
The larger your queue, the quicker the system will get low on memory.
* How often LeecHammer checks your queue.
The more often it checks, the sooner you might experience problems.
* Whether you are using a primary or secondary connection.
Primary connections require MUCH more memory. If you're experiencing slowdowns or sluggish performance, switch to a secondary connection! Actually this is something which is well documented about WinMX itself and is good advice to follow regardless if LeecHammer is running or not.

In general, the average user who runs WinMX for maybe a few hours at a time will probably never experience memory problems. However, those who run WinMX around the clock for days on end, should probably shut down and restart WinMX at least once per day.
Simply doing that will go a long way toward ensuring trouble-free operation.

Note: If anyone from Frontcode is reading this and cares to contact me concerning the memory leaks in WinMX, I'll be more than happy to share the information I've gathered and provide details about the nature of the leaks and where they are occurring.

[Rat]

I thought most of the memory leaks in WinMX had now been plugged. That ought to mean that the need to restart winmx and/or the computer should be a far less frequent thing.

[quicksilver]

Well what a nice guy , he offers to help frontcode with fixing this annoying problem.
I suppose they might read his announcement someday

[KM]

Well what a nice guy , he offers to help frontcode with fixing this annoying problem.
I suppose they might read his announcement someday

i wouldn't hold your breath...

i've already given frontcode some info on other (much more serious) issues and also offered to fix it myself if it wasn't a high enough priority to spend time fixing... getting a response from frontcode is even harder than getting Bill to start giving Microsoft Windows away for free

[JASON]

getting a response from frontcode is even harder than getting Bill to start giving Microsoft Windows away for free

Click Here

[quicksilver]

Unfortunately Jason thats Microsofts cynical plan to tie you in to their software by making sure your only trained using their products

[JASON]

That's probably right Quicksilver.. But those free downloads were nice
btw; I'll add that all IT students in the UK are elligable for it too

[KM]

btw; I'll add that all IT students in the UK are elligable for it too

not really, you'd be stoned to death if anyone found out you had a legal copy of windows

..but thats getting off topic a little