damn ....cause thats exactly what i did since the start ........yet get the above mentioned issue when using said java.vmoptions with added lines
Printable View
damn ....cause thats exactly what i did since the start ........yet get the above mentioned issue when using said java.vmoptions with added lines
Trying to figure out a strange behavior when using Ratio Tool + after restarting the client :
- When "Add stopped" is checked >> torrent is stopped after restarting, also all other torrents that are using Speed mode++ are seeding normally.
- When "Add stopped" is not checked >> torrent is Forced Seeding after restarting, also all other torrents that are using Speed mode++ are seeding normally.
I don't recall that this was the case when I was using Ratio Tool some time ago, tried to play with many options related to queueing and seeding but with no success.
I need all the torrent to be normally seeding after restart.
Any thought ?
"Add stopped" should have no effect on a torrent that has already been added...
Does that include these?
- Options
- Startup & Shutdown
- Auto-pause/resume
- Pause downloads on exit
- Resume paused downloads on start after initialization completes
- Files
- Torrents
- By default add new torrents in a stopped state
- When a torrent is added in a stopped state automatically pause it
Yes, I already tried those and I re-tried them again after you mentioned them but they don't have any effect on "forced seeding" state.
I will try the new 3.0.0.0 update, but I don't expect any difference as this part of configurations most probably hasn't been touched in the new implementation.
Interesting. As I recall, the part of the code that loads ratio tool torrents is a bit hacky, which is why the "add stopped" setting exists in the first place instead of following regular start and queue rules. The rest is solid though.
There is no "jre" folder in "biglybt" just ".install4j". How do I proceed?