Date   

locked Re: New - JTAlert 2.4.4 available - JT65-Comfort Support

Morris WA4MIT
 

Where is the Comfort 4.0 download. Link?

It is not showing up on the site I have used in the past for Comfort downloads.

73 WA4MIT


locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Ed Wilson
 

Laurie,

Actually, I am not sure whether they are showing-up or not (I will check later this morning). I thought that you had said that this was one of the fixes in 2.4.3, so I assumed that any JT65 contacts that I had previously made with WSJT-X and JTAlert-X 2.4.1 would not show-up as worked B4. If this is not correct, then it is a non-issue.

JT65 contacts made since the upgrade are definitely showing as worked B4...I remember that from yesterday.

I just log the contacts via WSJT-X.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 9:50 PM
Subject: Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
Hi Ed,

If previously worked JT65 stations under wsjt-x are not showing as B4 then something is wrong and I will need to look at your config file.
Are you using logging or just relying on the internal B4Log.mdb file?

Please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis.

de Laurie VK3AMA


On 29/07/2013 9:15 PM, Ed Wilson wrote:
Actually, Laurie, I was wondering about any JT65 stations that I may have worked with WSJT-X not showing-up as worked B4.
 
Ed, K0KC





locked New - JTAlert 2.4.4 available - JT65-Comfort Support

Laurie, VK3AMA <groups05@...>
 

JTAlert 2.4.4 is available for download.

From the Release Notes...
  New Features:
    - Works with JT65-Comfort 4.0.0 by DL4OCE (Alpha release).
    - Works with JT65-Comfort 3.6 by DL3VCO. NOTE: JTAlert logging only supports
       Comfort internal log types adif and MixW only.
    - German Language File.

  Changes:
    - JT65-HF JT65A decodes now spotted using the true DF offset from the QRG
       rather than DF zero = 1250Hz as traditionally reported by JT65-HF.

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.
  • virusscan.jotti.org : 100% pass against 22 engines. Results
  • virustotal.com : 100% pass against 43 engines. Results
de Laurie VK3AMA




locked Re: [Ham-Apps] jt9 mode bug? when logging to DXKeeper

Sam Morgan
 

You were correct, my DXKeeper version was 1120
after updating it's now version 1129

I had been starting the DXLabs pgms individually instead of with the Launcher so I wasn't getting the update notices <--op error agn (sigh)

and I had edited the C:&#92;DXLab&#92;DXKeeper&#92;Databases&#92;DefaultModes.txt file
saving it as C:&#92;DXLab&#92;DXKeeper&#92;Databases&#92;Modes.txt

as suggested months back using the info found here:
http://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Defining or Eliminating Modes

I think my problem was, I had added these lines:

JT9-1, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-2, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-5, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-10, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-30, DXCC_DIGI, WAZ_Digital, WPX_Digital


but just now I edited it again and added this line:

JT9, DXCC_DIGI, WAZ_Digital, WPX_Digital

now DXKeeper has both as choices in the QSO Mode drop down window

once again thanks for your help and great software!

On 7/29/2013 8:55 PM, Laurie, VK3AMA wrote:
Sam,

How old is your DXKeeper version?

I seem to recall that there is a file that can be edited to extend the list of
mode names.
Three of my DXKeeper installs all show JT9 and JT9-1 as being available in the
mode dropdown.
Two of those installs are just using defaults (for testing purposes) and I
didn't have to edit any files.
Perhaps a DXK upgrade will be the quickest solution.

de Laurie VK3AMA


On 29/07/2013 10:55 PM, Sam Morgan wrote:
When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?
--

GB & 73
K5OAI
Sam Morgan


locked Re: [Ham-Apps] jt9 mode bug? when logging to DXKeeper

Joe Subich, W4TV
 

Either add the following lines to DXKeeper&#92;Databases&#92;Modes.txt

JT9, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-1, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-2, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-5, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-10, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-30, DXCC_RTTY, WAZ_Digital, WPX_Digital

or configure JTAlert-X to log only the mode (JT9) and not sub-mode
(JT9-1).

73,

... Joe, W4TV

On 7/29/2013 9:55 PM, Laurie, VK3AMA wrote:


Sam,

How old is your DXKeeper version?

I seem to recall that there is a file that can be edited to extend the list of
mode names.
Three of my DXKeeper installs all show JT9 and JT9-1 as being available in the
mode dropdown.
Two of those installs are just using defaults (for testing purposes) and I
didn't have to edit any files.
Perhaps a DXK upgrade will be the quickest solution.

de Laurie VK3AMA


On 29/07/2013 10:55 PM, Sam Morgan wrote:
When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?



locked Re: [Ham-Apps] jt9 mode bug? when logging to DXKeeper

Laurie, VK3AMA <groups05@...>
 

Sam,

How old is your DXKeeper version?

I seem to recall that there is a file that can be edited to extend the list of mode names.
Three of my DXKeeper installs  all show JT9 and JT9-1 as being available in the mode dropdown.
Two of those installs are just using defaults (for testing purposes) and I didn't have to edit any files.
Perhaps a DXK upgrade will be the quickest solution.

de Laurie VK3AMA


On 29/07/2013 10:55 PM, Sam Morgan wrote:
When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?



locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Laurie, VK3AMA <groups05@...>
 

Hi Ed,

If previously worked JT65 stations under wsjt-x are not showing as B4 then something is wrong and I will need to look at your config file.
Are you using logging or just relying on the internal B4Log.mdb file?

Please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis.

de Laurie VK3AMA


On 29/07/2013 9:15 PM, Ed Wilson wrote:
Actually, Laurie, I was wondering about any JT65 stations that I may have worked with WSJT-X not showing-up as worked B4.
 
Ed, K0KC



locked jt9 mode bug? when logging to DXKeeper

Sam Morgan
 

When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?

--

GB & 73
K5OAI
Sam Morgan


locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Ed Wilson
 

Actually, Laurie, I was wondering about any JT65 stations that I may have worked with WSJT-X not showing-up as worked B4.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 6:36 AM
Subject: Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
Hi Ed,

No need for the log scan, unless you want to update your Wanted Lists.
Existing wanted lists are maintained during the 2.4.3 upgrade.

With 2.4.0, there was a fundamental change in how the lists were internally maintained and named that was not compatible with versions pre 2.4.0 so pre 2.4.0 lists couldn't be upgraded. Thus the special requirement to do a Log Scan or manual update.

I need to update the Ham-Apps site to better explain this.

de Laurie VK3AMA

On 29/07/2013 7:18 PM, Ed Wilson wrote:
Laurie,

With this new version, do we have to do a log scan to pick-up the JT65 calls that were not recorded (as worked B4) under WSJT-X?

If so, is it normal that I lose all of my wanted state information after a log scan and need to re-enter it manually; this was the case for the last upgrade that required a log scan.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 4:01 AM
Subject: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
JTAlert 2.4.3 is available for download.

This release fixes the defect introduced in 2.4.2 where JTMacros when set to auto-start would always start in
"wsjtx" mode resulting in missing macros and non-docking when started for JT65-HF

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA





locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Laurie, VK3AMA <groups05@...>
 

Hi Ed,

No need for the log scan, unless you want to update your Wanted Lists.
Existing wanted lists are maintained during the 2.4.3 upgrade.

With 2.4.0, there was a fundamental change in how the lists were internally maintained and named that was not compatible with versions pre 2.4.0 so pre 2.4.0 lists couldn't be upgraded. Thus the special requirement to do a Log Scan or manual update.

I need to update the Ham-Apps site to better explain this.

de Laurie VK3AMA

On 29/07/2013 7:18 PM, Ed Wilson wrote:
Laurie,

With this new version, do we have to do a log scan to pick-up the JT65 calls that were not recorded (as worked B4) under WSJT-X?

If so, is it normal that I lose all of my wanted state information after a log scan and need to re-enter it manually; this was the case for the last upgrade that required a log scan.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 4:01 AM
Subject: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
JTAlert 2.4.3 is available for download.

This release fixes the defect introduced in 2.4.2 where JTMacros when set to auto-start would always start in
"wsjtx" mode resulting in missing macros and non-docking when started for JT65-HF

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA



locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Ed Wilson
 

Laurie,

With this new version, do we have to do a log scan to pick-up the JT65 calls that were not recorded (as worked B4) under WSJT-X?

If so, is it normal that I lose all of my wanted state information after a log scan and need to re-enter it manually; this was the case for the last upgrade that required a log scan.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 4:01 AM
Subject: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
JTAlert 2.4.3 is available for download.

This release fixes the defect introduced in 2.4.2 where JTMacros when set to auto-start would always start in
"wsjtx" mode resulting in missing macros and non-docking when started for JT65-HF

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA






locked New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Laurie, VK3AMA <groups05@...>
 

JTAlert 2.4.3 is available for download.

This release fixes the defect introduced in 2.4.2 where JTMacros when set to auto-start would always start in
"wsjtx" mode resulting in missing macros and non-docking when started for JT65-HF

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA




locked DEFECT: JTAlert 2.4.2 - broken auto-start of JTMacros

Laurie, VK3AMA <groups05@...>
 

Erik,

Sorry about that.
I can confirm that JTMacros when set to autostart is broken and will always start. in wsjtx mode. This is why it is not docking and your original JT65-HF specific macros are not visible.

I will have a new release within the next 30 minutes.

Regarding "enable RB" and "enable PSKR" and their counters, they are unaffected by JTAlert. The counters are auto-incremented when JT65-HF has uploaded spots to the RBN and PSKR. JTAlert 2.4.2 will not be the cause for those to not work. Perhaps your virus software is preventing JT65_HF access to the Internet.

de Laurie VK3AMA

On 29/07/2013 2:39 PM, k5ww@... wrote:
Some interesting new features and a couple of good fixes, thanks.
 
But something went wrong here, during the upgrade. JT-macros 2.4.2 seems to have lost my favorite (custom) macros, and is no longer docked to JT65-HF.
 
And even though "enable RB" and "enable PSKR" boxes are checked, nothing seems to get reported at all. Both counters are still at "0", after an hour or so.
 
What did I mess up?

73,
 
Erik - K5WW
 
----- Original Message -----
Sent: Sunday, July 28, 2013 6:46 PM
Subject: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

 

A new version, 2.4.2 of JTAlert is available.

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.


From the Release Notes...

  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA





locked Re: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

k5ww@...
 

Some interesting new features and a couple of good fixes, thanks.
 
But something went wrong here, during the upgrade. JT-macros 2.4.2 seems to have lost my favorite (custom) macros, and is no longer docked to JT65-HF.
 
And even though "enable RB" and "enable PSKR" boxes are checked, nothing seems to get reported at all. Both counters are still at "0", after an hour or so.
 
What did I mess up?

73,
 
Erik - K5WW
 

----- Original Message -----
Sent: Sunday, July 28, 2013 6:46 PM
Subject: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

 

A new version, 2.4.2 of JTAlert is available.

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.


From the Release Notes...

  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA




locked Re: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

bill <bill@...>
 

Thank you Laurie
The Update to eQSL worked perfectly on my first try.
and.....

Whatever you did, also corrected the anomaly of my selecting a Macro with '73 in it while sending a report DID NOT also print a duplicate of the current message into the RX Freq panel
Nor force the Log QSO pane to open

That alone will help me keep track of what I'm doing.

Owe you Man....


On 2013-07-28 6:46 PM, Laurie, VK3AMA wrote:
A new version, 2.4.2 of JTAlert is available.

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.


From the Release Notes...
  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA




-- 

Black holes were created when God divided by zero.
---------------------------
I have an unequaled gift.. of squeezing BIG mistakes into LOST opportunities.
W9OL-Bill H. in Chicagoland
webcams at http://w9ol-towercam.webhop.org:8080
My weatherpage at http://home.comcast.net/~w9ol/WX/HH.htm


locked Re: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

digisignal@...
 

Thank you Laurie

73 Eddy N4ABN



On Sunday, July 28, 2013 at 7:46 PM, "VK3AMA Laurie" wrote:
 

A new version, 2.4.2 of JTAlert is available.

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.


From the Release Notes...

  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA




locked New - JTAlert 2.4.2 available - Fixes and changes

Laurie, VK3AMA <groups05@...>
 

A new version, 2.4.2 of JTAlert is available.

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.


From the Release Notes...
  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA




locked Re: [Ham-Apps] JTAlert Txt MSG request(s)

Ed Wilson
 

Thanks for considering this request, Laurie...no hurry, just would be a nice feature.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Sunday, July 28, 2013 4:41 PM
Subject: Re: [Ham-Apps] JTAlert Txt MSG request(s)

 
Text messages accidentally got released while it was still a "proof of concept" I was testing and some features, like audio alert and reply button, were not completed or available at that time.

It is on the todo list.

de Laurie VK3AMA

On 27/07/2013 9:27 PM, Ed Wilson wrote:
Speaking of "wish" lists, would it be difficult to include a "Reply" button on the text message window?

Ed, K0KC


From: Sam Morgan
To: Ham-Apps@...
Sent: Saturday, July 27, 2013 7:11 AM
Subject: [Ham-Apps] JTAlert Txt MSG request(s)

 
Low priority, but .......
Would it be possible to add a 'toggle' to log text messages sent?
Date, Time, Station sent to, Message content.

if it's a case of to much already happening at the end (50-60 sec mark)
perhaps right after the band map is populated and b4 the decodes come in?
or any time during the cycle for that matter
just so there is a log of what was sent.

also sometimes I fear what was sent may have been lost, not received,
and want to repeat the message, but don't rem exactly how I worded it,
or things are so busy I don't have time to retype it.

A drop down menu with the last 2-3 previous messages sent
and a resend button would be really nice.

--

GB & 73
K5OAI
Sam Morgan






locked Re: [Ham-Apps] Audio Alert on Text Message?

Don Hill AA5AU
 

Thanks Laurie. I hooked up my second sound card to speakers last night. Took me all but two minutes to do. Audio alerts are working fine on both JT-Alert & JT-Alert-X. Not sure why I didn't do this earlier.

The text feature in JT-Alert-X is really cool. The HamSpots website is just excellent. Just wish people would be more mindful of what band they are on. Numerous spots going out for wrong bands.

Still haven't gone to WSJT-X 1.1 yet. Still using JT65-HF for JT65 & WSJT-X 1.0 for JT9. Good enough for now.

73, Don AA5AU


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Sunday, July 28, 2013 3:36 PM
Subject: Re: [Ham-Apps] Audio Alert on Text Message?

 
Hi Don,

No, there is no audio alert for text messages. Text messages accidentally got released while it was still a "proof of concept" I was testing and some features, like audio alert and reply button, were not completed or available at that time.

It is on the todo list.

de Laurie VK3AMA

On 28/07/2013 2:26 PM, Don AA5AU wrote:
I did not see where there is an alert for receiving a text message. Is there an audible alert for that?

Thanks,
Don AA5AU




locked Re: [Ham-Apps] JTAlert Txt MSG request(s)

Laurie, VK3AMA <groups05@...>
 

Text messages accidentally got released while it was still a "proof of concept" I was testing and some features, like audio alert and reply button, were not completed or available at that time.

It is on the todo list.

de Laurie VK3AMA

On 27/07/2013 9:27 PM, Ed Wilson wrote:
Speaking of "wish" lists, would it be difficult to include a "Reply" button on the text message window?

Ed, K0KC


From: Sam Morgan
To: Ham-Apps@...
Sent: Saturday, July 27, 2013 7:11 AM
Subject: [Ham-Apps] JTAlert Txt MSG request(s)

 
Low priority, but .......
Would it be possible to add a 'toggle' to log text messages sent?
Date, Time, Station sent to, Message content.

if it's a case of to much already happening at the end (50-60 sec mark)
perhaps right after the band map is populated and b4 the decodes come in?
or any time during the cycle for that matter
just so there is a log of what was sent.

also sometimes I fear what was sent may have been lost, not received,
and want to repeat the message, but don't rem exactly how I worded it,
or things are so busy I don't have time to retype it.

A drop down menu with the last 2-3 previous messages sent
and a resend button would be really nice.

--

GB & 73
K5OAI
Sam Morgan