Date   

locked Logging with altert states in JT-Alert

jasnje
 

I'm new to this group, but have been using JT-Alert for nearly a year. One of the things that I think may be missing in JT-Alert and possible to implement is a log file of contacts.

It would be really nice if this logfile were similar to the logfile that JT65-HF creates but have the alert tags, and location for each contact.

So the old
"2013-01-01","01:31","3576","4","-10","-0.6","102","B","W2DX AE0AR 73","65A"

would appear:
"2013-01-01","01:31","3576","4","-10","-0.6","102","B","W2DX AE0AR 73","65A" <United States,KS,Alerts: Grid/State> ..... or something similar.

Basically it would append the information that you see in JT-Alert. This would give the ability for the user to view a log and see when that elusive contact shows up, or figure out when a certain DXCC usually comes online.

What do you think?


Thanks.
Jason
K7KKY


locked Re: HRD LOGGING PROBLEM

Mark W
 

I looked all over for that, guess I'll have to look again.
Thanks!
Mark


locked Re: [Ham-Apps] File in Use Error Message on upgrade

Laurie, VK3AMA <groups04@...>
 

Hi Rick,

This is a problem with XP. With Win7/Win8 the dialog offers an option to close the currently open applications. That works because once the setup has started then JT-Alert and the updater (which initiated the upgrade) are no longer actively participating in the upgrade and can be closed without aborting the upgrade.

I will be adding OS detection to the updater to only provide a download option for a JT-Alert upgrade if running under XP. The enduser will have to exit JT-Alert and manually run the setup file downloaded. It will have to be done this way due to XP limitations.

This change should be in the next release.

de Laurie VK3AMA

On 1/01/2013 6:22 AM, pontotochs wrote:
Hi All,
  I've noticed the "File In Use"f error message the last few times I've updated JT Alert. Hitting the Ignore button seems to work, but I was wondering if there is something else I need to be doing. The screen shot is included.
 
  Thanks,
    Rick, N5RB



locked Re: [Ham-Apps] HRD LOGGING PROBLEM

Laurie, VK3AMA <groups04@...>
 

Hi Mark,

Visit the logging section of the Configuration and change the logged mode to JT65.

de Laurie VK3AMA

On 1/01/2013 8:12 AM, k3mrk wrote:
I've been using HRD, JT-65HF and JT ALERT for quite a while with ZERO problems. they are all EXCELLENT products. All of the sudden about a month ago, i was unable to upload my HRD logs to LOTW. after much trial and error I found the problem to be that HRD is now logging the mode as JT65A. for some reason, that is causing a problem for me. if i go and change the mode on all the QSOs to JT-65, everything works like it always has. PERFECT. Anyone have any suggestions on how to get JT-65HF to log the mode as JT-65?
Also, I think this change happened when I upgraded JTALERT to 2.0.7. 
Not sure.
Mark
K3MRK



locked HRD LOGGING PROBLEM

Mark W
 

I've been using HRD, JT-65HF and JT ALERT for quite a while with ZERO problems. they are all EXCELLENT products. All of the sudden about a month ago, i was unable to upload my HRD logs to LOTW. after much trial and error I found the problem to be that HRD is now logging the mode as JT65A. for some reason, that is causing a problem for me. if i go and change the mode on all the QSOs to JT-65, everything works like it always has. PERFECT. Anyone have any suggestions on how to get JT-65HF to log the mode as JT-65?
Also, I think this change happened when I upgraded JTALERT to 2.0.7.
Not sure.
Mark
K3MRK


locked File in Use Error Message on upgrade

pontotochs <pontotochs@...>
 

Hi All,
  I've noticed the "File In Use"f error message the last few times I've updated JT Alert. Hitting the Ignore button seems to work, but I was wondering if there is something else I need to be doing. The screen shot is included.
 
  Thanks,
    Rick, N5RB
 


locked Re: [Ham-Apps] JT-Alert 2.0.8 available for download - Soundcard Fixes

***** <signalhz@...>
 

All works fine here. Thanks Laurie

73 Eddy N4ABN Happy New Year

On 12/31/2012 1:47 AM, Laurie, VK3AMA wrote:
 

JT-Alert 2.0.8 is ready for download.

The important fix here is the automatic detection of Windows initiated change of sound device ID while JT-Alert is running. JT-Alert will change to using the new ID without loss of audio alerts. This change in sound device ID only occurs under Vista/Win7/Win8 when an exisitng device is removed or goes into hibernation and then only if that device had a lower ID than the device used for JT-Alert audio announcements.

From the Release Notes...

  Fixes:
    - Sound playing with wrong soundcard after Windows reassigned Soundcard IDs.
    - Soundcard selection box not showing current setting (not all users).
    - One of the debugging session files being incorrectly truncated.
  Changes:
    - Decoded callsigns/colors are now cleared when Configuration is opened.
    - Language files will default to using English for missing words and phrases.
    - Setup now records a log of warnings and errors generated during install.

Download from here...
http://Ham-Apps.com/dnl/JTAlert/Ham-Apps_JT-Alert_2.0.8_Setup.exe

If you encounter any problems post a message to the Ham-Apps Yahoo group using a subject line related to the issue.
Please DON'
T just reply to this email. It doesn't help users doing message archive searches of specific issues.

de Laurie, VK3AMA



locked Re: [Ham-Apps] JT-Alert 2.0.8

Laurie, VK3AMA <groups04@...>
 

Tnx David,

All Setup programs on the server have been regenerated without the logging option until I can resolve this issue.

de Laurie VK3AMA

On 31/12/2012 6:49 PM, David wrote:
Hi Laurie....added the path as you suggested and setup installs on Win 7

David


On 31/12/12 17:31, Laurie, VK3AMA wrote:
 

Hi David,

I am not surprised about Wine.

2.0.8 now records a log of warnings or errors encountered by the Windows msiexec program when the setup is run. The setup is actually a wrapper for an .msi install file.

Under Win7, it would be trying to write to this path... "C:\Users\\AppData\Local\Ham-Apps\sessions"
Try creating that path and then run the setup again.

I will pull the 2.0.8 release from the server and regenerate the setup without the logging.

de Laurie VK3AMA

On 31/12/2012 6:04 PM, BuDJie wrote:
Hi Laurie.....
tried to install via Wine comes up with a error
so checked on my Win 7 laptop and it comes up with a Windows Installer error "Error opening installation log file. Verify that the specified log file location exists and is writable"

Happy new Year

73 David VK4BDJ






locked Re: [Ham-Apps] JT-Alert 2.0.8

BuDJie
 

Hi Laurie....added the path as you suggested and setup installs on Win 7

David


On 31/12/12 17:31, Laurie, VK3AMA wrote:
 

Hi David,

I am not surprised about Wine.

2.0.8 now records a log of warnings or errors encountered by the Windows msiexec program when the setup is run. The setup is actually a wrapper for an .msi install file.

Under Win7, it would be trying to write to this path... "C:\Users\\AppData\Local\Ham-Apps\sessions"
Try creating that path and then run the setup again.

I will pull the 2.0.8 release from the server and regenerate the setup without the logging.

de Laurie VK3AMA

On 31/12/2012 6:04 PM, BuDJie wrote:
Hi Laurie.....
tried to install via Wine comes up with a error
so checked on my Win 7 laptop and it comes up with a Windows Installer error "Error opening installation log file. Verify that the specified log file location exists and is writable"

Happy new Year

73 David VK4BDJ





locked Re: [Ham-Apps] JT-Alert 2.0.8

BuDJie
 

Hi Laurie...there is a path as follows in Win 7
C:\Users\David\App-Data\Local\Ham-Apps\JT-Alert\VK4BDJ\sessions

will try and make path as you suggest

David VK4BDJ

On 31/12/12 17:31, Laurie, VK3AMA wrote:
 

Hi David,

I am not surprised about Wine.

2.0.8 now records a log of warnings or errors encountered by the Windows msiexec program when the setup is run. The setup is actually a wrapper for an .msi install file.

Under Win7, it would be trying to write to this path... "C:\Users\\AppData\Local\Ham-Apps\sessions"
Try creating that path and then run the setup again.

I will pull the 2.0.8 release from the server and regenerate the setup without the logging.

de Laurie VK3AMA

On 31/12/2012 6:04 PM, BuDJie wrote:
Hi Laurie.....
tried to install via Wine comes up with a error
so checked on my Win 7 laptop and it comes up with a Windows Installer error "Error opening installation log file. Verify that the specified log file location exists and is writable"

Happy new Year

73 David VK4BDJ





locked Re: [Ham-Apps] JT-Alert 2.0.8

Laurie, VK3AMA <groups04@...>
 

Hi David,

I am not surprised about Wine.

2.0.8 now records a log of warnings or errors encountered by the Windows msiexec program when the setup is run. The setup is actually a wrapper for an .msi install file.

Under Win7, it would be trying to write to this path... "C:\Users\\AppData\Local\Ham-Apps\sessions"
Try creating that path and then run the setup again.

I will pull the 2.0.8 release from the server and regenerate the setup without the logging.

de Laurie VK3AMA

On 31/12/2012 6:04 PM, BuDJie wrote:
Hi Laurie.....
tried to install via Wine comes up with a error
so checked on my Win 7 laptop and it comes up with a Windows Installer error "Error opening installation log file. Verify that the specified log file location exists and is writable"

Happy new Year

73 David VK4BDJ




locked JT-Alert 2.0.8

BuDJie
 

Hi Laurie.....
tried to install via Wine comes up with a error
so checked on my Win 7 laptop and it comes up with a Windows Installer error "Error opening installation log file. Verify that the specified log file location exists and is writable"

Happy new Year

73 David VK4BDJ


locked [Ham-Apps] JT-Alert 2.0.8 available for download - Soundcard Fixes

Laurie, VK3AMA <groups04@...>
 

JT-Alert 2.0.8 is ready for download.

The important fix here is the automatic detection of Windows initiated change of sound device ID while JT-Alert is running. JT-Alert will change to using the new ID without loss of audio alerts. This change in sound device ID only occurs under Vista/Win7/Win8 when an existing device is removed or goes into hibernation and then only if that device had a lower ID than the device used for JT-Alert audio announcements.

From the Release Notes...
  Fixes:
    - Sound playing with wrong soundcard after Windows reassigned Soundcard IDs.
    - Soundcard selection box not showing current setting (not all users).
    - One of the debugging session files being incorrectly truncated.
  Changes:
    - Decoded callsigns/colors are now cleared when Configuration is opened.
    - Language files will default to using English for missing words and phrases.
    - Setup now records a log of warnings and errors generated during install.

Download from here...
http://Ham-Apps.com/dnl/JTAlert/Ham-Apps_JT-Alert_2.0.8_Setup.exe

If you encounter any problems post a message to the Ham-Apps Yahoo group using a subject line related to the issue.
Please DON'
T just reply to this email. It doesn't help users doing message archive searches of specific issues.

de Laurie, VK3AMA


locked Re: [Ham-Apps] Sound files default to none?

Laurie, VK3AMA <groups04@...>
 

Hi Andy,

This occurs when the JT-Alert upgrade is from 1.x to 2.0.x

There is technical reason combined with an oversight on my part that are the cause of the empty file paths. Sorry about that.

de Laurie VK3AMA

On 31/12/2012 5:28 AM, k3wyc wrote:
When I updated to 2.0.6 I didn't get the expected aural alerts.  I then found that JT Alert had not defaulted to the default wave file paths, they had to be selected.

Was there something unusual about my installation or is it intended that sound file defaults are not automatically selected at installation?

Mostly just curious and also wondering if anyone else had been caught by this.


Andy k3wyc



locked Re: Sound files default to none?

pcooper <pcooper@...>
 

Andy K3WYC and the group,

Yes, I found this out also. I upgraded from an earlier version (1.6.0) to 2.0.7 and only realised yesterday that I had lost audible alerts.

It wasn't until this morning that I found where they were, and also realised they were unassigned.
This puzzled me, as upgrading from 1.6.0 to 2.0.7 appeared to grab all other settings.
Even then, I only initially set the CALLING YOU part, and later realised that CQ was also missing, so I have now set that too.

As far as I can remember, the alerts were set by default in the earlier version, but do not appear to be so in this latest version.
I don't think it is a defect, just a change.

Still an amazing piece of software though!

73 and HNY to all
de Phil GU0SUP


locked Sound files default to none?

Andy k3wyc
 

When I updated to 2.0.6 I didn't get the expected aural alerts. I then found that JT Alert had not defaulted to the default wave file paths, they had to be selected.

Was there something unusual about my installation or is it intended that sound file defaults are not automatically selected at installation?

Mostly just curious and also wondering if anyone else had been caught by this.


Andy k3wyc


locked Re: [Ham-Apps] Questions

DGB <ns9i2016@...>
 

Thanks for all the directions. That was it, "Query callbook and DXCC database for missing items".

Works great now.

tnx again ... 73 Dwight NS9I

On 12/29/2012 8:57 PM, Jim McHale wrote:
 

Dwight,
To avoid hitting CBA:
(This is from a msg in this group on 2-Nov-2012):
if you check the "Query callbook and DXCC database for missing
items" box on the "Import QSOs" tab of DXKeeper's Import window, then each
time JT-Alert directs DXKeeper to log a QSO, DXKeeper will perform a lookup
using the callbook you've specified on its Configuration window's Callbook
tab.

I knew I'd seen it somewhere :) and that it cured my having to hit CBA..

That same import tab also has "deduce missing items from entity,
primary subdivision and DXCC database" which fills in missing items
like Cont, CQ, ITU, or ARRL Section when they can be unambiguously
determined from the DXCC entity and Primary Administrative Subdivision
and a DXCC database query of the imported callsign.

Also on the import qsos tab help button page under "Interactions with
other configuration settings" it mentions how to have lotw and eqsl
set to "R" automatically.
73
-Jim NM1W



locked Re: Voice announcement query

pcooper <pcooper@...>
 

Hello Laurie and the group,

I am now using version 2.0.7, and the voice announcements are not happening since upgrading from version 1.6.0.

However, I found the problem this morning! Because all other settings had been retained from the upgrade, I hadn't looked more closely at the configuration, but I now see that under the ALERTS part of the configuration, MY CALL and CQ had nothing in them, so I selected the appropriate sound files and it is now working!
Sorry for the trouble!

73 de Phil GU0SUP




locked Re: [Ham-Apps] Questions

Jim NM1W
 

Dwight,
To avoid hitting CBA:
(This is from a msg in this group on 2-Nov-2012):
if you check the "Query callbook and DXCC database for missing
items" box on the "Import QSOs" tab of DXKeeper's Import window, then each
time JT-Alert directs DXKeeper to log a QSO, DXKeeper will perform a lookup
using the callbook you've specified on its Configuration window's Callbook
tab.

I knew I'd seen it somewhere :) and that it cured my having to hit CBA..

That same import tab also has "deduce missing items from entity,
primary subdivision and DXCC database" which fills in missing items
like Cont, CQ, ITU, or ARRL Section when they can be unambiguously
determined from the DXCC entity and Primary Administrative Subdivision
and a DXCC database query of the imported callsign.

Also on the import qsos tab help button page under "Interactions with
other configuration settings" it mentions how to have lotw and eqsl
set to "R" automatically.
73
-Jim NM1W


locked FIXED - Callsign Databases Setup - New 12.12.30 version available

Laurie, VK3AMA <groups04@...>
 

For some users, typically on XP, the Callsign Databases install would fail. The file would download, but would throw an error when the setup file was opened by the updater program.

This was an obscure fault in the Installer software used to create the different Setup Programs. It didn't affect JT-Alert, JT-Macros or the Sounds Setup files.

A new installer project was created and Database installs are now working on the tests environments were it previously had a 100% failure rate.

Please visit the "Program Updates" section of the Configuration to install the latest version (12.12.30) for JT-Alert 2.0.5 or later only.

Note: If running a version of JT-Alert prior to 2.0.5 you will need to update it before you can get this new file. Also, all future database files will be only available for JT-Alert 2.0.5 or later. There will be NO callsign database updates after the 12.12.08 version for earlier JT-Alert releases.

de Laurie VK3AMA