Log in

View Full Version : a feature needed for WinMX

2004-08-07, 18:21
Look at the attached screenshot here. I normally have WinMX running with a bandwidth restriction of 10 KBytes/s and one slot open. The problem with WinMX is that the slot could be occupied by someone who is downloading at a really slow rate, and taking several hours to complete one song. I don't know if that is due to multisourcing on the part of the person, or an attempt by the RIAA to tie up the slots of people. In any case it works. WinMX has no feature to cancel download speeds if they are too slow. So queues are tied up by slow people. A solution would be for me to open up more uploading slots, but I don't like that solution because it makes people wait longer to download their song. Look at the screenshot and you will see that there are a total of 8 uploads occurring by 6 unique users. For the screenshot I wanted to close WinMX down and restart the computer, so I started everybody in the queue and then disconnected from the network. As you can see only the top two people are going at full speed. Everybody else is going at a reduced speed, and they should all be canceled for tying up my slots. That's four unique users out of six tying up my slots with slow downloads.

eMule uses bandwidth efficiently, and makes sure that someone is always uploading from me and using my bandwidth. But it is not as reliable as WinMX and after running it for a couple of days just stops working, until I restart my computer.

2004-08-08, 10:31
so whats goin on E?

2004-08-21, 07:08
interesting. and you could be right. it could be the riaa. and also unfortunate that your songs seem somewhat rare, making it hard to use the multisourcing. i think it would help, not hinder the upload speeds.
maybe i am not understanding...why not just cancel these slow speeders?
can they honestly blame you? more than likely newbies who don't know how to tweek their app. there are way too many people out there that they can receive the songs from, they should be trying different users until they find the best speeds. that's what i do.

2004-08-21, 15:57
maybe i am not understanding...why not just cancel these slow speeders?

I would like WinMX to do it automatically so that my queue is not tied up. That is the feature it needs. Most of the time I let the program run and I am not there to manually cancel slow uploaders. I do not micromanage my queues.

2006-01-14, 19:12
If you are like I am and are lacking in the "technical skills" department, but at the same time, miss using WinMX (http://www.vladd44.com/mx/), there is a quick, easy and free solution it is called MXPIE (http://www.MXPie.com). There is no spyware or anything else bundled with it. For those a little more savvy and courageous, there is even a manual option.

So come on back to WinMX, and download to your hearts content. Thanks to these updates, not even the power of the RIAA can stop a network.

IF you have downloaded WinMX and still cannot connect, you can even get personalized realtime help. Just go to this link WinMX Channels (http://www.vladd44.com/phpbb2/viewtopic.php?t=6514) Copy the Room name appropriate for your Language and paste it into your WinMX chat screen, then press the Join Button. This works on version 3.53 and up even if you are not connected. It allows you to join into chatrooms set up for you to get immediate help.

Everything you need at the MXPIE Website (http://www.MXPie.com) Free and Spyware free.

I have also found a site for Computer problem (http://www.gemini777.net) that is nice, prompt and VERY helpful. If there is a problem you need an answer to, they can help.

Realtime help available for WinMX 3.53 users having trouble getting connected. Go to WinMX Channels (http://www.vladd44.com/phpbb2/viewtopic.php?t=6514).

2006-01-15, 04:56
Another way to get the old WinMX client working on a WPNP variation is by way of WinMX Group (http://www.winmxgroup.com/). So now there are two versions of WPNP running. What are the statistics of the two communities in terms of their sizes?

There's not much hope for the future of WinMX because it was a closed source application. They should rename it to HearnMX, because developer Kevin Hearn refused to let it grow beyond himself. He smothered his own baby to death.