locked Re: [Ham-Apps] Logging problems
Laurie, VK3AMA <groups03@...>
Hi John,toggle quoted messageShow quoted text
I will answer you questions in reverse order.
The "Sound OFF" setting being remembered between JT-Alert restarts is implemented in 1.5.1 (due for release today)
The missing B4 log path is by design. When JT-Alert first starts and reads your configuration file, any file specified in the configuration is tested to see if the file exists. If the file no longer exists, the setting is cleared and the configuration will show an empty field. If your field is being cleared, but on further investigation you find that the file does exists, then that suggests that something on your PC is preventing JT-Alert from reading your file system accurately (Virus software maybe) and that will require further investigation.
Your ADIF issue. I assume you are opening the JT65-HF adi log file and editing that in ADIF master. Is that correct?
JT-Alert 1.4.1 never looked at the JT65-HF log file, but 1.5.0 does, but it attempts to open the file once and in read-only mode only (after a Log QSO command) to determine the QSO data. This fileopen action, if it fails (due to permissions or locking) is never repeated and just returns no data to JT-Alert. JT-Alert doesn't open the file in write mode or apply any locks to the file and doesn't alter the adi file in any way. So if ADIF Master is reporting that the file is not of the correct format, then that suggests that a program other than JT-Alert has modified the file, that leaves either ADIF master or JT65-HF.
Having said all that, there seems to be some sort of PC file-system issue at play here. What virus software are you running? Have you tried disabling that. There have been no other reports of this issue, yours is the first, again leading me to think that it is specific to your PC environment.
As an alternative, have you tried logging to a JT-Alert created ADIF file (visit the logging section of JT-Alert configuration) and opening that file in ADIF Master and avoid opening the JT65-HF adi log.
On 22-October-2011 02:58, g4gcl wrote: