Support@HamApps.groups.io

Re: Possible Timing Bug?

pcooper <pcooper@...>

#8962

Hi all,

I too have had this occur, and I also use DXKeeper with JTAlert.

The way I sort it is when I hit the LOG QSO button (in JT65HF), that brings up a dialogue box, and I simply adjust the start time in there, and then click LOG.

Maybe this is because I am using JT65HF, and it may not occur in other JT65 programs, but if it does, then that is one option for correcting the start time.

Best 73

Phil GU0SUP

Re: Possible Timing Bug?

Michael Black

#8961

Nope...2nd click does nothing right now. Only the 1st time JTAlert sees it. Laurie has discussed this before but it might be worth revisiting.

73

Mike W9MDB

Show quoted text

From: "Dave 'Doc' Corio kb3mow@... [HamApps]"
To: HamApps@...
Sent: Saturday, August 22, 2015 5:22 PM
Subject: Re: [HamApps] Possible Timing Bug?

I always thought using the "Erase" key cleared the current information from the queue. I'll have to be more aware of that. Sometimes takes several tries to get a station.

On the other hand, I had double-clicked his call the second time I responded to his CQ - seems like that alone should have reset the start timer?

Tnx es 73
Doc
KB3MOW

Dave 'Doc' Corio
KB3MOW

On 8/22/2015 6:00 PM, Black Michael mdblack98@... [HamApps] wrote:

Click the ? to find the contact support dialog.

As for your CQ...JTAlert records the 1st time you started it. If you wanted to record the 2nd time you started you need to either double-click in JTAlert's "Time" window or click to another call and back again.

I have to admit it would be nice if the CQ reset that timer. Sounds like it would be easy to do....Laurie????

73

Mike W9MDB

From: "kb3mow@... [HamApps]"

To: HamApps@...
Sent: Saturday, August 22, 2015 4:41 PM
Subject: [HamApps] Possible Timing Bug?

In 2.6.13 I have been unable to find the "Contact Support" option!

This problem, however, is timing of contacts going into the Log (DXKeeper in this case). Here's the chronology:

20:18 Station NxABC calls CQ

20:19 I answer his CQ with a call

20:20 He calls a different station (heard them instead of me)

at this point I "Erased" the call from WSJT-X

20:33 NxABC calls CQ once again

20:34 I answer his CQ with a call

At this point, the QSO proceeds as normal, ending at 20:38, at which time I logged the contact via the prompt from JTAlert. The log entry in DXKeeper, however, shows the original time of 20:19, creating a discrepancy between our two stations regarding LoTW and EQSL.

Tnx es 73

Doc

KB3MOW

Re: Possible Timing Bug?

K1DJE - Dave Corio

#8960

I always thought using the "Erase" key cleared the current information from the queue. I'll have to be more aware of that. Sometimes takes several tries to get a station.

On the other hand, I had double-clicked his call the second time I responded to his CQ - seems like that alone should have reset the start timer?

Tnx es 73
Doc
KB3MOW

Dave 'Doc' Corio
KB3MOW

On 8/22/2015 6:00 PM, Black Michael mdblack98@... [HamApps] wrote:

Show quoted text

Click the ? to find the contact support dialog.

As for your CQ...JTAlert records the 1st time you started it. If you wanted to record the 2nd time you started you need to either double-click in JTAlert's "Time" window or click to another call and back again.

I have to admit it would be nice if the CQ reset that timer. Sounds like it would be easy to do....Laurie????

73

Mike W9MDB

From: "kb3mow@... [HamApps]"

To: HamApps@...
Sent: Saturday, August 22, 2015 4:41 PM
Subject: [HamApps] Possible Timing Bug?

In 2.6.13 I have been unable to find the "Contact Support" option!

This problem, however, is timing of contacts going into the Log (DXKeeper in this case). Here's the chronology:

20:18 Station NxABC calls CQ

20:19 I answer his CQ with a call

20:20 He calls a different station (heard them instead of me)

at this point I "Erased" the call from WSJT-X

20:33 NxABC calls CQ once again

20:34 I answer his CQ with a call

At this point, the QSO proceeds as normal, ending at 20:38, at which time I logged the contact via the prompt from JTAlert. The log entry in DXKeeper, however, shows the original time of 20:19, creating a discrepancy between our two stations regarding LoTW and EQSL.

Tnx es 73

Doc

KB3MOW

Re: Possible Timing Bug?

Michael Black

#8959

Click the ? to find the contact support dialog.

As for your CQ...JTAlert records the 1st time you started it. If you wanted to record the 2nd time you started you need to either double-click in JTAlert's "Time" window or click to another call and back again.

I have to admit it would be nice if the CQ reset that timer. Sounds like it would be easy to do....Laurie????

73

Mike W9MDB

Show quoted text

From: "kb3mow@... [HamApps]"

To: HamApps@...
Sent: Saturday, August 22, 2015 4:41 PM
Subject: [HamApps] Possible Timing Bug?

In 2.6.13 I have been unable to find the "Contact Support" option!

This problem, however, is timing of contacts going into the Log (DXKeeper in this case). Here's the chronology:

20:18 Station NxABC calls CQ

20:19 I answer his CQ with a call

20:20 He calls a different station (heard them instead of me)

at this point I "Erased" the call from WSJT-X

20:33 NxABC calls CQ once again

20:34 I answer his CQ with a call

At this point, the QSO proceeds as normal, ending at 20:38, at which time I logged the contact via the prompt from JTAlert. The log entry in DXKeeper, however, shows the original time of 20:19, creating a discrepancy between our two stations regarding LoTW and EQSL.

Tnx es 73

Doc

KB3MOW

Possible Timing Bug?

K1DJE - Dave Corio

#8958

In 2.6.13 I have been unable to find the "Contact Support" option!

This problem, however, is timing of contacts going into the Log (DXKeeper in this case). Here's the chronology:

20:18 Station NxABC calls CQ

20:19 I answer his CQ with a call

20:20 He calls a different station (heard them instead of me)

at this point I "Erased" the call from WSJT-X

20:33 NxABC calls CQ once again

20:34 I answer his CQ with a call

At this point, the QSO proceeds as normal, ending at 20:38, at which time I logged the contact via the prompt from JTAlert. The log entry in DXKeeper, however, shows the original time of 20:19, creating a discrepancy between our two stations regarding LoTW and EQSL.

Tnx es 73

Doc

KB3MOW

Re: : JTAlert Window Extended

kj4dj_dj

#8957

Tony thanks so much, I am now happy with almost the same size. Nice trick to know. Thanks agaim.

Re: Test buttons don't work in v 2.6.13

JGMAGS <jgmags2000@...>

#8956

the .wav's will still work, just get them programmed..

73, John KJ1J
"Many a good argument is ruined by some fool that knows what he is talking about"...  Marshall McLuhan...

--------------------------------------------

Show quoted text

On Sat, 8/22/15, Don AA5AU aa5au@bellsouth.net [HamApps] <HamApps@yahoogroups.com.au> wrote:

 Subject: Re: [HamApps] Test buttons don't work in v 2.6.13
 To: "HamApps@yahoogroups.com.au" <HamApps@yahoogroups.com.au>
 Date: Saturday, August 22, 2015, 11:55 AM

       Thanks Manuel.
 Perhaps this has already been posted and I missed it.
 It's a problem created by receiving too much email.
 HI
 73, Don
 AA5AU

 From:
 "YV5MM Manuel Mosquera yv5mm@yahoo.com [HamApps]"
 <HamApps@yahoogroups.com.au>
  To:
 "HamApps@yahoogroups.com.au"
 <HamApps@yahoogroups.com.au>

 Sent:
 Saturday, August 22, 2015 10:47 AM
  Subject: Re: [HamApps]
 Test buttons don't work in v 2.6.13

       Hello Don:
  I do have the same experience. I understand that  Laurie
 is going to fix this issue very soon . Best 73 de Manuel
 YV5MM 

 Manuel
 Mosquera Ramirez
 YV5MM /
 YW5M - yv5mm@amsat.org
 Asociación de
 Radioaficionados de VenezuelaP.O.
 Box 3636Caracas 1010A, D.C.yv5mm@gdxc.org

 JAMAS SUBESTIMES A TU
 PROJIMO

    From: "Don AA5AU
 aa5au@bellsouth.net [HamApps]"
 <HamApps@yahoogroups.com.au>
  To:
 "hamapps@yahoogroups.com.au"
 <hamapps@yahoogroups.com.au>

 Sent:
 Saturday, August 22, 2015 11:09 AM
  Subject: [HamApps] Test
 buttons don't work in v 2.6.13

       Just
 installed JT Alert 2.6.13 and noticed the "Test"
 buttons do not work when testing the individual alerts in
 Settings.
 I believe
 the alerts are actually working (haven't had any new
 ones come up yet), but I did activate the CQ/QRZ alert and
 it works. "Testing your soundcard" also works.
 It's only when trying to test the alerts in settings.
 The button presses, but the alert is not sounded.
 Anyone
 else experiencing this?
 73, Don
 AA5AU

 #yiv0976998398 #yiv0976998398 --
   #yiv0976998398ygrp-mkp {
 border:1px solid #d8d8d8;font-family:Arial;margin:10px
 0;padding:0 10px;}

 #yiv0976998398 #yiv0976998398ygrp-mkp hr {
 border:1px solid #d8d8d8;}

 #yiv0976998398 #yiv0976998398ygrp-mkp #yiv0976998398hd {
 color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
 0;}

 #yiv0976998398 #yiv0976998398ygrp-mkp #yiv0976998398ads {
 margin-bottom:10px;}

 #yiv0976998398 #yiv0976998398ygrp-mkp .yiv0976998398ad {
 padding:0 0;}

 #yiv0976998398 #yiv0976998398ygrp-mkp .yiv0976998398ad p {
 margin:0;}

 #yiv0976998398 #yiv0976998398ygrp-mkp .yiv0976998398ad a {
 color:#0000ff;text-decoration:none;}
 #yiv0976998398 #yiv0976998398ygrp-sponsor
 #yiv0976998398ygrp-lc {
 font-family:Arial;}

 #yiv0976998398 #yiv0976998398ygrp-sponsor
 #yiv0976998398ygrp-lc #yiv0976998398hd {
 margin:10px
 0px;font-weight:700;font-size:78%;line-height:122%;}

 #yiv0976998398 #yiv0976998398ygrp-sponsor
 #yiv0976998398ygrp-lc .yiv0976998398ad {
 margin-bottom:10px;padding:0 0;}

 #yiv0976998398 #yiv0976998398actions {
 font-family:Verdana;font-size:11px;padding:10px 0;}

 #yiv0976998398 #yiv0976998398activity {
 background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

 #yiv0976998398 #yiv0976998398activity span {
 font-weight:700;}

 #yiv0976998398 #yiv0976998398activity span:first-child {
 text-transform:uppercase;}

 #yiv0976998398 #yiv0976998398activity span a {
 color:#5085b6;text-decoration:none;}

 #yiv0976998398 #yiv0976998398activity span span {
 color:#ff7900;}

 #yiv0976998398 #yiv0976998398activity span
 .yiv0976998398underline {
 text-decoration:underline;}

 #yiv0976998398 .yiv0976998398attach {
 clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
 0;width:400px;}

 #yiv0976998398 .yiv0976998398attach div a {
 text-decoration:none;}

 #yiv0976998398 .yiv0976998398attach img {
 border:none;padding-right:5px;}

 #yiv0976998398 .yiv0976998398attach label {
 display:block;margin-bottom:5px;}

 #yiv0976998398 .yiv0976998398attach label a {
 text-decoration:none;}

 #yiv0976998398 blockquote {
 margin:0 0 0 4px;}

 #yiv0976998398 .yiv0976998398bold {
 font-family:Arial;font-size:13px;font-weight:700;}

 #yiv0976998398 .yiv0976998398bold a {
 text-decoration:none;}

 #yiv0976998398 dd.yiv0976998398last p a {
 font-family:Verdana;font-weight:700;}

 #yiv0976998398 dd.yiv0976998398last p span {
 margin-right:10px;font-family:Verdana;font-weight:700;}

 #yiv0976998398 dd.yiv0976998398last p
 span.yiv0976998398yshortcuts {
 margin-right:0;}

 #yiv0976998398 div.yiv0976998398attach-table div div a {
 text-decoration:none;}

 #yiv0976998398 div.yiv0976998398attach-table {
 width:400px;}

 #yiv0976998398 div.yiv0976998398file-title a, #yiv0976998398
 div.yiv0976998398file-title a:active, #yiv0976998398
 div.yiv0976998398file-title a:hover, #yiv0976998398
 div.yiv0976998398file-title a:visited {
 text-decoration:none;}

 #yiv0976998398 div.yiv0976998398photo-title a,
 #yiv0976998398 div.yiv0976998398photo-title a:active,
 #yiv0976998398 div.yiv0976998398photo-title a:hover,
 #yiv0976998398 div.yiv0976998398photo-title a:visited {
 text-decoration:none;}

 #yiv0976998398 div#yiv0976998398ygrp-mlmsg
 #yiv0976998398ygrp-msg p a span.yiv0976998398yshortcuts {
 font-family:Verdana;font-size:10px;font-weight:normal;}

 #yiv0976998398 .yiv0976998398green {
 color:#628c2a;}

 #yiv0976998398 .yiv0976998398MsoNormal {
 margin:0 0 0 0;}

 #yiv0976998398 o {
 font-size:0;}

 #yiv0976998398 #yiv0976998398photos div {
 float:left;width:72px;}

 #yiv0976998398 #yiv0976998398photos div div {
 border:1px solid
 #666666;height:62px;overflow:hidden;width:62px;}

 #yiv0976998398 #yiv0976998398photos div label {
 color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

 #yiv0976998398 #yiv0976998398reco-category {
 font-size:77%;}

 #yiv0976998398 #yiv0976998398reco-desc {
 font-size:77%;}

 #yiv0976998398 .yiv0976998398replbq {
 margin:4px;}

 #yiv0976998398 #yiv0976998398ygrp-actbar div a:first-child {
 margin-right:2px;padding-right:5px;}

 #yiv0976998398 #yiv0976998398ygrp-mlmsg {
 font-size:13px;font-family:Arial, helvetica, clean,
 sans-serif;}

 #yiv0976998398 #yiv0976998398ygrp-mlmsg table {
 font-size:inherit;font:100%;}

 #yiv0976998398 #yiv0976998398ygrp-mlmsg select,
 #yiv0976998398 input, #yiv0976998398 textarea {
 font:99% Arial, Helvetica, clean, sans-serif;}

 #yiv0976998398 #yiv0976998398ygrp-mlmsg pre, #yiv0976998398
 code {
 font:115% monospace;}

 #yiv0976998398 #yiv0976998398ygrp-mlmsg * {
 line-height:1.22em;}

 #yiv0976998398 #yiv0976998398ygrp-mlmsg #yiv0976998398logo {
 padding-bottom:10px;}

 #yiv0976998398 #yiv0976998398ygrp-msg p a {
 font-family:Verdana;}

 #yiv0976998398 #yiv0976998398ygrp-msg
 p#yiv0976998398attach-count span {
 color:#1E66AE;font-weight:700;}

 #yiv0976998398 #yiv0976998398ygrp-reco
 #yiv0976998398reco-head {
 color:#ff7900;font-weight:700;}

 #yiv0976998398 #yiv0976998398ygrp-reco {
 margin-bottom:20px;padding:0px;}

 #yiv0976998398 #yiv0976998398ygrp-sponsor #yiv0976998398ov
 li a {
 font-size:130%;text-decoration:none;}

 #yiv0976998398 #yiv0976998398ygrp-sponsor #yiv0976998398ov
 li {
 font-size:77%;list-style-type:square;padding:6px 0;}

 #yiv0976998398 #yiv0976998398ygrp-sponsor #yiv0976998398ov
 ul {
 margin:0;padding:0 0 0 8px;}

 #yiv0976998398 #yiv0976998398ygrp-text {
 font-family:Georgia;}

 #yiv0976998398 #yiv0976998398ygrp-text p {
 margin:0 0 1em 0;}

 #yiv0976998398 #yiv0976998398ygrp-text tt {
 font-size:120%;}

 #yiv0976998398 #yiv0976998398ygrp-vital ul li:last-child {
 border-right:none !important;
 }
 #yiv0976998398

Re: : JTAlert Window Extended

kj4dj_dj

#8955

Thank you for your responses. And yes I usually dock the JT65 window. the space between does not bother me, in fact kind of like it. But the extension is troubling. Hope there is a fix. Thanks again.

Re: Test buttons don't work in v 2.6.13

Don Hill AA5AU

#8953

Thanks Manuel. Perhaps this has already been posted and I missed it. It's a problem created by receiving too much email. HI

73, Don AA5AU

Show quoted text

From: "YV5MM Manuel Mosquera yv5mm@... [HamApps]"
To: "HamApps@..."
Sent: Saturday, August 22, 2015 10:47 AM
Subject: Re: [HamApps] Test buttons don't work in v 2.6.13

Hello Don: I do have the same experience. I understand that Laurie is going to fix this issue very soon . Best 73 de Manuel YV5MM

Manuel Mosquera Ramirez
YV5MM / YW5M - yv5mm@...
Asociación de Radioaficionados de Venezuela
P.O. Box 3636
Caracas 1010A, D.C.
yv5mm@...

JAMAS SUBESTIMES A TU PROJIMO

From: "Don AA5AU aa5au@... [HamApps]"
To: "hamapps@..." Sent: Saturday, August 22, 2015 11:09 AM
Subject: [HamApps] Test buttons don't work in v 2.6.13

Just installed JT Alert 2.6.13 and noticed the "Test" buttons do not work when testing the individual alerts in Settings.

I believe the alerts are actually working (haven't had any new ones come up yet), but I did activate the CQ/QRZ alert and it works. "Testing your soundcard" also works. It's only when trying to test the alerts in settings. The button presses, but the alert is not sounded.

Anyone else experiencing this?

73, Don AA5AU

Re: Test buttons don't work in v 2.6.13

YV5MM Manuel Mosquera

#8954

VK3AM - Laurie confirma que realmente existe un error en los botones de sonido de la última versión, que será corregida de inmediato...

I can confirm that all "Test" sound buttons on the Settings window are not working (they all share the same code routine). This only affects the 2.6.13 release.

The "Settings -> Test Sound Card" menu (JTAlert title-bar) is working correctly.

I should have a fix available later today.

Sorry for the inconvenience.
de Laurie VK3AMA

Manuel Mosquera Ramirez
YV5MM / YW5M - yv5mm@...
Asociación de Radioaficionados de Venezuela

P.O. Box 3636

Caracas 1010A, D.C.

yv5mm@...

JAMAS SUBESTIMES A TU PROJIMO

Show quoted text

From: "Don AA5AU aa5au@... [HamApps]"
To: "hamapps@..."
Sent: Saturday, August 22, 2015 11:09 AM
Subject: [HamApps] Test buttons don't work in v 2.6.13

Just installed JT Alert 2.6.13 and noticed the "Test" buttons do not work when testing the individual alerts in Settings.

I believe the alerts are actually working (haven't had any new ones come up yet), but I did activate the CQ/QRZ alert and it works. "Testing your soundcard" also works. It's only when trying to test the alerts in settings. The button presses, but the alert is not sounded.

Anyone else experiencing this?

73, Don AA5AU

Re: Test buttons don't work in v 2.6.13

YV5MM Manuel Mosquera

#8952

Hello Don: I do have the same experience. I understand that Laurie is going to fix this issue very soon . Best 73 de Manuel YV5MM

Manuel Mosquera Ramirez
YV5MM / YW5M - yv5mm@...
Asociación de Radioaficionados de Venezuela

P.O. Box 3636

Caracas 1010A, D.C.

yv5mm@...

JAMAS SUBESTIMES A TU PROJIMO

Show quoted text

From: "Don AA5AU aa5au@... [HamApps]"
To: "hamapps@..." <hamapps@...>
Sent: Saturday, August 22, 2015 11:09 AM
Subject: [HamApps] Test buttons don't work in v 2.6.13

Just installed JT Alert 2.6.13 and noticed the "Test" buttons do not work when testing the individual alerts in Settings.

I believe the alerts are actually working (haven't had any new ones come up yet), but I did activate the CQ/QRZ alert and it works. "Testing your soundcard" also works. It's only when trying to test the alerts in settings. The button presses, but the alert is not sounded.

Anyone else experiencing this?

73, Don AA5AU

Test buttons don't work in v 2.6.13

Don Hill AA5AU

#8951

Just installed JT Alert 2.6.13 and noticed the "Test" buttons do not work when testing the individual alerts in Settings.

I believe the alerts are actually working (haven't had any new ones come up yet), but I did activate the CQ/QRZ alert and it works. "Testing your soundcard" also works. It's only when trying to test the alerts in settings. The button presses, but the alert is not sounded.

Anyone else experiencing this?

73, Don AA5AU

Re: Dimension 4 clock software issue

Anton Iriawan

#8950

pse try Time-Sync

speed.soft.de

Anton - YB5QZ

Show quoted text

From: HamApps@... [mailto:HamApps@...]
Sent: 22 Agustus 2015 11:25
To: HamApps@...
Subject: Re: [HamApps] Dimension 4 clock software issue

Just adding my 2 cents here............

I found on my Win 7 systems that I needed to run D4 as administrator. Otherwise the system sometimes would not accept the time correction from D4

John - WA2HIP

On Thursday, August 20, 2015 9:26 PM, "'Patrick J. Fagan' pfagan@... [HamApps]" <HamApps@...> wrote:

Mike:

I am running Windows 10 Pro with Dimension 4. D4 does not disable the connection to Windows Time Server, at least not on my machines (I have 2 computers running D4). After reading the thread this morning I checked and Windows Time Sync was still running. After I turned it off Windows 10 Pro stated that it was not enabled.

I have not checked this out on Windows 8.1, 8.0 or 7 so I can’t speak about that. Your findings may be different. Dimension 4 is working fine here. I have my time sync set for every 5 minutes. That may be a little aggressive but so far there has not been an issue. Since using D4 I have stopped getting notices to “set my clock” when running JT65 or JT9.

Pat – WA5DVV

=====

From: mailto:HamApps@...

Sent: Thursday, August 20, 2015 6:13 AM

To: HamApps@...

Subject: Re: [HamApps] Dimension 4 clock software issue

I do believe Dimension 4 disables the windows time service itself.

So you should see that it's already disabled.

73

Mike W9MDB

Re: Dimension 4 clock software issue

John P.

#8949

Just adding my 2 cents here............

I found on my Win 7 systems that I needed to run D4 as administrator. Otherwise the system sometimes would not accept the time correction from D4

John - WA2HIP

Show quoted text

On Thursday, August 20, 2015 9:26 PM, "'Patrick J. Fagan' pfagan@... [HamApps]" wrote:

Mike:

I am running Windows 10 Pro with Dimension 4. D4 does not disable the connection to Windows Time Server, at least not on my machines (I have 2 computers running D4). After reading the thread this morning I checked and Windows Time Sync was still running. After I turned it off Windows 10 Pro stated that it was not enabled.

I have not checked this out on Windows 8.1, 8.0 or 7 so I can’t speak about that. Your findings may be different. Dimension 4 is working fine here. I have my time sync set for every 5 minutes. That may be a little aggressive but so far there has not been an issue. Since using D4 I have stopped getting notices to “set my clock” when running JT65 or JT9.

Pat – WA5DVV

=====

From: mailto:HamApps@...

Sent: Thursday, August 20, 2015 6:13 AM

To: HamApps@...

Subject: Re: [HamApps] Dimension 4 clock software issue

I do believe Dimension 4 disables the windows time service itself.

So you should see that it's already disabled.

73

Mike W9MDB

Re: JTAlert Window Extended

Laurie, VK3AMA <groups07@...>

#8948

On 22/08/2015 1:28 AM, KJ4DJ@... [HamApps] wrote:

I am running Windows 10 and JTAlert 2.6.13. I had some trouble finding the right graphics drivers initially with 10. Now most everything is OK, except that the JTAlert window extends

a couple of inches to the right of the JT65-HR window. Also the Macros and JTAlert windows are separated from the JT65-HF window by about 14 inch.

It is the JTAlert window extending way out to the right past the JT65-HF window that is a problem. Any ideas?

I am aware of the small gap between windows when docked.
Standard Window size and positioning functions that work identically from XP through to Win8 now don't. I need to rewrite the docking code, tacking into account the users OS version. It's on my todo list.

JTAlert will be wider when docked to WSJT-X, but should resize correctly to match the width of a JT65-HF window. JTAlert was written, before the narrower WSJT-X was available.

Please send me direct, not via the group, an email with a screen-capture showing your desktop with the JT65-HF and JTAlert window visible.

de Laurie VK3AMA

Confirmed Defect - JTAlert 2.6.13 Settings Test Sound buttons not working.

Laurie, VK3AMA <groups07@...>

#8947

I can confirm that all "Test" sound buttons on the Settings window are not working (they all share the same code routine). This only affects theï¿½ 2.6.13 release.

The "Settings -> Test Sound Card" menu (JTAlert title-bar) is working correctly.

I should have a fix available later today.

Sorry for the inconvenience.
de Laurie VK3AMA
ï¿½ï¿½ï¿½

Re: Need to Auto-Start a different JT65-HF program

Laurie, VK3AMA <groups07@...>

#8946

On 21/08/2015 10:32 PM, parker@... [HamApps] wrote:

I need to Auto-Start the following -

C:\Program Files (x86)\JT65HF-GUImod\JT65-HF-GUImode.exe

instead of the four (4) selections offered in the Select JT Mode Application error message.

Selecting the JT65-HF-GUImode.exe application in the Auto-Start panel does open it, but I would like to avoid the Select JT Mode Application error message every time I start JT-Alert.

Is there a way to edit the Target info in the Properties dialog for the desktop shortcut to avoid the error message?

Previously, we were able to work around the delayed start of the GUImode variant by waiting until its opening message was cleared manually (a different issue, but possibly related).

--

Parker W5ADD

Parker,

Set the shortcut target field to "/jt65hf", without the quotes, the same as the standard JT65-HF shortcut.

de Laurie VK3AMA

Re: JTAlert Window Extended

Tony Farrow

#8945

I have found the windows of some apps do appear larger with Win 10 (and also their text may appear fuzzy with a lower resolution). Someone in the DXLab group found this could be changed within the app's shortcut; see ...

http://www.dxlabsuite.com/dxlabwiki/PreventReducedResolution

Cheers,

Tony VK2AJF

Show quoted text

On Saturday, August 22, 2015, KJ4DJ@... [HamApps] <HamApps@...> wrote:

I am running Windows 10 and JTAlert 2.6.13. I had some trouble finding the right graphics drivers initially with 10. Now most everything is OK, except that the JTAlert window extends
a couple of inches to the right of the JT65-HR window. Also the Macros and JTAlert windows are separated from the JT65-HF window by about 14 inch.

It is the JTAlert window extending way out to the right past the JT65-HF window that is a problem. Any ideas?

--
Sent from Gmail Mobile

Re: Contact Support

Jim N6VH

#8944

Click on the "?". The bottom option is "Contact Support"

73,

Jim N6VH

Show quoted text

On 8/21/2015 1:34 PM, jgmags2000@yahoo.com [HamApps] wrote:
Hello Group,
  I  noticed that  the latest version has no Contact Support tab,,

kj1j

Re: Sound

Kevin Utzy

#8943

All,
Yes.  The sounds work, just not the test.