VarAC.ini file cannot be edited => cannot change VarAC configuration from the dialogs in VarAC program.
The cause is that VarAC.ini file is placed in the same directory as the program file, therefore it is protected by the system against write access.
I think professionals have solved this dozens years ago when they wisely decided to put data files in different directories that the program files. In the current versions of Windows this is something like C:\Users\<userid>\AppData\Local\<program name>.
I can't understand why VarAC had to choose its own way to do it wrong, and would like to ask to fix this design flaw. It is really annoying.
This isn’t a design flaw; it’s intentional.
Most hams aren't particularly PC-tech-savvy, so simplicity is key when it comes to ham software. That simplicity means making sure the software installs and runs within a self-contained directory. Many users prefer the straightforward ZIP file option for deploying VarAC in its lightweight (non-installer) mode.
After three years of supporting hams through various technical issues, I’ve seen that this approach works best. If you’re not a tech expert, simply run VarAC as an administrator. For those who are more comfortable with tech, you can set permissions manually.
This setup applies to the VARA modem as well, which is a prerequisite for VarAC. It, too, is designed to operate from the same directory. "Fixing" the setup for VarAC wouldn’t change things for VARA.
Ultimately, this decision prioritizes ease of use for the average ham rather than meeting higher technical standards (which I also appreciate).
Hope that clarifies.
73s,
Irad 4Z1AC