Regarding the memory reader, on whatever tools used... Is it safe to use different values on different torrents? I know those values change overtime anyways (like stopping and starting torrents).....
WHat Im thinking is using two different computers to seed... DIfferent torrents offcourse but have same trackers... So I'll end up using different values on the Memory reader at the same time... Is this safe?
Why don't you read my answer on the exact same question you previously stated here?
The memory reader thing isn't working for me. I go on the advanced tab and choose: uTorrent 2.0.4 Build (21515) for client stimulation since i have the client uTorrent 2.0.4 and i click on memory reader. I start search but i get a message when the bar gets full thats loading saying 'Search failed, Make sure that torrent client is running and that at least one torrent is working' I don't understand since the my utorrent client is open and is seeding around 300 torrents, so i don't understand what that message on ratiomaster is talking about. This is the stong i get btw, '&peer_id=-UT2040-%0bT' Is that the right string?
Any help?
Probable causes for the memory reader not working:
1. you're not using the same exact build you attempt to emulate OR you're using the wrong client file
2.you don't have any torrents running
3. you aren't running RM as administrator
"I just remembered something that happened a long time ago."
I have one problem with memory reading... i do everything what you say but my speed isnt random its always same... how do i know that?? i write that my dw is bigger than up speed (min dw > max up) and whole time i have more UP than DW... and i saw that in general my up speed is 900kbps and dw is 10... i checked random speed so that isnt problem... pls help i need the answer fast xD
Hi good forum you guys have here...
I have a problem with the memory reader. Most of the time the 'search' for utorrent fails. If i pause and unpause some torrents in utorrent and immediately click seach then it usually works. Does anyone know why this could be happening?
Cheers,
uTorrent's memory wasn't meant to be read. So you have to do that sort of stuff sometimes.
"I just remembered something that happened a long time ago."
Oh ok cool. Thanks for that guys, just wanted to make sure there was nothing wrong on my end.
Tsk tsk... rule two... rule two!
"I just remembered something that happened a long time ago."
Any plans on updating the emulation list? For example to cover uTorrent 2.2.1 +
Bookmarks