On Linux (Wine), VarAC cannot find its config files

VarAC doesn't seem to be able to locate its own home directory while run from Wine (it ends up putting its config files in the user's home directory): VarAC's .conf & .ini files are housed in the VarAC directory (in the ~/.wine/ folder), but the .ini files there don't get used. VarAC also then creates brand new .conf & .ini files inside of ~/. (aka /home/user/.) that VarAC is actually reading/writing to. VarAC still functions well, but it makes the initial installation of VarAC not very intuitive for users (users have to know default ports for applications) and it also causes error messages to pop up until the config files are all in the user's home directory. I've tried making workarounds for this using AutoHotKey and sed in an installer script, but I can't seem to work around the config file problem easily/elegantly at the moment. VarAC accidentally putting its config files in the /home/user/ directory (instead of its own ~/.wine/drive_c/VarAC program folder) is kind of messy for users and could lead to some users accidentally deleting their settings files without realizing. This bug could also be related to a minor bug where VarAC seems to only run if invoked from outside its own program directory (for example, in the terminal, if I go to the program directory and try to run VarAC then it doesn't open, but if I go up one directory and run it then it opens).

2 comments

2 Comments

irad d

Feb 26, 2023

As I do not know WINE very well - what do you suggest as a solution that I can apply on my end ?

By default, if not implied differently, all files in windows are searched/created in the place where VarAC was executed.

Here are some question:

I use c# function to get the VarAC executable dir (AppDomain.CurrentDomain.BaseDirectory) and concatenate it to the begining of files before accessing them.

I did find in my code that some files were not addressed with this when created/read. But some do. For example - the VarAC.db is and the VarAC_frequencies.conf isn't.

Do you see on your end that ?

Irad

Ken Baker

Mar 19

Replying to

I have the exact same issue with Linux Mint and wine. the VarAC.ini file and the VarAC_cat_commands.ini file have to be on my linux home directory (which it thinks is z: ) or the VarAC program can't find it; otherwise the program works fine. I can add the path to a VarAC.ini file at the end of the CLI statement to run VarAC, but this is cumbersome, but works:

env WINEDEBUG=-all wine ~/.wine/drive_c/VarAC/VarAC.exe ~/.wine/drive_c/VarAC/VarAC.ini

It would seem to not be an issue with wine since I have had other programs (like RMS Express, VARA or VARAFM) installed using wine place their ini files in ~/.wine/drive_c/ sub directories. all using the same WINEPREFIX.

Thanks.

Edited