Mx Monitor 1.28eb For Winmx [latest Sept. 20]
Leyland 154 Parts Manual. I have found via my roomy that mxmoni isnt quite wonderful. I use it rarely and only to auto upload to traders. Anything involving ignoring people off.
Problem is that any delay in mxmoni getting a browse, or a whois, results in sending someone who actually is sharing off to the ignore list. It works sorta OK if and only if, your connected to other connections that actually work (meaning mostly secondary). Lots of connections you make as a secondary to another primary are slow or even non-responsive. Yet the lil green light will sit there working just fine in WinMX. Another issue with mxmoni is that it will eat resources if you have many incompletes or people in your queue. (the roomate part).
His PC will slow to a crawl, the entire system including the clock. It has been doing that all the time for years, has nothing at all to do with the current attacks. He does have it set to scan anyone who enters queue, ignore people who supposedly share nothing, etc and he always runs it whenever WinMX is running. I have not had that problem.
I leave the thing totally off unless I hit upon some sharer who I am doing regular trades with. Yet another problem with mxmoni is that if you you have it running and then exit it, odds are fairly high that it will not only exit, but then crash WinMX itself and you lose all you queues and everything and have to start over. One more reason I hate to use it. (BTW, to any grammer Nazis out there, please feel free to STFU and you know who you are). Miners, you didnt say what version of Moni you or roomy use, but. I use a version 1.30 (Re-Fit by the Wraith) that seems reasonably well behaved Some of the settings that bug you can be adjusted, such as the delay time for a browse, and under what condition ppl get ignored It does have a wonderful lil feature i kinda wish WinMX had, a button to dump the whole iggy list. (WinMX only lets you remove 1 name at a time, I tried selecting several names and got trouble) I have not noticed any resource-hogging or memory leakage as you describe, mebbe The Wraith tweaked something under the hood to fix.
MX Monitor v1.28Eb Help. This section will display downloads being currently being managed by WinMX monitor. You use this to tell MX Moni where WinMX is. Last released english-language version. While MX Monitor does not seem to be developed/supported any longer, version 1.28Eb works very well with WinMX.
The crashing of WinMX is not a fault, its a design feature you can turn off, likely yours is set to close WinMX when Moni is closed.
Bubba's Winmx & Monitor's Idiots Guide to Trading! Contributed to the forum on January 31, 2006 by a guest poster: Bubba. Just want to say thanks to them for posting this and say that although we are unaware who the original author is of this one, there are many guides similar to this one floating around WinMX, this is a well done one. Great Job to the poster and author. Posted by Bubba follows: I got this from a guy in WinMX and I thought it might be of use. Naturally each person's own needs dictate the way they use WinMX and how they prefer to set it up, anyway I did find these tips valuable. INTRODUCTION: WinMX is a powerful P2P tool, one that allows its users a degree of options rarely seen in other P2P applications, something that becomes all the more true with the use of its excellent companion, MX Monitor.
The good side of this is that people can set WinMX up to do things pretty much the way they need and want; the bad is that inexperienced or foolhardy users will quickly be overflooded by settings and options they don't understand, leading to much confusion and misunderstandings in the WinMX network between users. This is a simple, basic configuration guide based on my own experiences over the years with using WinMX and its companion tool MX Monitor for the purpose of file trading, which hopefully will help you to sort out your difficulties and make your WinMX experience a better one (it may also get you off people's ban lists for a change Razz ).
WINMX SETTINGS ->QUEUING: -Before anything else, turn the 'When there are (.) change reported speed' option OFF. This is a vital step. Because if you let WinMX change your reported speed like this, your client will be considered by such tools as MXMonitor as a different user, and you will lose any trades in process with other people, likely ending up on their ignore lists as well. -'Max Downloads per user': set it to 1 or 2 at most, depending on your specific needs. I would recommend 1 nevertheless. Because a) there's only so much bandwidth you can get from a user, and multiple transfers will only divide that bandwidth up and increase the overhead, as well as the chances of time outs and disconnections.