When I boot my computer and QAP attempts to load, I get an error message that the QAP folder is read only and QAP cannot write to the ini file. The folder is not read-only. QAP then terminates and I have to load it via the exe file. Why am I getting this odd message?
Thanks.
QAP 9.5.2
I used the zip file to install it on my desktop
Windows explorer, Windows 10
Hi Wsc3,
This normally happens when the QAP executable is started from a zip file, a read-only folder or a "protected" folder (such as "C:\" root or any location under "C:\Program Files"). Normally, QAP should run from the Desktop (if the file is unzipped). If it does not, try from a folder under "My Documents".
Jean
Hi Jean,
Thanks for the response. QAP is not started from a Zip file. I unzipped all of the files into a folder call C:\QAP and removed the Zip file. It is executed as all of my programs are without such a puzzling error message. I'm sorry I misstated this.
Hi Wsc3,
This is the first time this issue is reported for a "regular" folder. I could not tell why this is happening. Just for a test, would you try unzipping and running it from "My Documents\QAP" ?
Jean
(2019-08-01 10:30)jlalonde Wrote: [ -> ]Hi Wsc3,
This is the first time this issue is reported for a "regular" folder. I could not tell why this is happening. Just for a test, would you try unzipping and running it from "My Documents\QAP" ?
Jean
It only happens at boot up. I never get the error again, which is weird. It runs fine after that.
Since QAP didn’t install itself to load at boot, I added it to my start up program list via WinPatrol. Could that be the problem? How is QAP suppose to load at boot?
If you install QAP in portable mode (with the ZIP file), there is an option (first tab of Options window) to enable the "Run at Startup" option. Or you could enable it by right-clicking the QAP icon in the Notification zone and enable "Run at Startup". This creates a file shortcut in your Windows Startup folder.
I removed it from Winpatrol and found the start-up option as you pointed out. The error has (so far) stopped. Thanks!!!
Great! Have fun with QAP :-)