If you found a bug post here your report.
Do command line arguments still work?
kerosama Posts: 1
13/10/2024
|
I'm trying to change my config, programs, temp, and log directories, but nothing seems to change. So far I've tried (from the Symenu directory) entering commands like symenu.exe -ft"T:\SyMenu\" with several variations including but not limited to removing the end slash and having the application running or not. I even tried making a shortcut with all 4 commands total in the "Target" field. The command line section of the manual doesn't seem to go into any more detail, and it brings me to wonder if it's even up-to-date.
|
|
link
|
Gianluca Administrator Posts: 1274
13/10/2024
|
Hi kerosama.
The command args still work. Every redefined path must end with no slash so, for example SyMenu.exe -fc"D:\misc\temp\config\" won't work while SyMenu.exe -fc"D:\misc\temp\config" will.
I discourage you from defining an alternative folder the way you are trying to do. My advice is to define a separate folder for every redefined path.
So instead of defining
symenu.exe -ft"T:\SyMenu\" please define symenu.exe -ft"T:\SyMenu\temp" with no final backslash and with an exclusive path.
When you test the alternative path, you should create the root folder (T:\SyMenu) but not the pointed folder (temp) so you will have a clear counterproof that SyMenu is really redefining that folder, because if SyMenu doesn't find its folders, it creates them. In the same way, rename the normal folder it uses (not the temp one, please, because it's a system folder, but the log one or the config one). This way you can check for real if SyMenu is still pointing in the default location or in a redefined one.
Don't expect that SyMenu can create the entire full path. So in the previous example the folder T:\SyMenu must exist.
There's no need to change the target in a shortcut to get the redefinition.
Are you sure SyMenu has the right to access the alternative path? Because this could be the real problem.
|
|
link
|