[chirp_devel] Add new Wiki file, consolidate others
Hi Dan / all,
I'd like to add a new file to the Wiki library, and later also to edit / consolidate some others. I can already edit; do I need extra privileges to add new files or to remove others?
This simple short one, "Running Chirp under Windows" would be added:
h1. Running CHIRP Under Windows
{{>toc}}
Running Chirp under Windows is pretty straight-forward, but it has some traps to offer. You can run into a few situations in which a little doing is needed before Chirp starts correctly.
h2. Corrupt Chirp configuration file
If Chirp just does nothing when you try to start it, then its configuration file might have been damaged: Windows 10 has a bad habit of corrupting it. Solution: Delete the chirp.config file. The next time CHIRP is loaded, a new chirp.config file will be created. The chirp.config file is kept in the same folder as the debug.log file (it might be in C:\Users<user>\AppData\Roaming\CHIRP\chirp.config).
h2. Non-standard character in program path
CHIRP won't load when the Windows user account has a special character (accented characters, umlauts, characters which aren't in the latin alphabet) in it. Solution: Put Chirp somewhere into a path which doesn't contain special characters.
h2. You get an "Error opening file for writing: c:\program files (x86)\chirp_ctypes.pyd"
Solution: Run Chirp with Administrator privileges.
Thanks and 73, Bernhard AE6YN
I'd like to add a new file to the Wiki library, and later also to edit / consolidate some others. I can already edit; do I need extra privileges to add new files or to remove others?
I don't think so, you should be able to create a new page.
h2. You get an "Error opening file for writing: c:\program files (x86)\chirp_ctypes.pyd"
Solution: Run Chirp with Administrator privileges.
I assume you mean the installer. CHIRP itself shouldn't need to be run as admin, and doing so would be a bad idea.
--Dan
h2. You get an "Error opening file for writing: c:\program files (x86)\chirp_ctypes.pyd"
Solution: Run Chirp with Administrator privileges.
A more likely cause of this error is due to the user trying to perform and upgrade while CHIRP is already running. Windows can't replace/upgrade any files that are currently in use.
This is likely due to CHIRP prompting the user that there is an upgrade available and the user clicked [OK] or pressed [Enter] to continue which causes the CHIRP "Download" page to load in the user's browser. They then download the latest daily build and, forgetting that CHIRP is already running, runs the newly downloaded CHIRP "installer" to upgrade CHIRP and is presented with the error message above regardless of whether they are performing the upgrade with Administrator privileges or not. So the "solution" should be worded something like this.
Solution: Close all running instances of CHIRP then right-click the CHIRP installer and choose "Run as administrator" to initiate the upgrade.
Jim KC9HI
Thanks for the feedback Dan and Jim. I will change accordingly before publishing.
73, Bernhard
On 10-Sep-20 07:54, Jim Unroe wrote:
h2. You get an "Error opening file for writing: c:\program files (x86)\chirp_ctypes.pyd"
Solution: Run Chirp with Administrator privileges.
A more likely cause of this error is due to the user trying to perform and upgrade while CHIRP is already running. Windows can't replace/upgrade any files that are currently in use.
This is likely due to CHIRP prompting the user that there is an upgrade available and the user clicked [OK] or pressed [Enter] to continue which causes the CHIRP "Download" page to load in the user's browser. They then download the latest daily build and, forgetting that CHIRP is already running, runs the newly downloaded CHIRP "installer" to upgrade CHIRP and is presented with the error message above regardless of whether they are performing the upgrade with Administrator privileges or not. So the "solution" should be worded something like this.
Solution: Close all running instances of CHIRP then right-click the CHIRP installer and choose "Run as administrator" to initiate the upgrade.
Jim KC9HI
participants (3)
-
Bernhard Hailer
-
Dan Smith
-
Jim Unroe