locked [Ham-Apps] Re: Falure: QSO Not Logged!


Laurie, VK3AMA <groups03@...>
 

The Backslash fix is no longer needed under 1.5.1 but having it wont affect logging.

More info needed.

What log type are you using?
Does it happen for every Log attempt?
Does the QSO actually get logged but the "Not Logged" message is incorrect?

To debug, please send me you config.ini and session.txt files. For the session file, close JT-Alert after a failed log attempt before sending otherwise it wont contain the debugging information I need.

File locations...
For Win7
C:&#92;Users&#92;<UserName>&#92;AppData&#92;Local&#92;Ham-Apps&#92;JT-Alert&#92;<Callsign>&#92;configs&#92;config.ini

C:&#92;Users&#92;<UserName>&#92;AppData&#92;Local&#92;Ham-Apps&#92;JT-Alert&#92;<Callsign>&#92;sessions&#92;session.txt

For XP
C:&#92;Documents and Settings&#92;<UserName>&#92;Local Settings&#92;Application Data&#92;Ham-Apps&#92;JT-Alert&#92;<Callsign>&#92;configs&#92;config.ini
C:&#92;Documents and Settings&#92;<UserName>&#92;Local Settings&#92;Application Data&#92;Ham-Apps&#92;JT-Alert&#92;<Callsign>&#92;sessions&#92;session.txt

Please email files as attachments in a direct email.

de Laurie, VK3AMA

On 23-October-2011 14:47, w7psk wrote:
PS
When I click ok the QSO gets logged.

--- In Ham-Apps@yahoogroups.com.au, "w7psk"<w7psk@...> wrote:
Keep getting this when I log using 1.5.1

JT65HF 1.0.7

I went into the file location and added the &#92; and saved

Still receiving it.