Build Transmission on Windows

[rb07]

BTW, the dbus problem could be outside transmission-qt, i.e. something I introduced moving MS Windows registry (or, wonder of wonders, Windows needs to be rebooted . I only saw that it works once with magnets, then stops working... but, if I use dbus-send it works always, so that probably points to my own mistake.

On a different note, what happened to the open panel? Now it shows no file hierarchy, just a flat list of file names with slashes. It was better before.

[rb07]

Before someone asks: some of the icons show in the screen shots are not standard (the file, folder, and network), I'm using Gnome's icon set.

[Jordan]

Did you notice the about panel? The copyright now has no year, that's an improvement from the old hard coded values, but I'm not sure that was intended.

Yes, it was intentional. After reading up on the subject, it seems that the year isn't necessary.

On a different note, what happened to the open panel? Now it shows no file hierarchy, just a flat list of file names with slashes. It was better before.

??

It's working for me.

You ought to consider idling in #transmission on chat.freenode.net.

[rb07]

About the open panel...

It's working for me.

Here's how a torrent's file list looks:


And here is how the open torrent panel looks in this version (I haven't noticed until now that it is using back slashes, could be a Windows problem?):


The list of files used to look the same, now the second is just a flat list. Problem: there is no way to select/deselect whole directories, you have to go item by item.

[rb07]

Is it that way for all .torrents?

Its the same for all... just checked again.

[Jordan]

r11126 might fix the directory delimiter issue, but I don't have a Windows box to test it on...

[rb07]

Yes it does fix it.

I'll put a new link after I figure out how I broke magnet support (configured by the installer).

Thanks!

[rb07]

It is a bug: dbus support for magnets is broken.

I just made (force) it work by commenting out the "if( addme.type != addme.NONE )" in dbus-adaptor.cc:AddMetainfo(). Additionally this comes out on the console:

Code: Select all

unhandled AddData.type: 0

The test was something like this (obfuscated to protect the innocent):

Code: Select all

./transmission-qt "magnet:?xt=urn:btih:1234567890&dn=Sumthing&tr=http://tracker.openexample.com/announce"

[Jordan]

Gak! You're right. Fixed in r11133.

[rb07]

One more new bug: the upload/download units are wrong in revision 11116, show too much by a factor of 1024, MiB/s instead of KiB/s, etc.

[rb07]

Another bug: the delete tracker button doesn't do anything, I know its new, but is it supposed to be non-functional? or perhaps its only that way with remote sessions (which is all I use).

[Jordan]

One more new bug: the upload/download units are wrong in revision 11116, show too much by a factor of 1024, MiB/s instead of KiB/s, etc.

Another bug: the delete tracker button doesn't do anything, I know its new, but is it supposed to be non-functional? or perhaps its only that way with remote sessions (which is all I use).

Both of these sound like you're running a remote session connected to a session that's running an older version of Transmission....?

The units changed after 2.0x was branched, and the "remove tracker" RPC call was also added after 2.0x was branched. So to pick up those features, you need the server to run a nightly build too.

[d_tr]

I have been looking for a way to get transmission running as a Windows Service. I didn't want any user interface on it. I wasn't happy with the solutions I could find so I wrote one. I started with the transmission daemon and added the logic to register, unregister and manage windows service events.

When I was testing it I found a bunch of problems reading the configuration file from the service. Long story short I ended up moving the configuration to the registry, that made the service a lot happier. I also moved the log to the Windows Event Log. Although there are some benefits to the Windows Event Log it made the initial setup a bit more complicated.

Anyway, not sure how many people would like to run transmission as a Windows Service. If you do you can grab the build from here: http://ifile.it/nx6jsq8/Transmission.7z.

This is a statically linked 2.0.1 build with no external dependencies. I bundled the web interface just in case someone wants to play with that. I use Transdroid from my android phone and transmisson-remote-gui from my PC. Both work just fine to control the transmission service.

What I didn't do was to create an installer package. If anyone is familiar with doing that I would appreciate the help. In the meantime these are the setup steps:

1. unzip the package anywhere you want the executable to be (using 7-zip http://www.7-zip.org/download.html)
2. launch an elevated command prompt window. You will need admin rights to register the service and configure it
3. CD into the folder you unziped the binaries and register the service with transmission-service -s. This will add the service to the service list and set it to start automatically next time you reboot but won't start it
4. Need to configure the events the service will log in the Event Log. Edit the win-log.xml file using your favorite text editor (notepad will do) and replace both instances of <%install_dir%> with the complete path to the folder you unzipped the package in. Assuming you used C:\Program Files\Transmission you will end up with these two lines:

Code: Select all

          resourceFileName="C:\Program Files\Transmission\WinLog.dll"
          messageFileName="C:\Program Files\Transmission\WinLog.dll"

5. To actually register the events run wevtutil im win-log.xml
6. If you want to change any of the transmission service configuration you can do that via the command line. Type tranmission-service /? for a list of all options. Note that changing the transmission configuration won't start the service, if any arguments are passed via command line they will simply be written to the registry. Changing parameters won't affect a running service either, you will have to restart the service for the new configuration to take effect.
7. Now you can start the service. Enjoy.

[jdarias]

Hi all devs.
I´m trying the 2.03 version of Qtransmission to connect to a 1.91 daemon running on my nas. It is wonderful!
However every time i start Qtransmission, it starts without remembering the window configuration (size, position) and the info for the remote session, so it has to be entered every time i run it.

[rb07]

However every time i start Qtransmission, it starts without remembering the window configuration (size, position) and the info for the remote session, so it has to be entered every time i run it.

Must be having a problem writing to your home directory.

Run the application from a console window (Run -> cmd; then change to the installation directory \Programs or \Program Files; and just execute qtr.exe), it will print some messages to the console, the interesting ones are when you close the application and it tries to save settings.json (which is where all the information you mention is stored).

My guess: Your user and therefore your home directory has accents or any other non-English character. Currently QTransmission can't handle that. Workaround: try something like this (my data between brackets are just examples, you fill your own values without brackets):

Code: Select all

qtr --remote <192.168.1.8> --username <trans> --password <mission> --config-dir </Program Files/QTransmission/config>