[chirp_users] Where do I find chirpw.exe.log ??
Dan,
When I attempt to start Chirp, I get the following error.
Error Msg: The logfile 'C:\Program Files (x86)\CHIRP\chirpw.exe.log' could not be opened: (Errno 13) Permission denied: 'C:\Program Files (x86)\CHIRP\chirpw.exe.log'
I uninstalled Chirp and then reinstalled using chirp-daily-01212012-installer.exe and I still get this error. There is not chirpw.exe.log file, however, I do find the chirpw.exe file.
Thanks & 73 de KK4DBR Ron
22.01.2012, 15:28, "Ron McKenzie" rmckenzie5@cfl.rr.com:
When I attempt to start Chirp, I get the following error.
Error Msg: The logfile 'C:\Program Files (x86)\CHIRP\chirpw.exe.log' could not be opened: (Errno 13) Permission denied: 'C:\Program Files (x86)\CHIRP\chirpw.exe.log'
I uninstalled Chirp and then reinstalled using chirp-daily-01212012-installer.exe and I still get this error. There is not chirpw.exe.log file, however, I do find the chirpw.exe file.
I had reported about this problem at 22 September 2011 ( http://intrepid.danplanet.com/pipermail/chirp_users/2011-September/001406.ht... ) and Dan has opened the issue - http://chirp.danplanet.com/issues/12 . But it has been closed later.
If you are using Windows Vista or Windows Seven, you always should run the program as administrator - right click on the Chirp's shortcut and select "Run as administrator". Or you can change the directory permissions on 'C:\Program Files (x86)\CHIRP' or reinstall the program to another (non Program Files) directory.
I had reported about this problem at 22 September 2011 ( http://intrepid.danplanet.com/pipermail/chirp_users/2011-September/001406.ht... ) and Dan has opened the issue - http://chirp.danplanet.com/issues/12 . But it has been closed later.
No, you reported debug.log, which is no longer stored in Program Files as of some daily version months ago.
He's asking about chirpw.exe.log, which is something that the Py2Exe environment creates by itself and I have no control over, as far as I know. I don't believe it gets created unless there's an error that needs to be logged there.
If you are using Windows Vista or Windows Seven, you always should run the program as administrator - right click on the Chirp's shortcut and select "Run as administrator". Or you can change the directory permissions on 'C:\Program Files (x86)\CHIRP' or reinstall the program to another (non Program Files) directory.
Ron, if you could try this and then see if a chirpw.exe.log file gets created, that would be helpful. The contents of this log may help me determine what's causing it to be created in the first place.
See below.
On 1/22/2012 10:33 AM, Dan Smith wrote:
He's asking about chirpw.exe.log, which is something that the Py2Exe environment creates by itself and I have no control over, as far as I know. I don't believe it gets created unless there's an error that needs to be logged there.
If you are using Windows Vista or Windows Seven, you always should run the program as administrator - right click on the Chirp's shortcut and select "Run as administrator". Or you can change the directory permissions on 'C:\Program Files (x86)\CHIRP' or reinstall the program to another (non Program Files) directory.
Ron, if you could try this and then see if a chirpw.exe.log file gets created, that would be helpful. The contents of this log may help me determine what's causing it to be created in the first place.
Dan, I was able to start Chirp by using the right-click menu's Run as Admin. I also tried uninstalling Chirp from \Programs (x86)\ and installing it to C:\Chirp. After doing this and fixing the paths in my desktop Chirp icon, Chirp starts without displaying the error msg.
Thanks,
Ron
23.01.2012, 02:33, "Dan Smith" dsmith@danplanet.com:
I had reported about this problem at 22 September 2011 ( http://intrepid.danplanet.com/pipermail/chirp_users/2011-September/001406.ht... ) and Dan has opened the issue - http://chirp.danplanet.com/issues/12 . But it has been closed later.
No, you reported debug.log, which is no longer stored in Program Files as of some daily version months ago.
He's asking about chirpw.exe.log, which is something that the Py2Exe environment creates by itself and I have no control over, as far as I know. I don't believe it gets created unless there's an error that needs to be logged there.
It's a similar problem. Windows Vista/Seven forbids to wirite any user data to the Program Files subfolders on default. But chirpw.exe.log is a user data. It's would be cool you will move the chirpw.exe.log file to the %LOCALAPPDATA% or %TEMP% directory.
It's a similar problem. Windows Vista/Seven forbids to wirite any user data to the Program Files subfolders on default. But chirpw.exe.log is a user data.
Yes, I understand.
It's would be cool you will move the chirpw.exe.log file to the %LOCALAPPDATA% or %TEMP% directory.
As I said, I'm not sure why that file is being created (as I think it's only done when there is an error before I arrest standard output to the debug.log file) and it's not something I can control.
Ron, did a chirpw.exe.log file get created in Program Files after you ran it as Administrator?
23.01.2012, 11:58, "Dan Smith" dsmith@danplanet.com:
It's would be cool you will move the chirpw.exe.log file to the %LOCALAPPDATA% or %TEMP% directory.
As I said, I'm not sure why that file is being created (as I think it's only done when there is an error before I arrest standard output to the debug.log file) and it's not something I can control.
I'm sorry. I had not understood at the first time. )
Ron, did a chirpw.exe.log file get created in Program Files after you ran it as Administrator?
I am not Ron, but I can say. A chirpw.exe.log file didn't get created, but a debug.log file got created.
If I've set RO flag on the debug.log file, a I am getting an "See the logfile 'C:\Program Files\chirpw.exe.log' for details" error during CHIRP running.
=== chirpw.exe.log === Traceback (most recent call last): File "chirpw", line 31, in <module> IOError: [Errno 13] Permission denied: 'debug.log' ===
I am not Ron,
Yes, I know, I was speaking to Ron McKenzie, the other gentleman in the thread who is experiencing the problem.
but I can say. A chirpw.exe.log file didn't get created, but a debug.log file got created.
Right, you're causing an error to occur before (during) the debug log can be opened.
Maybe Ron is not running the latest daily version and 0.1.12 was before I fixed the location issue and thus is hitting the chirpw.exe.log message *because* of the failure to open debug.log?
below
On 1/22/2012 8:26 PM, Dan Smith wrote:
I am not Ron,
Yes, I know, I was speaking to Ron McKenzie, the other gentleman in the thread who is experiencing the problem.
but I can say. A chirpw.exe.log file didn't get created, but a debug.log file got created.
Right, you're causing an error to occur before (during) the debug log can be opened.
Maybe Ron is not running the latest daily version and 0.1.12 was before I fixed the location issue and thus is hitting the chirpw.exe.log message *because* of the failure to open debug.log?
I'm running whatever was installed by chirp-daily-01212012-installer.exe. Do I need to first install an older version before applying the daily file?
Thanks/73,
Ron
Below.
On 1/22/2012 7:58 PM, Dan Smith wrote:
It's a similar problem. Windows Vista/Seven forbids to wirite any user data to the Program Files subfolders on default. But chirpw.exe.log is a user data.
Yes, I understand.
It's would be cool you will move the chirpw.exe.log file to the %LOCALAPPDATA% or %TEMP% directory.
As I said, I'm not sure why that file is being created (as I think it's only done when there is an error before I arrest standard output to the debug.log file) and it's not something I can control.
Ron, did a chirpw.exe.log file get created in Program Files after you ran it as Administrator?
No, Dan, I do not find a chirpw.exe.log file anywhere in CHIRP or its subdirectories. There is a debug file but that's it.
No, Dan, I do not find a chirpw.exe.log file anywhere in CHIRP or its subdirectories. There is a debug file but that's it.
Hmm, okay, I'm not sure how to resolve the behavior you're seeing then. I do have a Windows 7 VM somewhere, so I should be able to try it at some point, but I don't recall having any such trouble on it in the past.
23.01.2012, 12:48, "Dan Smith" dsmith@danplanet.com:
Hmm, okay, I'm not sure how to resolve the behavior you're seeing then. I do have a Windows 7 VM somewhere, so I should be able to try it at some point, but I don't recall having any such trouble on it in the past.
Do you have enabled UAC option in the your VM?
23.01.2012, 11:38, "Dan Smith" dsmith@danplanet.com:
I had reported about this problem at 22 September 2011 ( http://intrepid.danplanet.com/pipermail/chirp_users/2011-September/001406.ht... ) and Dan has opened the issue - http://chirp.danplanet.com/issues/12 . But it has been closed later.
No, you reported debug.log, which is no longer stored in Program Files as of some daily version months ago.
And so? Does debug.log store in Program Files or not?
Do you have enabled UAC option in the your VM?
Dunno, I'm not a Windows user, but I'll be sure to check that.
And so? Does debug.log store in Program Files or not?
It should, yes, according to the code. Do you think the daily version still puts it in Program Files?
23.01.2012, 13:44, "Dan Smith" dsmith@danplanet.com:
And so? Does debug.log store in Program Files or not?
It should, yes, according to the code. Do you think the daily version still puts it in Program Files?
Daily version (01212012) puts it (debug.log) in program directory (ex. C:/Program Files/CHIRP/). But Windows forbids that, all user (runtime) data MUST be stored in non Program Files (and subdirs) directory.
Daily version (01212012) puts it (debug.log) in program directory (ex. C:/Program Files/CHIRP/). But Windows forbids that, all user (runtime) data MUST be stored in non Program Files (and subdirs) directory.
Yes, and that was my intent, of course (and why I closed the bug, because I thought it was fixed. However, I see now that it was choosing the wrong path only on windows and only when packed as a .exe (which isn't how I run it for development, of course).
A fix is in the queue for tomorrow, please report back that the problem is resolved.
23.01.2012, 18:07, "Dan Smith" dsmith@danplanet.com:
Daily version (01212012) puts it (debug.log) in program directory (ex. C:/Program Files/CHIRP/). But Windows forbids that, all user (runtime) data MUST be stored in non Program Files (and subdirs) directory.
A fix is in the queue for tomorrow, please report back that the problem is resolved.
The 01232012 is working great. debug.log is storing in "%APPDATA%/CHIRP" directory now. Thx.
Puzzles me, too, since I have administrator rights assigned to myself.
I have a workaround for the moment, actually, I have 2. Either I "run as admin" or I install to a non-program files directory so the permissions problem is no longer a problem.
Thanks,
Ron
On 1/22/2012 8:48 PM, Dan Smith wrote:
No, Dan, I do not find a chirpw.exe.log file anywhere in CHIRP or its subdirectories. There is a debug file but that's it.
Hmm, okay, I'm not sure how to resolve the behavior you're seeing then. I do have a Windows 7 VM somewhere, so I should be able to try it at some point, but I don't recall having any such trouble on it in the past.
participants (3)
-
Boris Korzun -
Dan Smith -
Ron McKenzie