6 Jan
2014
6 Jan
'14
8:44 a.m.
I seem to remember someone else having an issue similar to this and had to delete their "chirp.config" file. Here is how you do it.
- Go to Start->Run and type "%APPDATA%\CHIRP".
- Click on the CHIRP folder that is listed.
- Delete or rename the "chirp.config" file.
Now launch CHIRP and see if the problem is solved.
If that's the case, we should save the chirp.config and fix the problem, not just have them delete the evidence!
--Dan