Date   

locked Re: [Ham-Apps] mixw

David Pykett
 

Thanks Laurie, I look forward to 1.5.2 release whenever you get time to do it.
 
73
 
Dave
G0IIQ


 
 

Hi Dave,

Its on my "To be Implemented List".
It wont be in the upcoming 1.5.1 release due in about 2 days.

It will most likely be in the 1.5.2 release, but timing on that is unknown at this time.

de Laurie, VK3AMA


On 20-October-2011 07:16, David Pykett wrote:

,___


locked Test email. Please ignore

Laurie, VK3AMA <groups03@...>
 

Testing if Yahoo Groups is having message posting/delivery problems today.
posted @ 0816 21-Oct utc

de Laurie, VK3AMA


locked Re: Test email. Please ignore

Laurie <groups03@...>
 

Received OK.
Must be just a very quiet day on Yahoo today.

--- In Ham-Apps@yahoogroups.com.au, "Laurie, VK3AMA" <groups03@...> wrote:

Testing if Yahoo Groups is having message posting/delivery problems today.
posted @ 0816 21-Oct utc

de Laurie, VK3AMA


locked Re: [Ham-Apps] Re: Test email. Please ignore

John <john@...>
 

Make the most of the silence Laurie :-D

73, John

On 21/10/2011 09:18, Laurie wrote:
 

Received OK.
Must be just a very quiet day on Yahoo today.

--- In Ham-Apps@..., "Laurie, VK3AMA" wrote:
>
> Testing if Yahoo Groups is having message posting/delivery problems today.
> posted @ 0816 21-Oct utc
>
> de Laurie, VK3AMA
>


locked Logging problems

g4gcl <john@...>
 

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked Re: [Ham-Apps] Logging problems

Laurie, VK3AMA <groups03@...>
 

Hi John,

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.

Regards
Laurie, VK3AMA


On 22-October-2011 02:58, g4gcl wrote:

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked Re: [Ham-Apps] Logging problems

John <john@...>
 

Hi Laurie.
We have visitors tonight so I will go through all your suggestions in the morning!

One quick thing is that the B4 path is actually there and is pointing to the same database used in 1.4.1 it was the path to the ADIF log file which had disappeared. I put it back in but still had the problems described.
I follow what you say about JT-Alert not locking the file but the strange thing is that it has worked, and still does work perfectly with version 1.4.1 which makes me think that JT65-HF and ADIF Master are not the culprits.

I'm running AVG Free, the latest 2012 version.

As I said I will work through your suggestions very carefully in the morning when the visitors leave. As always I appreciate all your help and it really is not a major problem because I can still use V1.4.1.

Very many thanks.
73,
John.

On 21/10/2011 21:54, Laurie, VK3AMA wrote:
 

Hi John,

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.

Regards
Laurie, VK3AMA


On 22-October-2011 02:58, g4gcl wrote:

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked JT-Alert 1.5.1 now available for download.

Laurie, VK3AMA <groups03@...>
 


JT-Alert 1.5.1 is now available for download at http://Ham-Apps.com/

This version contains important Bug Fixes. It is recommended this version is installed.
 
Note: There is no help file at present.

Note: JT-Alert 1.5.1 comes bundled with Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.

Install Instructions:
  1. Uninstall 1.5.0.
  2. Download either the Male or Female voice JT-Alert setup file.
  3. Run the newly downloaded file and install to a directory of your choice (it is OK to install the Program Files directory tree of Vista or Win7 as files that are modified and/or created by JT-Alert are store in the Users Local AppData area so there are no security issues).
  4. While JT-Alert is running, click the word "Settings" in the title-bar and click "Configuration..." on the displayed menu.
  5. In the Configuration window check that your settings are still correct.
  6. Close the Configuration window, saving the settings.
  7. JT-Alert 1.5.1 is now setup.
From the Release notes:
  New    - HRDV5 & DXKeeper options to flag QSO with LoTW/eQSL upload requested.
  New    - Additional error detection and warning of inability to locate
            the JT65-HF log file and or path.
  New    - Support for multi-monitor PCs when moving and restoring windows.
  New    - Option to not use Memory Cache for DB query results.
            (Only enable if advised by Support)
  New    - Warning if log & database files specified in Config don't exist.
            (file paths will get reset to blank in Config after this warning)
  Change - Removed pop-up window display timeout for failed QSO logging.
  Change - Logging Configuration layout for clearer understanding of which log
            is active. Enabling one log force disables other logs.
  Change - JT65-HF Notes now logged to HRDV5 Comments field.
  BugFix - Callsign not shown as B4 after failed QSO Log message.
  BugFix - Failed Log message when QSO was correctly logged due to timing.
  BugFix - Windows Regional Settings with non-dot used as decimal separator
            caused logging failures and SQL error messages.
  BugFix - Config window position off screen.
  BugFix - HRDV5 log crash when missing DXCC code logged.
  BugFix - HRDV5 QSOs being flagged as SWL rather than normal contact.
  BugFix - DXLab Workspaces caused JT-Alert Configuration to abort.
  BugFix - Spaces in JT65-HF Log path or no trailing backslash caused no logging.
  BugFix - Sound OFF setting not being remembered between restarts.
  BugFix - Out of Shack alert not correctly toggling Wanted Calls check mark.
  BugFix - JT-Alert always on top not working.
  BugFix - DXKeeper Lookup on new JT65-HF "TX to Call Sign" entry not working.

If you experience problems or have questions post a message to the Ham-Apps Yahoo Group.
Please DON'T reply to this message with your questions.
Start a new message with a subject line that reflects the question or problem.

Enjoy,
de Laurie, VK3AMA


locked Re: [Ham-Apps] JT-Alert 1.5.1 now available for download.

BuDJie
 

Hi Laurie..is this version compatible with Wine
under Linux

73 David VK4BDJ




On 22/10/11 08:59, Laurie, VK3AMA wrote:
 


JT-Alert 1.5.1 is now available for download at http://Ham-Apps.com/

This version contains important Bug Fixes. It is recommended this version is installed.
 
Note: There is no help file at present.

Note: JT-Alert 1.5.1 comes bundled with Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.

Install Instructions:

  1. Uninstall 1.5.0.
  2. Download either the Male or Female voice JT-Alert setup file.
  3. Run the newly downloaded file and install to a directory of your choice (it is OK to install the Program Files directory tree of Vista or Win7 as files that are modified and/or created by JT-Alert are store in the Users Local AppData area so there are no security issues).
  4. While JT-Alert is running, click the word "Settings" in the title-bar and click "Configuration..." on the displayed menu.
  5. In the Configuration window check that your settings are still correct.
  6. Close the Configuration window, saving the settings.
  7. JT-Alert 1.5.1 is now setup.
From the Release notes:
  New    - HRDV5 & DXKeeper options to flag QSO with LoTW/eQSL upload requested.
  New    - Additional error detection and warning of inability to locate
            the JT65-HF log file and or path.
  New    - Support for multi-monitor PCs when moving and restoring windows.
  New    - Option to not use Memory Cache for DB query results.
            (Only enable if advised by Support)
  New    - Warning if log & database files specified in Config don't exist.
            (file paths will get reset to blank in Config after this warning)
  Change - Removed pop-up window display timeout for failed QSO logging.
  Change - Logging Configuration layout for clearer understanding of which log
            is active. Enabling one log force disables other logs.
  Change - JT65-HF Notes now logged to HRDV5 Comments field.
  BugFix - Callsign not shown as B4 after failed QSO Log message.
  BugFix - Failed Log message when QSO was correctly logged due to timing.
  BugFix - Windows Regional Settings with non-dot used as decimal separator
            caused logging failures and SQL error messages.
  BugFix - Config window position off screen.
  BugFix - HRDV5 log crash when missing DXCC code logged.
  BugFix - HRDV5 QSOs being flagged as SWL rather than normal contact.
  BugFix - DXLab Workspaces caused JT-Alert Configuration to abort.
  BugFix - Spaces in JT65-HF Log path or no trailing backslash caused no logging.
  BugFix - Sound OFF setting not being remembered between restarts.
  BugFix - Out of Shack alert not correctly toggling Wanted Calls check mark.
  BugFix - JT-Alert always on top not working.
  BugFix - DXKeeper Lookup on new JT65-HF "TX to Call Sign" entry not working.

If you experience problems or have questions post a message to the Ham-Apps Yahoo Group.
Please DON'T reply to this message with your questions.
Start a new message with a subject line that reflects the question or problem.

Enjoy,
de Laurie, VK3AMA



locked Re: [Ham-Apps] JT-Alert 1.5.1 now available for download.

Laurie, VK3AMA <groups03@...>
 

HI David,

It is using the same linux/Wine code as the test version you have been running. Your version doesn't include all the additional bugfixes or changes. I recommend you install this new version.

73 de Laurie, VK3AMA

On 22-October-2011 11:21, David wrote:
Hi Laurie..is this version compatible with Wine
under Linux

73 David VK4BDJ




On 22/10/11 08:59, Laurie, VK3AMA wrote:
 


JT-Alert 1.5.1 is now available for download at http://Ham-Apps.com/

This version contains important Bug Fixes. It is recommended this version is installed.
 
Note: There is no help file at present.

Note: JT-Alert 1.5.1 comes bundled with Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.

Install Instructions:

  1. Uninstall 1.5.0.
  2. Download either the Male or Female voice JT-Alert setup file.
  3. Run the newly downloaded file and install to a directory of your choice (it is OK to install the Program Files directory tree of Vista or Win7 as files that are modified and/or created by JT-Alert are store in the Users Local AppData area so there are no security issues).
  4. While JT-Alert is running, click the word "Settings" in the title-bar and click "Configuration..." on the displayed menu.
  5. In the Configuration window check that your settings are still correct.
  6. Close the Configuration window, saving the settings.
  7. JT-Alert 1.5.1 is now setup.
From the Release notes:
  New    - HRDV5 & DXKeeper options to flag QSO with LoTW/eQSL upload requested.
  New    - Additional error detection and warning of inability to locate
            the JT65-HF log file and or path.
  New    - Support for multi-monitor PCs when moving and restoring windows.
  New    - Option to not use Memory Cache for DB query results.
            (Only enable if advised by Support)
  New    - Warning if log & database files specified in Config don't exist.
            (file paths will get reset to blank in Config after this warning)
  Change - Removed pop-up window display timeout for failed QSO logging.
  Change - Logging Configuration layout for clearer understanding of which log
            is active. Enabling one log force disables other logs.
  Change - JT65-HF Notes now logged to HRDV5 Comments field.
  BugFix - Callsign not shown as B4 after failed QSO Log message.
  BugFix - Failed Log message when QSO was correctly logged due to timing.
  BugFix - Windows Regional Settings with non-dot used as decimal separator
            caused logging failures and SQL error messages.
  BugFix - Config window position off screen.
  BugFix - HRDV5 log crash when missing DXCC code logged.
  BugFix - HRDV5 QSOs being flagged as SWL rather than normal contact.
  BugFix - DXLab Workspaces caused JT-Alert Configuration to abort.
  BugFix - Spaces in JT65-HF Log path or no trailing backslash caused no logging.
  BugFix - Sound OFF setting not being remembered between restarts.
  BugFix - Out of Shack alert not correctly toggling Wanted Calls check mark.
  BugFix - JT-Alert always on top not working.
  BugFix - DXKeeper Lookup on new JT65-HF "TX to Call Sign" entry not working.

If you experience problems or have questions post a message to the Ham-Apps Yahoo Group.
Please DON'T reply to this message with your questions.
Start a new message with a subject line that reflects the question or problem.

Enjoy,
de Laurie, VK3AMA



locked jt-alert

jgmags2000 <jgmags2000@...>
 

Fabulous! fabulous job Laurie.. All working well. Incredible piece of software, thank you for this gift. One question. Could HAlt/tx be moved to the title bar using only 1 click instead of going into set up?

Again, thanks Laurie

73, John KJ1J


locked Re: [Ham-Apps] jt-alert

Laurie, VK3AMA <groups03@...>
 

Hi John,

Moving the Halt TX to the titlebar would save one mouse-click.

I will consider your request and if it doesn't make the titlebar visually crowded it may be in the next release.

de Laurie, VK3AMA

On 22-October-2011 17:13, jgmags2000 wrote:
Fabulous! fabulous job Laurie.. All working well. Incredible piece of software, thank you for this gift. One question. Could HAlt/tx be moved to the title bar using only 1 click instead of going into set up?

Again, thanks Laurie

73, John KJ1J


locked How to freeze a position on screen for new startup ?

FORESTIER <f5rrs@...>
 

Hi,

I'm testing the new 1.5.1 version and would like first to thanks Laurie for this very great job !
I have a little request : When I start JT-Alert 1.5.1 it appears on left side (vertical position) and at the middle (horizontal position) of the screen.
I moved it to my favorite position on the screen but on the next startup this position is to recorded. Everything was working fine on 1.5.0
I use Win7 64bit with 3 screens and WinXp laptop (1 screen) with the same result.
Any idea ?

73 - Damien F5RRS


locked Re: [Ham-Apps] How to freeze a position on screen for new startup ?

Laurie, VK3AMA <groups03@...>
 

Hi Damien,

There were changes made in 1.5.1 to support multi-monitors and also code to prevent JT-Alert or its configuration window from opening off screen (fully or partially). Maybe I introduced a bug.

Can you please send me 2 screen-captures. One showing where JT-Alert is positioned on startup (the incorrect position) and the other showing JT-Alert in your preferred position. Please email them to me direct as attachments.

de Laurie, VK3AMA

On 22-October-2011 20:43, FORESTIER wrote:
Hi,

I'm testing the new 1.5.1 version and would like first to thanks Laurie for this very great job !
I have a little request : When I start JT-Alert 1.5.1 it appears on left side (vertical position) and at the middle (horizontal position) of the screen.
I moved it to my favorite position on the screen but on the next startup this position is to recorded. Everything was working fine on 1.5.0
I use Win7 64bit with 3 screens and WinXp laptop (1 screen) with the same result.
Any idea ?

73 - Damien F5RRS


locked Re: [Ham-Apps] Logging problems

John <john@...>
 

Hi Laurie.
I have spent a little time trying to work out the failure mode.

The ADIF file is in the same location it's always been and so is the database. The only change I made was to get rid of the space in the folder name as you recommended and changed everything to match plus adding the \ of course.

If I start JT65-HF & JT-Alert and log a contact without ADIF Master running then I get an error. If I close down JT-Alert before pressing the log button it's fine. If I log the QSO and then, without JT-Alert running, open the ADIF file with ADIF Master it's fine but if, after logging without JT-Alert running I start it up and then try to open the file ADIF Master tells me that it is the incorrect format. If I close down JT-Alert at that point and try to open the file again it's fine.

None of these problems occur with 1.4.1.

I really get the impression that JT-Alert, as I have it set up, is taking over the log file and restricting access. Obviously it's my setup!

Here is the config of the log file location and the database. Can you see any obvious error?





I am obviously doing something very silly with a very simple setup but I can't see what!

All the very best Laurie,
John.





On 21/10/2011 21:54, Laurie, VK3AMA wrote:
 

Hi John,

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.

Regards
Laurie, VK3AMA


On 22-October-2011 02:58, g4gcl wrote:

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked call change

WX4CB <ai4ri@...>
 

i accidentally put my call as wxc4cb when i installed it. is there a way to change it in jtalert?

i tried just renaming the folder but it didnt work.

charlie
wx4cb


locked Reduce to taksbar

Larry Bryan
 

Laurie,

I thought in previous versions that when I reduced JT65 to the task bar it took JT-Alert with it and when I brought JT-65 back up JT-Alert came back up with it. I have always had JTA docked and I drop JT65 to taskbar all the time, that's why I bring this up. I don't remember having to click on both taskbar icons to get both on screen.

Larry
W8LIG


locked Logs to HRD log ; not to LotW

w7rjc
 

Hi Laurie,
Well I'm gaining .. I guess.
I can now get JT-Alert to put a record in the HRD log.
However when I hit the LotW upload button in HRD log I get the following error windows

TGSL error window
"Name not found"

LotW window
"Failed to sign the ADIF with TQSL"

I expect I'm geting the LotW window because of the failure in the TGSL window.

I have no Idea what name they are refering to ??? Passward or file location or ???

I have (can) transfer the JT65 adif file to my AClog program and upload to LotW with no errors .. I use the same TQSL paswords there.

Perhaps you could add AClog to your future revision list.

Thanks for your help .. this is getting down right embarassing.. HI Hi
Ray W7RJC


locked hrd 5 odbc failure

Charles Blackburn <ai4ri@...>
 

Using mysql on a separate machine, I rying to get hrd logging working.

 

I get the following error when it tries to log to hrd.

 

“sorry there appears to be an error

 

ODBC Ddrover does not support the requested properties

Err.number is 80020009

Scriptline is -1

Source is Microsoft ole db provider for odbc drivers

 

I click OK and then I get another error that says the same thing except in the description it says.

 

[mysql][odbc 5.1 drviver][mysqld-5.1.49-3]Table ‘hrdlog.table_hrd_contacts_v01’ doesnt exist

 

Charlie

Wx4cb


locked Re: [Ham-Apps] How to freeze a position on screen for new startup ?

W5ADD@arrl.net
 

On Oct 22, 2011, at 4:58 AM, Laurie, VK3AMA wrote:

There were changes made in 1.5.1 to support multi-monitors and also code
to prevent JT-Alert or its configuration window from opening off screen
(fully or partially). Maybe I introduced a bug.

Works fine here now in 1.5.1, stays right in place.

Windows 7 (64-bit) / Parallels 7 - w/multiple desktop views.

--
Parker, W5ADD

161 - 180 of 36910