RatioMaster 1.9.1 updated by SB-Innovation

[anon]

SB-Innovation Presents

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

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

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

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

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

╔═══════════════════════════╗
Client file credits:
╚═══════════════════════════╝

>>>>>> Rebound <<<<<<
>>>>>> anon <<<<<<
>>>>>> HellD0t <<<<<<
>>>>>> CoreCore <<<<<<
>>>>>> Vation <<<<<<

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

Changelog:

Version 1.9.1
--------------
- Bug fix : fixed big memory leak in some cases
...
- Update : compiled with VS 2010 and tested on Win7 64bit :)

Version 1.9.0
--------------
- Bug fix : fixed several problems with parsing some torrent files - The filesize bug with PT torrents is fixed!
- Bug fix : fixed several resource leaks
- Bug fix : fixed startup crash on some systems and added more robust error message for such cases
- Update : new translation and client files (23 languages)

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 port 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: 29.08.2010

Spoiler Click >>>:

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
Vuze 4.2.0.8
Vuze 4.3.0.6
Vuze 4.3.1.0
Vuze 4.3.1.2
Vuze 4.3.1.4
Vuze 4.4.0.0
Vuze 4.4.0.2
Vuze 4.4.0.4
Vuze 4.4.0.6
Vuze 4.4.1.0
Vuze 4.5.0.0
Vuze 4.5.0.2
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
BitComet 1.13
BitComet 1.14
BitComet 1.16
BitComet 1.18
BitComet 1.20
Halite 0.3.1.1
Halite 0.3.1.2
µTorrent 1.5 (Build 437)
µ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)
µ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)
µTorrent 1.8.4 (Build 16286)
µTorrent 1.8.4 (Build 16301)
µTorrent 1.8.4 (Build 16381)
µTorrent 1.8.4 (Build 16442)
µTorrent 1.8.4 (Build 16667)
µTorrent 1.8.4 (Build 16688)
µTorrent 1.8.5 (Build 17091)
µTorrent 1.8.5 (Build 17414)
µTorrent 2.0 (Build 17920)
µTorrent 2.0 (Build 18097)
µTorrent 2.0 (Build 18296)
µTorrent 2.0 (Build 18488)
µTorrent 2.0 (Build 18620)
µTorrent 2.0.1 (Build 19078)
µTorrent 2.0.1 (Build 19248)
µTorrent 2.0.2 (Build 19648)
µTorrent 2.0.2 (Build 20165)
µTorrent 2.0.3 (Build 20664)
µTorrent 2.0.3 (Build 20683)
µTorrent 2.0.3 (Build 21177)
µTorrent 2.0.4 (Build 21431)
µTorrent 2.0.4 (Build 21515)
µTorrent 2.0.4 (Build 21586)

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

If you want the latest client files but don't have the Member title, register at the Moofdev.net forums!

We have permission from the coder to post this tool!


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

iaocy94t4hkmjxwx

[jacksbi]

Anyone knows if this programm also works on POLISHTRACKER?
PM me please!
I need to upload some data in the first month and I am not sure if I can make it without......

EDIT// and do i have to bind it to the IP in the network options or just let it be by default?

works perfectly on PT but remember to use memory reader.

[anon]

Anyone knows if this programm also works on POLISHTRACKER?
PM me please!

Please don't ask people to PM you unless you need to know something critical that's better off not posted in public. A "yes" or "no" doesn't qualify for that.

And the answer is yes, it works on PT. Please refer to this thread for more info:
http://www.sb-innovation.de/showthre...threadid=17204

EDIT// and do i have to bind it to the IP in the network options or just let it be by default?

That's not necessary. The default is "Default", and it'll pick your main network adapter, so no worries here.

[Sb Lover]

I am just suggesting to you to add an option to stop when the ratio reach some value (like VEM)
+ how I can save settings ? (I opened ratiomaster.config and change values and make save are they easier way ? )
+ what happens if RM is on when the OS crush or when OS restart !

[anon]

Official answer has been that it won't be implemented due to the volatile nature of how RM keeps track of ratios.

[bernardosgr]

Is it optimal to use like: one instance of RM faking with some torrent and another instance of, let's say vuze running with a different torrent?

And, of course, RM with memory reader of the same client that you are using (vuze in this case)

[saebrtooth]

Is it optimal to use like: one instance of RM faking with some torrent and another instance of, let's say vuze running with a different torrent?

And, of course, RM with memory reader of the same client that you are using (vuze in this case)

to say its optimal I cant say it woud be, but it can be done

[seldom]

and it is safe. if that's was a question.

[saebrtooth]

if it can be done, it will be safe

[bernardosgr]

Lol, yeah, that was my question... Btw, yesterday i got banned from SceneXPress... was doing this exact same thing... but in 2 days i uploaded about 100 GB... Guess it was stupid...

One other thing: I noticed when i changed torrent and did the whole memory reading thing that the peer id had changed from what it was before... is this normal? I thought these settings would be updated automatically...

[seldom]

Hmm, I am using this combination (RM + client) all the time at SceneXPress with no issues, also by looking at some users profiles, I don't think 100Gb upload in 2 days is something unusual there...
Memory reader is very important and must be done every time (I know, I know, technicaly speaking it is not necessary if the client wasn't restarted, but it is a good habit. Better safe than sorry!)

[saebrtooth]

@bernard
how old was the acc?
rm remembers the old torrents details incl used client details, did you leave them as they were or did u use new memory reader details?

[anon]

And, of course, RM with memory reader of the same client that you are using (vuze in this case)

Vuze generates a new peer_id and key every time you start the torrent, so it may actually not be a good idea to use the memory reader on it. Since it (Azureus) is open-source, the RM should be able to generate "good" values by just looking at the client file.

And sure, you can run the RM side-by-side with Vuze, just make sure you use the same port and client version, of course.

One other thing: I noticed when i changed torrent and did the whole memory reading thing that the peer id had changed from what it was before... is this normal?

See above.

[bernardosgr]

The account had 2 days. But I don't quite understand your second question, saebrtooth. I did this: I was using RM with a torrent from SeX, emulation of utorrent 2.0.3, same client I had running with two other torrents from the tracker... I seeded a lot (around 30/40 GB) and then, after having completed one of the two downloads on utorrent i removed it from the list and used that same one on RM but, at this time, I didn't do the whole memory reading thing again, since it already had the previos values... I woke up getting this message : Invalid passkey

[anon]

I think it was the "seeding a lot" part that got you banned. Specially if the torrent(s) had no leechers.

[bernardosgr]

It was a torrent with around 35 GB of size and it had like 40-60 leechers... I was using speed randomization with values between 95 and 635 kbps, but I believe I only got banned with the second torrent I started faking (because I didn't do the memory thing again)