RatioMaster 1.8.9 updated by SB-Innovation

[anon]

SB-Innovation Presents

>>>>>> RatioMaster 1.8.9 updated by SB-Innovation <<<<<<

╔═══════════════════════════╗
Coded by:
╚═══════════════════════════╝

>>>>>> RatioMaster <<<<<<

╔═══════════════════════════╗
Source:
╚═══════════════════════════╝

>>>>>> moofdev <<<<<<

╔═══════════════════════════╗
Updated by:
╚═══════════════════════════╝

>>>>>> Rebound & anon <<<<<<

╔═══════════════════════════╗
Supplier:
╚═══════════════════════════╝

>>>>>> anon <<<<<<

╔═══════════════════════════╗
Changelog / Features:
╚═══════════════════════════╝

Changelog:

Version 1.8.9
--------------
- Bug fix : fixed speed randomizer not accepting float values
- Bug fix : fixed crash on some systems by setting compatible font rendering
- Bug fix : fixed problem with some trackers and client files, when RM getting stuck waiting for server response
...
- Update : support for numwant node for Azureus client file (...) - Allowing for a more realistic Azureus emulation!
...

Version 1.8.8
--------------
...
- Feature : added ability to save list of peers per torrent ("Save list of peers" checkbox in Network/Miscellaneous).
...

Version 1.8.6
--------------
- Feature : added 'Reset Counters' button, to reset upload/download amounts to previous values
...

Version 1.8.5
--------------
- Feature : added another HTTP proxy support (UltraSurf and similar programs)
...
- Update : improvements to memory reader
...

Version 1.8.4
--------------
- Feature : added HTTP and SOCKS4a proxy support
- Feature : added UPnP port forwarding support
- Feature : added option to ignore connection timeouts
...

Version 1.8.2
--------------
- Feature : added ability to download new client files and translations directly from RM (tab Updates)
- Bug fix : corrected "Host" header that RM sending to tracker in some cases - No more ort issue!
...
- Small fixes and improvements that i forgot about. - Scrape now works!

Version 1.7.5
--------------
- Bug Fix : Improved handling of connection and response timeouts.
- Bug Fix : Fixed problem with sockets not being closed
- Update : Updated build in uTorrent emulation to uTorrent 1.6.1 (build 490)
- Feature : added AI based on neural networks
- Feature : added voice recognition.
- built an installer (THX CoreCore!)

Client Files

Last Update: 22.08.2009

- Azureus 2.5.0.0 *
- Azureus 2.5.0.2 *
- Azureus 2.5.0.4 *
- Azureus 3.0.0.6 *
- Azureus 3.0.0.8 *
- Azureus 3.0.3.0 *
- Azureus 3.0.3.4 *
- Azureus 3.0.4.2 *
- Azureus 3.0.5.0 *
- Vuze 3.1.1.0 *
- Vuze 4.0.0.0 *
- Vuze 4.0.0.2 *
- Vuze 4.0.0.4 *
- Vuze 4.1.0.2 *
- Vuze 4.1.0.4 *
- Vuze 4.2.0.0 *
- Vuze 4.2.0.2 *
- Vuze 4.2.0.4 *
- BitComet 0.63
- BitComet 0.79
- BitComet 0.84
- BitComet 0.85
- BitComet 0.86
- BitComet 0.87
- BitComet 0.88
- BitComet 0.89
- BitComet 0.90
- BitComet 0.91
- BitComet 0.92
- BitComet 0.93
- BitComet 0.94
- BitComet 0.95
- BitComet 0.96
- BitComet 0.97
- BitComet 0.98
- BitComet 0.99
- BitComet 1.00
- BitComet 1.03
- BitComet 1.04
- BitComet 1.05
- BitComet 1.07
- BitTorrent 6 (Build 4747) *
- BitTorrent 6 (Build 5535) *
- BitTorrent 6.0.3 (Build 8642) *
- BitTorrent 6.1 (Build 11862) *
- Deluge 1.1.9 ***
- Halite 0.3.1.1 ***
- Transmission 1.06 (Build 5136) **
- µTorrent 1.5 *
- µTorrent 1.6 (Build 474) *
- µTorrent 1.6.1 (Build 483) *
- µTorrent 1.6.1 (Build 489) *
- µTorrent 1.6.1 (Build 490) *
- µTorrent 1.7 (Build 1875) *
- µTorrent 1.7.1 (Build 3360) *
- µTorrent 1.7.2 (Build 3458) *
- µTorrent 1.7.3 (Build 4470) *
- µTorrent 1.7.4 (Build 4482) *
- µTorrent 1.7.5 (Build 4602) *
- µTorrent 1.7.6 (Build 7859) *
- µTorrent 1.7.7 (Build 8179) * (THX CoreCore!)
- µTorrent 1.8 (Build 11813) *
- µTorrent 1.8.1 (Build 12616) *
- µTorrent 1.8.1 (Build 12639) *
- µTorrent 1.8.2 (Build 14153) *
- µTorrent 1.8.2 (Build 14458) *
- µTorrent 1.8.2 (Build 15167) *
- µTorrent 1.8.2 (Build 15227) *
- µTorrent 1.8.2 (Build 15296) *
- µTorrent 1.8.2 (Build 15357) *
- µTorrent 1.8.3 (Build 15728) *
- µTorrent 1.8.3 (Build 15772) *
- µTorrent 1.8.3 (Build 16010) *
- µTorrent 1.8.4 (Build 16150) *

* = info_hash issue fixed
** = generated peer_id and key improved
*** = info_hash issue fixed and generation improved

Weitere Wünsche für Client-Files sind immer Willkommen.
Of course you can post client file wishes for any client.

Make sure you don't use the memory reader on modded uTorrent builds, for example - it can lead to problems.

We have permission from the coder to post this tool!


╔═══════════════════════════╗
Password:
╚═══════════════════════════╝

c5ejh7mg20ad12pt

[anon]

Well, I guess you can still get a client file for that via the built-in autoupdater.

[tj0ckis]

CRAP! I was just suppose to try flashing for the first time today! So I've heard that you take a really high upload speed then you set RM to stop after the desired amounts of GB upload you want.

So I just choose 9999999kb/s then I set it to stop after it had uploaded 25GB! So it started and stopped but now when I check the TL site it stand I've uploaded 9.31TB!!! Why didn't it stop after 25GB? Was it a too fast speed?

Any chance of me not being banned? I was not in top10 when i checked.

Should I just continue to seed the torrent normal in uTorrent or should I stop all my TL torrents?

[anon]

So I just choose 9999999kb/s then I set it to stop after it had uploaded 25GB! So it started and stopped but now when I check the TL site it stand I've uploaded 9.31TB!!! Why didn't it stop after 25GB? Was it a too fast speed?

It'd have been a lot better if you had used 1000000kB/s (1GB/s).

All you can do now is hoping you don't get banned, lol.

[tj0ckis]

It'd have been a lot better if you had used 1000000kB/s (1GB/s).

All you can do now is hoping you don't get banned, lol.

I searched for flashing and I found a thread where you had written 999999kb/s so I thought that would be okey.

Why would that been better? Wouldn't that have bugged RM? So I won't get banned?

[anon]

Yes, but you said you used 9999999kB/s in post #212 - note the extra 9.

Why would that been better?

Because at 1GB/s you'll have to stop it after just 25 seconds.

[tj0ckis]

Yes, but you said you used 9999999kB/s in post #212 - note the extra 9.



Because at 1GB/s you'll have to stop it after just 25 seconds.

Aha okey I thought that flashing was suppose to happend in just a few seconds.

Can anyone tell me a % of my not being banned? Does it help if I say that I created the account 5 hours ago

It's okey if I get banned I have another account.

EDIT: Crap I've been banned! Okey so now I know that I can't trust RM to stop by itself after any written amount.

[anon]

Does it help if I say that I created the account 5 hours ago

It didn't Well, at least you have another account.

Don't rely on the RM to stop by itself when flashing - do it yourself.

[morenutti]

hello I wanted a info on this program I am trying to use it but I have noticed a thing I have ended to unload my film then I have put with rm in upload it I only dull nothing dw na I have gone on the traker and the film that I have ended to unload gives me I am unloading that it newly you can say to me like never I gave I have it to use in simultaneous mentee I am unloading the film thanks

[anon]

Make sure the finished % is set to 100.

[banneduser]

works fine for me but
how do we know whether use tcp listener has to be used on that specific tracker or not

[alpacino]

works fine for me but
how do we know whether use tcp listener has to be used on that specific tracker or not

You have the option to use tcp listener if you want/need to appear to the tracker as "connectable".

[anon]

And being connectable prevents you from standing out. You won't need to tick if another app (your real BitTorrent client) is already listening on that port, but it won't do any harm, unless you start the RM first and then the client.

[banneduser]

And being connectable prevents you from standing out. You won't need to tick if another app (your real BitTorrent client) is already listening on that port, but it won't do any harm, unless you start the RM first and then the client.

well correct me if i am wrong that if Torrent client is already listening on the same port and I start RM with same torrent then its a ban if scripts are good .
But if I close the client wait for few minutes then start with RM with tcp listener then i shouldnt be in the danger list
correct ??

[vDD+wR]

well correct me if i am wrong that if Torrent client is already listening on the same port and I start RM with same torrent then its a ban if scripts are good .
But if I close the client wait for few minutes then start with RM with tcp listener then i shouldnt be in the danger list
correct ??

Yes, I'd say so.
Exactly, why do you want to run the same torrent in both programs at the same time? Or did you ask for a better understanding?

[thecoolest]

as i say when you get key & port number & peer id then u can close utorrent...i always do..works like charm..also it saves that config file so u dont have to do all that things again...