Date   

locked Logging to DXKeeper

Larry Bryan
 

Laurie,

I just downloaded WSJTx 1.9.1 and was working some stations using HamApps 2.11.1. Had 3 Q's and each one failed to log to DXKeeper. It's been working fine and I'm not sure what downloading 1.9.1 has to do with this. I was using 1.9.0 prior and things were fine.

Larry
W8LIG


locked Re: V11.1.1 Fails to load

HamApps Support (VK3AMA)
 

On 4/06/2018 1:32 AM, Gilbert Baron wrote:

There would be fewer problems of this type if the application were not put in ProgramFiles nor ProgramFiles(X86).  Using these causes many problems for many apps. As an example DXLABS runs in its own directory as the top of the tree and never has such a problem.

This has nothing to do with installing to the Windows protected Programs Files directories. Installing to those directories is perfectly valid (and recommended by Microsoft) if the application is written correctly to not create/modify/delete files or folders in its install directory. JTAlert follows these guidelines and is quite happy to be installed there.

Installing outside the Program Files directories is needed by some older applications (like DXLab) that were created during the XP era when these security restrictions (first introduced with Vista) were not part of the Windows OS. S
ome badly written modern applications (I wont name them) also need to be installed outside those directories. Plus there are the special cases where an application is designed correctly but has the ability to write to its own directories if instructed to by the user, this is typically done to create portable installations of a program.

de Laurie VK3AMA
 


locked Re: new version of JT Alert throws error when writing to AC Log 6.2

HamApps Support (VK3AMA)
 

On 4/06/2018 12:04 AM, z_ kevino wrote:
I sent the support logs to the support email. What I notice is that JT Alert is able to fill the files in AC Log during the contact via the API. However, when I go to log the file, it throws the error that it could not confirm the QSO logging, but that it is still in WSJT-X log (which it is). 
Checked, and AC Log is not running as Admin, and also the JT Alert settings picked up the path correctly to the .mdb file. Worked with previous version of JT Alert. 
Any other ideas while I wait for Laurie or his support team to examine the logs?
thanks,
-Kevin (KK4YEL) 
Kevin,

This may be related to the HRD logging problem experienced by some users. You will need to resend the support request. Please do the following...

Do the following...
  1. Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  2. Restart JTAlert, that is close JTAlert and then start JTAlert.
  3. Operate as normal.
  4. Once a Logging failure occurs send the support request.
  5. Leave the "Enable Debug Recording" menu enabled.
  6. Once a solution is found for your problem you can turn off debugging.
 de Laurie VK3AMA


locked #Important #HRD Logging Failure Support Requests & JTAlert 2.11.1 #Important #HRD

HamApps Support (VK3AMA)
 

For those who are sending support requests for the intermittent HRD logging failure of JTAlert 2.11.1 it is important that you enable debug recording in JTAlert otherwise there is no data for me to examine.

Do the following...

  1. Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  2. Restart JTAlert, that is close JTAlert and then start JTAlert.
  3. Operate as normal.
  4. Once a HRD Logging failure occurs send the support request.
  5. Leave the "Enable Debug Recording" menu enabled.
  6. Once a solution is found for your problem you can turn off debugging.
 de Laurie VK3AMA


locked Re: V11.1.1 Fails to load

Michael Black
 

Where do you get that idea from?  The problem he had simply because something was still running and a reboot fixed the problem (or you could've found it via task manager and killed it).
Same thing would've happened no matter where it was installed.

de Mike W9MDB




On Sunday, June 3, 2018, 10:32:50 AM CDT, Gilbert Baron <w0mn00@...> wrote:


There would be fewer problems of this type if the application were not put in ProgramFiles nor ProgramFiles(X86).  Using these causes many problems for many apps. As an example DXLABS runs in its own directory as the top of the tree and never has such a problem.

 

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Ron W3RJW
Sent: Sunday, June 3, 2018 07:45
To: Support@HamApps.groups.io
Subject: [HamApps] V11.1.1 Fails to load

 

Win 8.1   v2.11.1 fails during setup ..  Downloaded new copy and reran with same results ... 


--
73
Ron, W3RJW


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: New JTAlert 2.11.1 Available

Jim - N4ST
 

Thanks for the update Laurie.

All running fine here.

 

WSJT-X ver 1.9.1

JTAlert ver 2.11.1

HRD ver 6.4.0.840

Windows 10 Home ver 1803

 

_____________

73,

Jim – N4ST


locked Re: V11.1.1 Fails to load

KQ8M
 

That’s why I install all of my apps elsewhere unless forced to. I have JTAlert installed elsewhere. Eazy peazy.

 

73

Tim, KQ8M

kq8m@kq8m.com

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Gilbert Baron
Sent: Sunday, June 3, 2018 11:33
To: Support@HamApps.groups.io
Subject: Re: [HamApps] V11.1.1 Fails to load

 

There would be fewer problems of this type if the application were not put in ProgramFiles nor ProgramFiles(X86).  Using these causes many problems for many apps. As an example DXLABS runs in its own directory as the top of the tree and never has such a problem.

 

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Ron W3RJW
Sent: Sunday, June 3, 2018 07:45
To: Support@HamApps.groups.io
Subject: [HamApps] V11.1.1 Fails to load

 

Win 8.1   v2.11.1 fails during setup ..  Downloaded new copy and reran with same results ... 


--
73
Ron, W3RJW


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: Time info, Log ADIF and list for chat?

g4wjs
 

On 03/06/2018 16:49, Franco Borsa [HB9oab] wrote:
I have the impression that this "timout delete" comes from frequency CAT commands that are passed on UDP traffic, that when something changes on the WSJTx CAT for example the frequency, JTalert receives a UDP that causes the "monitor" to reset to zero . But this is not always the case when I use VSPE above all this problem, however not always, I can not monitor UDP traffic but I think it depends on this.

Hi Franco,

dumb serial port splitters like VSPE are not supported with WSJT-X as reliable CAT control is not possible using them.

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: JTAlert 2.11.1 Fails install

 

You just reminded me of another symptom.  No new icons/shortcuts were produced during my install attempts.  FYI Win10 x64, new i7 machine with 32GB RAM and plenty of disk space so whatever the problem is, a shortage of resources is not it.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of David Michael Gaytko // WD4KPD
Sent: Sunday, June 3, 2018 10:22 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.11.1 Fails install

 

just a note...

v2.11.1 installed with no hits/runs/errors.  right over top of previous version.

when new icons created, just moved them and replaced the previous ones in my wsjt folder.

setup is win10/1803

david/wd4kpd

 

 

On 6/3/2018 2:48 PM, Dan Malcolm wrote:

I have read the other reports of JTAlert 2.11.1 showing errors during install.  When I install 2.11.1, I don’t receive any errors.  However if I try to use the existing shortcut to start JTAlert, I get an error saying that the shortcut is invalid.  Looking at the install folder, I see JTAlert.exe with the musical note icon instead of the “X” icon (I selected only the WSJT-X install).  If I double click that, the file seems to delete itself. 

 

I have tried this 5 time with the same results, and both before and after a reboot.  I have also re-downloaded the new JTAlert to no avail.

 

I am quite sure that Laurie will sort this out in short order, but in the meantime I will stick with 2.10.17.

__________

Dan – K4SHQ

 


--
Dan - K4SHQ

 


--
Dan - K4SHQ


locked Re: Time info, Log ADIF and list for chat?

Frank
 

HI Laurie
thanks fast reply
>>PCs that don't have enough CPU
I do not think this since I have WIN10pro with I7 + 32GB ram and there are no problems of delays as with win10pro and this CPU I could not expect more on the speed of the PC.

The use of the CPU is at 2% with these active things, checking it on the CPU activity function decode that reaches at most 10% ...
Everything else is Decode Depth by default, having never touched anything in particular. However, it is a problem that has existed for a long time even on previous versions.

I have the impression that this "timout delete" comes from frequency CAT commands that are passed on UDP traffic, that when something changes on the WSJTx CAT for example the frequency, JTalert receives a UDP that causes the "monitor" to reset to zero . But this is not always the case when I use VSPE above all this problem, however not always, I can not monitor UDP traffic but I think it depends on this.

Could it be possible to verify this?
When WSJT CAT swerves on the monitor frequency (then I can also explain why...), JTalert resets the call monitor list in advance.
I checked it only now having opened the two windows nearby. Which were previously on different monitors (I use 4 monitors).
It's only because sometimes VSPE sends me "fake" one of my apps that seems to change the frequency and wsjt receives this change on his monitor cat frequency that sends it in red for half a second and then come back just right.
VSPE interacts perfectly but this anomaly, of which I know the cause, while JTalert, resets the callsign monitor ....
You can try it by switching from VFO A to VFO B during the slot.
is my Home Made application that changes the qrg, and I'm trying to AUTO ALC: this puts me to zero via CAT automatically the ALC in transmission even when I change the audio frequency, always leaving a clean transmission and I'm verifying right now that the this is a problem.

73's
Franco, HB9oab




locked Re: 2.11.1 Fails to Log to HRD Logbook

Brad Penn
 

Interesting...I'm running the same versions as you, but have the logging problem.

73
Brad
KD5ZAT


locked Re: V11.1.1 Fails to load

Gilbert Baron <w0mn00@...>
 

There would be fewer problems of this type if the application were not put in ProgramFiles nor ProgramFiles(X86).  Using these causes many problems for many apps. As an example DXLABS runs in its own directory as the top of the tree and never has such a problem.

 

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Ron W3RJW
Sent: Sunday, June 3, 2018 07:45
To: Support@HamApps.groups.io
Subject: [HamApps] V11.1.1 Fails to load

 

Win 8.1   v2.11.1 fails during setup ..  Downloaded new copy and reran with same results ... 


--
73
Ron, W3RJW


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: JTAlert 2.11.1 Fails install

David Michael Gaytko // WD4KPD
 

just a note...

v2.11.1 installed with no hits/runs/errors.  right over top of previous version.

when new icons created, just moved them and replaced the previous ones in my wsjt folder.

setup is win10/1803

david/wd4kpd



On 6/3/2018 2:48 PM, Dan Malcolm wrote:

I have read the other reports of JTAlert 2.11.1 showing errors during install.  When I install 2.11.1, I don’t receive any errors.  However if I try to use the existing shortcut to start JTAlert, I get an error saying that the shortcut is invalid.  Looking at the install folder, I see JTAlert.exe with the musical note icon instead of the “X” icon (I selected only the WSJT-X install).  If I double click that, the file seems to delete itself. 

 

I have tried this 5 time with the same results, and both before and after a reboot.  I have also re-downloaded the new JTAlert to no avail.

 

I am quite sure that Laurie will sort this out in short order, but in the meantime I will stick with 2.10.17.

__________

Dan – K4SHQ

 


--
Dan - K4SHQ


locked JTAlert 2.11.1 Fails install

 

I have read the other reports of JTAlert 2.11.1 showing errors during install.  When I install 2.11.1, I don’t receive any errors.  However if I try to use the existing shortcut to start JTAlert, I get an error saying that the shortcut is invalid.  Looking at the install folder, I see JTAlert.exe with the musical note icon instead of the “X” icon (I selected only the WSJT-X install).  If I double click that, the file seems to delete itself. 

 

I have tried this 5 time with the same results, and both before and after a reboot.  I have also re-downloaded the new JTAlert to no avail.

 

I am quite sure that Laurie will sort this out in short order, but in the meantime I will stick with 2.10.17.

__________

Dan – K4SHQ

 


--
Dan - K4SHQ


locked new version of JT Alert throws error when writing to AC Log 6.2

z_ kevino
 

I sent the support logs to the support email. What I notice is that JT Alert is able to fill the files in AC Log during the contact via the API. However, when I go to log the file, it throws the error that it could not confirm the QSO logging, but that it is still in WSJT-X log (which it is). 
Checked, and AC Log is not running as Admin, and also the JT Alert settings picked up the path correctly to the .mdb file. Worked with previous version of JT Alert. 
Any other ideas while I wait for Laurie or his support team to examine the logs?
thanks,
-Kevin (KK4YEL) 


locked Re: 2.11.1 Fails to Log to HRD Logbook

Rick Johnson
 

My problem is JTA won't log to DXK on the first 2 attempts.
I must click Log QSO, acknowledge it failed to log to DXK twice and then on the third attempt it acknowledges logging.
Then I must go to QRZ.com and remove 2 of the entries. Reboot and cold start don't help.
73, Rick W3BI


On Sun, Jun 3, 2018 at 9:41 AM, Rick Johnson <w3bi.rick@...> wrote:
Reboot doesn't help.
W3BI

On Sun, Jun 3, 2018 at 9:16 AM, Morris WA4MIT via Groups.Io <wa4mit@...> wrote:
Having the same no logging issue here now along with the delay issue what next? I enabled debugging and sent a report hope it helps 
73 Morris wa4mit




locked Re: 2.11.1 Fails to Log to HRD Logbook

Rick Johnson
 

Reboot doesn't help.
W3BI

On Sun, Jun 3, 2018 at 9:16 AM, Morris WA4MIT via Groups.Io <wa4mit@...> wrote:
Having the same no logging issue here now along with the delay issue what next? I enabled debugging and sent a report hope it helps 
73 Morris wa4mit



locked Re: 2.11.1 Fails to Log to HRD Logbook

Ron W3RJW
 

Another data point: Using HRD v6.4.0.840, WSJT-X v1.9.0 and newly installed JTAlertX v 2.11.1 ....   JTAlert logs to HRD like always ...
--
73
Ron, W3RJW


locked Re: 2.11.1 Fails to Log to HRD Logbook

Rick Johnson
 

I find the same. I need to Log QSO 3 times before it will log to DXK. 
Then go to QRZ.com and delete 2 of them.
73,
Rick W3BI


On Sun, Jun 3, 2018 at 9:09 AM, on5po <on5po@...> wrote:
<br class="Apple-interchange-newline"><div></div>
112/5000
hello, for info,
With the latest version jtalert, "send date eqslcc, no longer fits, in the log of HRD





De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Envoyé : dimanche 3 juin 2018 14:22
À : Support@HamApps.groups.io
Objet : Re: [HamApps] 2.11.1 Fails to Log to HRD Logbook
 
On 3/06/2018 10:03 PM, Michael Black via Groups.Io wrote:
Laurie, is the HRD logging a single TCP packet?

I've been trying to write a hamlib back-end for HRD rig control and I've found throwing multiple packets at it (like is needed for WSJT-X split mode) causes TCP reset problems with HRD (done the same thing with FLRig and TRXManager without such problems).  Still trying to figure out the sleeps needed or identify enough to create a bug report for HRD.

de Mike W9MDB
Mike,

JTAlert sends a single TCP packet, this hasn't changed for a couple of years now and there is definitely no HRD changes in this build of JTAlert.

I don't believe it is a packet data length issue as the HRDLogbook.trace file has a 680 character command logging correctly while a 649 character packet failed (no response for HRDLogbook).

de Laurie VK3AMA




locked Re: 2.11.1 Fails to Log to HRD Logbook

Morris WA4MIT
 

Having the same no logging issue here now along with the delay issue what next? I enabled debugging and sent a report hope it helps 
73 Morris wa4mit

16801 - 16820 of 36983