Are you saying that in one hour you requested 38 different files? And you use a dial-up? If I'm reading you correctly, I'd disconnect you too. I've got a fairly fast connection, but to keep things under control I've limited the number of simultaneous uploads. Within a few minutes of me firing up the client software, all those upload slots are in use and they stay in use until I shut down. From looking at the logs, I know that I'm rejecting at least 100 upload requests for every one that gets through. I can't stand to see one of those slots poking along at 500 bytes/sec, which is about where you'd be if you were downloading half those 38 files on a dial-up.

It's like I'm running a very busy tavern. There are only so many seats at the bar. If you're sitting at one of them, you better be drinking at a reasonable rate. I've got customers six deep waiting for a seat to open up and if you're not going to make good use of yours, I'm going to kick you out and let a real drinker have your stool.

I'm not saying you have to be downloading at DSL speeds, but I at least want to see a good percentage of your dial-up bandwidth dedicated to that transfer. If you can't keep up at least 1k bytes/sec download speed, you don't want that file bad enough. At least that's my take on it.

I HAVE a cable modem and I can't connect to download most of the stuff I try because all the available upload slots on the target clients are in use. To go back to the tavern analogy, it's like all the seats at the bar are being used by people slowly sipping at their drinks while the heavy drinkers are standing outside waiting for a seat to open up. If the barkeep doesn't get rid of those slow drinkers he's going to go out of business. If Gnet doesn't figure out how to efficiently manage the available bandwidth, people are going to get tired of seeing screens full of "Queued" statuses and they'll go looking for alternatives. People on dial-ups requesting dozens of files simultaneously only compounds the problem.