Careful, I CAN hear you!
- Dec 18, 2002
- Indianapolis, IN
It complains about the com port, and on first basic fix of reset the baud rate, it says the port is in use by this instance but nothing is being fed to the laptop. SO then I do the switch to another port. After the third time this happened I decided its time to see if Bob or anyone has an fix. If i was doing a feed this would really be a pain. As it is, its just every time the laptop reboots from an update etc...It almost sounds like it is not writing your changes to the ProScan.cfg file which should be located in the same folder you are running that instance of ProScan from.
Possibly a permissions problem or it's writing your changes to a proscan.cfg located elsewhere.
I'd think ProScan would complain about something though when you start it or make a change that is written to the cfg file if it's missing or blocked due to a permissions setting.
I've not seen this error on Win 7 or the latest Win 10 release version.