i am unable to upload faster than right around 107kbps...
just wondering why... yes /fsend is on
i can use other mediums to uupload at around 385kbps
including ftp

anyone else having this problem?
anyone know of any solutions?

Try typing /!REMOTE OFF and observing for a few mins the upload speed, does it increase significantly? If so, then your mirc is to busy doing other things to maintain sending at max speed.

PS are you talking kbps (kiloBITS per second here) or Kbps (kiloBYTES per second here as in 107K of file ?)

/remtoe on/off makes no difference
and its KB/Sec as mirc shows it

did u type REMTOE or was that a typo here ?

ya, it was a typo /remote on/off makes no difference

anyone actually have a upload greater than 107kB/s that could test/verify this bug?

Not via DCC

??
You confirming the bug or saying your isp doesnt supply you with a upload of greater that 107kBps?

Sorry, I guess I should've made that clearer..I've never gotten a DCC transfer over 107k (actually 100k).

I have gotten better than that using FTP

Can anyone else confirm this?

I would like to see it fixed in the next release....

Probbabbly more likely to get fixed if more than one or two people could confirm it.

Thanks

You've already requested someone to confirm it, posting again and again isn't going to help.

The DCC protocol is far from the greatest protocol to be used for uploading or downloading files. It's really not a surprise that you are not getting great speeds. Given how many people upload using mIRC now, I also find it unlikely it would have taken this long for some bizarre 107kb throttle limit bug be reported...I also question whether such a "bug" could actually exist in mIRC anyway.

Also try these commands:
/dcc packetsize 8192
/pdcc on

Do you experience this same problem with versions prior to 6.17? (and earlier than 6.16 too)?

Regards,

I have downloaded from a friend of mine from IRC who has a dedicated 10mbit upload server, and it was going at around 940kb/s, so I think there's not really a problem to upload at higher speeds than 107kb/s. I can't help with a solution I'm afraid, but atleast you know it's not something about mIRC being unable to send at over 107 kb/s.

I sent a 102MB file (test.rar) to another machine on my lan.

Machine 1 (192.168.1.2)
WinXP Pro SP2
1 x Intel Celeron D 2.93GHz - 1GB RAM
mIRC v6.17

Machine 2 (192.168.1.4)
WinXP Pro SP2
1 x AMD Athlon 500MHz - 512MB RAM
mIRC v6.16

[09:02] DCC Send of test.rar to Machine2 complete (00:02:03 849 KB/Sec)
Peaked at 936KB/Sec

[09:07] DCC Get of test.rar from Machine2 complete (00:01:57 893 KB/Sec)
Peaked at 0.98MB/Sec (1,003.52KB)

So I guess I cannot confirm this bug.

~ Edit ~

Mentality:

Quote:

The DCC protocol is far from the greatest protocol to be used for uploading or downloading files.

The test file (test.rar) came out perfect on both sides, it looks
like DCC is just as perfect (or imperfect) for sending/receiving
files as about anything else eh?

Umm, because something is not the greatest doesn't mean it doesn't work for anyone. It's well known and documented that the DCC protocol is worse than a lot of other protocols for sending/receiving files (such as FTP). We're not doing down this road of discussion though

Regards,

You turned down the road, not me.

DCC sends its own ACK packets. This is rather redundant, but that's how it works. When you are sending data to someone, they are constantly replying with 4-byte packets indicating how much data they have so far received. The various "speed up DCC" commands enable things such as sending packets before receiving the ACKs for previous packets, but it doesn't do this indefinitely -- eventually it will wait for the ACKs to catch up (else it would be wasteful, you don't even know the other end is there anymore).

What this amounts to is, your DCC send speed is probably being affected by the upload speed of the person you are sending to. Try sending to multiple people at the same time, and see if your total throughput is thus limited or if it is only on a person by person basis. Whatever it is, it can probably be blamed on the DCC send protocol itself and not mIRC directly, or some combination of networking parameters unknown to me.

-m-