works perfectly on PT but remember to use memory reader.
Printable View
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
That's not necessary. The default is "Default", and it'll pick your main network adapter, so no worries here.Quote:
EDIT// and do i have to bind it to the IP in the network options or just let it be by default?
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 !
Official answer has been that it won't be implemented due to the volatile nature of how RM keeps track of ratios.
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)
and it is safe. if that's was a question.
if it can be done, it will be safe ;)
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...
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!)
@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?
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.
See above.
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
I think it was the "seeding a lot" part that got you banned. Specially if the torrent(s) had no leechers.
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)