Thread: Utorrent Multiple Setup

1. Create a new folder

2. Copy utorrent.exe into that folder

3. Copy the .dat files from \appdata\uTorrent into this new folder

4. Create a shortcut for this utorrent.exe in this folder

5. Edit the shortcut's target by adding /RECOVER to the end of the Target, outside of any quotation marks, and separated with a space.



6. Open this shortcut. Your settings should be retained, just edit the IP and/or port you want to use.

I don't quite understand the purpose for this

Do all that thinks for what?

Originally Posted by ShiekAbdul

I don't quite understand the purpose for this

I assume this is a tutorial to run multiple instances of utorrent on the same box.

How To Run Multiple Instances of uTorrent (v1.7.7 & v1.8) | THE source for BitTorrent & P2P Tips, Tricks and Info. | FileShareFreak

I understand this is about running multiple utorrents on one box, but is there any advantage to this? What would 2 clients do that the one client wouldn't do??

very interested to hear an outcome to this :)

You could use the separate clients for separate trackers, and limit speeds depending on the tracker.

yes better control of each tracker, or maybe if you have a second internet connection

Would it be better to have one torrent instance running private trackers while the other does public trackers? I think though that I would get confused as to which torrent client did what when adding torrents. May be better to use a different client entirely

Windows firewall wouldn't be able to tell the difference between the two instances and more importantly wouldn't incoming connections possibly get sent to the wrong instance and discarded? Perhaps if you are certain to set incoming traffic port as well as outgoing traffic port then that wouldn't happen.

@npowerd, I think the second internet connection would have to be set at the router. When I have played around with second internet connections on client os machines, it tends to be an all or nothing deal. I mean, you can add a second internet connection, but as long as the second connection can handle all of the traffic generated by the windows box, windows sends all traffic down the second interface and leaves the first interface completely dead until the second interface goes offline or there isn't a routeable path from the second interface that exists on the first interface. No OS software load balancing is done by non server editions but I think it is allowed as early as server 2003 editions better than small business.

If you or anyone has seen differently, please let me know that I may learn :P

Well i guess i will stick with one version at any point of time, that has worked fine for me so far. This info is still useful and if i get to this point, i will use the info above to good use