-
-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom home path doesnt seems to work #386
Comments
There are settings to change where syncthing.exe and the syncthing config and database are stored. Look in the settings window.
…On 23 July 2017 14:57:16 BST, beerisgood ***@***.***> wrote:
I have my Syncthing unpacked in "E:\X\syncthing-windows-amd64" and use
it for many months now, but now i try the switch to this more automatic
tool. Thanks for it!
For me this setting means, the syncthing.exe is used from that folder
too, but SyncTrayzor always use
"C:\Users\USER\AppData\Roaming\SyncTrayzor\syncthing.exe"
Why? In my config and sure a lot of more users restrict access to
AppData and then SyncTrayzor doesnt work.
I get then that error:

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#386
|
Also the "Migrating between "raw" Syncthing, Portable, and Installed SyncTrayzor" section in the README, which was written to address your question.
…On 23 July 2017 14:57:16 BST, beerisgood ***@***.***> wrote:
I have my Syncthing unpacked in "E:\X\syncthing-windows-amd64" and use
it for many months now, but now i try the switch to this more automatic
tool. Thanks for it!
For me this setting means, the syncthing.exe is used from that folder
too, but SyncTrayzor always use
"C:\Users\USER\AppData\Roaming\SyncTrayzor\syncthing.exe"
Why? In my config and sure a lot of more users restrict access to
AppData and then SyncTrayzor doesnt work.
I get then that error:

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#386
|
Yes i found that setting with home path for Syncthing in the settings (Settings -> Syncthing -> Advanced -> Syncthing Custom Home Path) but sadly SycnTrayzor still try to start "C:\Users<You>\AppData\Roaming\SyncTrayzor\syncthing.exe" which i dont want. |
Ah yeah, that particular setting isn't in the user-editable settings. You can use the portable version of SyncTrayzor. Put it in |
But i want use the windows autostart feature and auto update Or another way is if that would be a user-editable settings in menu for installer version |
Both of those are available in the portable edition.
beerisgood wrote:
…
But i want use the windows autostart feature and auto update
Or can i do that with the portable as well?
Or another way is if that would be a user-editable settings in menu
for installer version
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#386 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAirKJOco_hxBrACNNEi1o8aJb4saLmvks5sQ46BgaJpZM4Ogdag>.
|
Alright, then i will switch to the portable version. |
Contributions welcome! |
Looks fixed cause it works as you told me in this issue: #464 |
Yes, I fixed it on the 28th Feb, as it says above. |
I have my Syncthing unpacked in "E:\X\syncthing-windows-amd64" and use it for many months now, but now i try the switch to this more automatic tool. Thanks for it!
For me this setting means, the syncthing.exe is used from that folder too, but SyncTrayzor always use "C:\Users\USER\AppData\Roaming\SyncTrayzor\syncthing.exe"
Why? In my config and sure a lot of more users restrict access to AppData and then SyncTrayzor doesnt work.
I get then that error:

The text was updated successfully, but these errors were encountered: