Transmission

See https://github.com/transmission/transmission/issues/537

Sorry if that wasn't clear, but I meant to tell you that we're using Windows API functions that are not available on Windows XP. It won't work out of the box, you'll have to make changes to the source code and build your own binaries. If you need an example, one of those new functions we use is GetF...

Windows XP and Windows 2003 support was dropped by us since those systems aren't officially supported by Microsoft anymore. This means they don't get any security updates, which is something you most probably need to worry about these days. Another reason is that newer Windows versions provide new A...

Same as on other platforms, sparse preallocation is what is used by default. And same as on other platforms, you could adjust it in settings.json by changing the value of "preallocation" key (see https://github.com/transmission/transmission/wiki/Editing-Configuration-Files#files-and-locati...

1. Locate settings.json (in e.g. C:\Users\<username>\AppData\Local\transmission\settings.json) and open it with a text editor (e.g. notepad). Check out the values of "main-window-x" and "main-window-y" keys and compare them to your screen resolution. If window coordinates are out...

Are you using the Qt client or the daemon? Is Transmission running when you reboot? Are the settings being preserved if you quit Transmission and start it again without reboot?

You're probably talking about 2.84 and 2.93. On Windows, versions before 2.9x were not provided by us, they were maintained by the guy nicknamed rb07 on SourceForge. The two versions (rb07's and ours) aren't compatible in a number of ways, one being that they have different configuration directories...

I think you're talking about Transmission Remote GUI, which is a program developed elsewhere. Try their support forums maybe (https://sourceforge.net/p/transgui/discussion/general/).

If I were you I would access environment variables from the PowerShell script directly instead of passing them as arguments to prevent issues with e.g. torrent name containing spaces or other special characters. Just use $Env:TR_TORRENT_DIR and the like.

Without -g, and if started under the same user account, both instances will use the same configuration directory.

The reason I initially wrote about being "more strict about running multiple instances" is I tried it myself and was able to start two instances without even passing -g. Not via a shortcut though, but just navigating to C:\Program Files\Transmission and double-clicking on transmission-qt.e...

What version are you using?

I'm not recommending running a particular program, you're free to choose on your own. The argument -g/--config-dir is the same for all flavors. If you're using the Qt client then yes, you could create a new shortcut and add these arguments in its properties (changing "c:\config2" to whatev...

If anything, it needs to be more strict about running multiple instances. But anyway, if you want two independent instances (be it the Qt client or the daemon), run them with passing different configuration directories as command line arguments, e.g. transmission-qt -g c:\config1 transmission-qt -g ...

Option #1, obviously, is to use a newer Windows version. Option #2 is to try programs like the one(s) mentioned in https://stackoverflow.com/q/813086/583456 (or write your own) to send the daemon the Crtl+C event instead of WM_CLOSE that taskkill on Windows 7 seems to be doing. Option #3 is, if you ...