PiRSquared17 / transmission-remote-dotnet

Automatically exported from code.google.com/p/transmission-remote-dotnet
GNU General Public License v3.0
0 stars 0 forks source link

Enter one-line summary #94

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
In the older version 3.09 I could easyly insertet the share of the
Transmission client to open it.

Example: U:\BitTorrent\temp
(this is equivalent to'\\nas\bittorent\temp' on the nas)

Since version 3.10 there are two fields:

UNIX path prefix:
Samba share:

It's not posible for me, to add my already mounted share like in version 3.9.
Any suggestions what to fill in the two new fields?

TIA!

Original issue reported on code.google.com by toor2...@googlemail.com on 4 Jul 2009 at 11:20

GoogleCodeExporter commented 9 years ago
Hi there,

It should be possible still and accept mounted shares, you just need to know the
remote UNIX path of the download directory/directories. Because of the new move 
data
and alternate download directory features, more people have multiple download
directories so setting one samba share isn't good enough anymore.

Right click on a torrent and do copy info object to clipboard and paste it in
notepad. Look for the value to the right of "downloadDir" on a few and find the
common part (/home/alan/torrents for me). This is your UNIX path prefix. The 
samba
share can be U:\BitTorrent or whatever.

Hope this helps.

Original comment by AlanF...@googlemail.com on 4 Jul 2009 at 8:30

GoogleCodeExporter commented 9 years ago
Configuring a share with your instructions lead to success.

Works like a charm now. :)

Thanks and keep up the good work!

cu

tor2o12

Original comment by toor2...@googlemail.com on 4 Jul 2009 at 9:58

GoogleCodeExporter commented 9 years ago

Original comment by AlanF...@googlemail.com on 6 Jul 2009 at 7:35