BitShares Forum
Other => Graveyard => Keyhotee => Topic started by: sudo on April 03, 2014, 08:59:33 am
-
Now the default （xp）is C:\Documents and Settings\Administrator\Local Settings\Application Data\KEYHOTEE
my KEYHOTEE path G:\Keyhotee\Keyhotee.exe
BitShares-PTS can custom by add some command in shortcut “G:\BitShares-PTS\BitShares-PTS.exe -datadir=G:\PTS\ProtoShares”
or run.bat
“@echo off
start Keyhotee.exe -datadir=.\profiles”
if Keyhotee has some similar ways？
-
No, it's not changeable at this time.
-
I recommend to change the default profilepath for the Keyhotee Windows version to a more dynamic location.
E.g. %appdata% or {CSIDL_APPDATA}
Using local userprofil path as now is not a very suitable solution for roaming profiles or terminal server environments.
In addition it would be great to control Keyhotee application settings via registry HKCU, e.g. profilepath etc.
This will become important as soon as Keyhotee hits the business segment and should be implemented early.
Keyhotee currently uses %appdata% on windows. The above explanations are just the typical "resolved" value for %appdata% on various user's machines.
-
Well, the first post indicates that keyhotee is using %localappdata%.
And on my computer with windows 8.1 it is also not using %appdata% as my keyhotee profile is located at C:\Users\username\AppData\Local\keyhotee.
On my computer "%appdata%" is resolved as C:\Users\username\AppData\Roaming .
http://www.microsoft.com/security/portal/mmpc/shared/variables.aspx (http://www.microsoft.com/security/portal/mmpc/shared/variables.aspx)
Ah, then the first post is correct and it uses %localappdata%. I had misinterpreted your previous post to mean that it was hardcoded to a folder.