Date   

locked Re: Logging time excessive

Laurie, VK3AMA <groups08@...>
 

Dwight,

Now that I have had my first coffee for the day, I have some other questions/comments.

Do you have DXKeeper set to auto upload to eQSL and Clublog, if so, try disabling those temporarily to see if the response time improves?

DXKeeper, because it uses an Access file, will benefit from running a Compact (DXKeeper Config, Log Tab).

de Laurie VK3AMA
   

On 12/03/2016 9:14 AM, 'DGB' ns9i2016@... [HamApps] wrote:
Tnx Laurie

I am defragging right now and it needed it.

It happens on all logged qso's and does it after a fresh reboot as well.

I  frequently do good housekeeping, cleaning the registry etc. but defragging has completely skipped my mind as all my other pc's have SS drives. ;= )

We'll see, tnx agn 73 Dwight NS9I


locked Re: Logging time excessive

'DGB' <ns9i2016@...>
 

Tnx Laurie

I am defragging right now and it needed it.

It happens on all logged qso's and does it after a fresh reboot as well.

I  frequently do good housekeeping, cleaning the registry etc. but defragging has completely skipped my mind as all my other pc's have SS drives. ;= )

We'll see, tnx agn 73 Dwight NS9I

On 3/11/2016 4:07 PM, 'Laurie, VK3AMA' groups08@... [HamApps] wrote:
 

Dwight,

Does this happen for all logged QSOs, or does it vary?

Does this delay persist after a reboot of your PC?

I might be able to discover something by examining your session files. Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Include a note of the UTC Time and Date of a logging time that was excessive.

de Laurie VK3AMA
   


On 12/03/2016 12:30 AM, 'DGB' ns9i2016@... [HamApps] wrote:
Recently it has taken longer and longer for my Q to be logged to DXK,
almost 2 minutes now.

Am running Win 8.1 with I5 processor in a HP 8540p laptop with 6gb of ram.

What could be causing this? I keep all the apps up to date.

Only virus/malware sftwe is MS Windows Defender.

73 Dwight NS9I



locked Re: Logging time excessive

Laurie, VK3AMA <groups08@...>
 

Dwight,

Does this happen for all logged QSOs, or does it vary?

Does this delay persist after a reboot of your PC?

I might be able to discover something by examining your session files. Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Include a note of the UTC Time and Date of a logging time that was excessive.

de Laurie VK3AMA
   


On 12/03/2016 12:30 AM, 'DGB' ns9i2016@... [HamApps] wrote:
Recently it has taken longer and longer for my Q to be logged to DXK,
almost 2 minutes now.

Am running Win 8.1 with I5 processor in a HP 8540p laptop with 6gb of ram.

What could be causing this? I keep all the apps up to date.

Only virus/malware sftwe is MS Windows Defender.

73 Dwight NS9I


locked Re: : Re: Is logging to HRD v6 Database fixed?

Laurie, VK3AMA <groups08@...>
 

Dan,

Writing direct to the HRD Log using the ODBC DSN is the old technique (now used only for HRD V5 and pre V6.3) for logging and is not used with HRD  6.3+

de Laurie VK3AMA
   


On 12/03/2016 12:34 AM, 'Dan Malcolm' dmalcolm24@... [HamApps] wrote:

One additional point.  JTAlert posts to the HRD Logbook through an ODBC connection to the data file (which is a Microsoft Access file).  ODBC doesn’t need the HRD Logbook to be running to post QSO’s to the logbook.  I run HRD Logbook so I can add QRZ data plus my station data, before uploading to eQSL & LoTW.

 

_____________________________

Dan Malcolm CFI/II

K4SHQ



locked Re: : Re: Is logging to HRD v6 Database fixed?

Laurie, VK3AMA <groups08@...>
 

Neal,

WSJT-X needs to be running first, if not, JTAlert will pause and display a waiting message.
HRDLogbook can be started anytime, it needs to be running for JTAlert logging to HRD to work as the new API uses TCP to communicate.

One thing I neglected to mention regarding the logging setup, the ODBC DSN for your HRD Log needs to be set as JTAlert uses that to read the HRD Log to confirm the QSO was written (the result message from the API are unreliable so JTAlert reads the log directly)

de Laurie VK3AMA
   

On 11/03/2016 4:45 PM, nealix@... [HamApps] wrote:
OK, that is very good.   I am running JT-Alert ver 2.6.30 and HRD 6.3.0.483.

Question, since I can't find a user manual for JT-Alert.   Once I configure JT-Alert to use
the HRD logbook, what is the sequence of programs to start?  In other words;
Do I start WSJT-X, then HRD Logbook, and then JT-Alert?   Or do I need to start the full
Ham Radio Deluxe main program (as opposed to just directly starting the logbook app)?

Thanks,

Neal


locked Re: Logging time excessive

Jim Hertel <n6kmr@...>
 

Might want to try defraging and disk clean up for a starter. simple windows stuff and also lately the updates have been coming in too that usually slows mine down a bit.

On 3/11/2016 6:09 AM, Black Michael mdblack98@... [HamApps] wrote:
 
Try excluding that directory from Windows Defender.  You can do that in the settings.

I've noticed a similar thing with Log4OM where, once in a while, it will take more than a minute to log a QSO with lots of disk chatter.

Is your delay happening on every QSO?

So I've excluded that dir now from Windows Defender and hopefully that problem goes away.

RRR
Mike W9MDB



From: "'DGB' ns9i2016@... [HamApps]"
To: HamApps@...
Sent: Friday, March 11, 2016 7:30 AM
Subject: [HamApps] Logging time excessive

 
Recently it has taken longer and longer for my Q to be logged to DXK,
almost 2 minutes now.

Am running Win 8.1 with I5 processor in a HP 8540p laptop with 6gb of ram.

What could be causing this? I keep all the apps up to date.

Only virus/malware sftwe is MS Windows Defender.

73 Dwight NS9I





locked Re: Logging time excessive

Michael Black
 

Try excluding that directory from Windows Defender.  You can do that in the settings.

I've noticed a similar thing with Log4OM where, once in a while, it will take more than a minute to log a QSO with lots of disk chatter.

Is your delay happening on every QSO?

So I've excluded that dir now from Windows Defender and hopefully that problem goes away.

RRR
Mike W9MDB



From: "'DGB' ns9i2016@... [HamApps]"
To: HamApps@...
Sent: Friday, March 11, 2016 7:30 AM
Subject: [HamApps] Logging time excessive

 
Recently it has taken longer and longer for my Q to be logged to DXK,
almost 2 minutes now.

Am running Win 8.1 with I5 processor in a HP 8540p laptop with 6gb of ram.

What could be causing this? I keep all the apps up to date.

Only virus/malware sftwe is MS Windows Defender.

73 Dwight NS9I




locked Re: : Re: Is logging to HRD v6 Database fixed?

Dan Malcolm <dmalcolm24@...>
 

Neal,

One additional point.  JTAlert posts to the HRD Logbook through an ODBC connection to the data file (which is a Microsoft Access file).  ODBC doesn’t need the HRD Logbook to be running to post QSO’s to the logbook.  I run HRD Logbook so I can add QRZ data plus my station data, before uploading to eQSL & LoTW.

 

_____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Friday, March 11, 2016 6:25 AM
To: HamApps@...
Subject: RE: : Re: [HamApps] Is logging to HRD v6 Database fixed?

 

 

Neal,

I have a similar setup.  I don’t need HRD to interface with my rig, but I do use HRD Logbook.  The only program I need started first is WSJT-X.  After that starts I use JTAlert to start HRD Logbook.  So my sequence including a rig interface program is:

1.       OpenHPSDR

2.       WSJT-X

3.       JTAlert -> HRD Logbook

Item 1 is the interface to my Apache ANAN 100D.

_____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, March 10, 2016 11:46 PM
To: HamApps@...
Subject: Re:: Re: [HamApps] Is logging to HRD v6 Database fixed?

 

 

OK, that is very good.   I am running JT-Alert ver 2.6.30 and HRD 6.3.0.483.

Question, since I can't find a user manual for JT-Alert.   Once I configure JT-Alert to use
the HRD logbook, what is the sequence of programs to start?  In other words;
Do I start WSJT-X, then HRD Logbook, and then JT-Alert?   Or do I need to start the full
Ham Radio Deluxe main program (as opposed to just directly starting the logbook app)?

Thanks,

Neal


locked Logging time excessive

'DGB' <ns9i2016@...>
 

Recently it has taken longer and longer for my Q to be logged to DXK, almost 2 minutes now.

Am running Win 8.1 with I5 processor in a HP 8540p laptop with 6gb of ram.

What could be causing this? I keep all the apps up to date.

Only virus/malware sftwe is MS Windows Defender.

73 Dwight NS9I


locked Re: : Re: Is logging to HRD v6 Database fixed?

chas cartmel
 

I have wsjt_x in the autostart section of JT Alert settings. I only start HRD logbook when I want to add in QRZ and station info, usually at the end of an operating session.

WSJT-X has direct CAT control so no need for HRD interface.

 

73

Charlie

www.G4EST.me.uk

Twitter:@ccartmel

 

From: HamApps@... [mailto:HamApps@...]
Sent: 11 March 2016 12:25
To: HamApps@...
Subject: RE: : Re: [HamApps] Is logging to HRD v6 Database fixed?

 

 

Neal,

I have a similar setup.  I don’t need HRD to interface with my rig, but I do use HRD Logbook.  The only program I need started first is WSJT-X.  After that starts I use JTAlert to start HRD Logbook.  So my sequence including a rig interface program is:

1.       OpenHPSDR

2.       WSJT-X

3.       JTAlert -> HRD Logbook

Item 1 is the interface to my Apache ANAN 100D.

_____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, March 10, 2016 11:46 PM
To: HamApps@...
Subject: Re:: Re: [HamApps] Is logging to HRD v6 Database fixed?

 

 

OK, that is very good.   I am running JT-Alert ver 2.6.30 and HRD 6.3.0.483.

Question, since I can't find a user manual for JT-Alert.   Once I configure JT-Alert to use
the HRD logbook, what is the sequence of programs to start?  In other words;
Do I start WSJT-X, then HRD Logbook, and then JT-Alert?   Or do I need to start the full
Ham Radio Deluxe main program (as opposed to just directly starting the logbook app)?

Thanks,

Neal

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7442 / Virus Database: 4540/11793 - Release Date: 03/11/16


locked Re: : Re: Is logging to HRD v6 Database fixed?

Dan Malcolm <dmalcolm24@...>
 

Neal,

I have a similar setup.  I don’t need HRD to interface with my rig, but I do use HRD Logbook.  The only program I need started first is WSJT-X.  After that starts I use JTAlert to start HRD Logbook.  So my sequence including a rig interface program is:

1.       OpenHPSDR

2.       WSJT-X

3.       JTAlert -> HRD Logbook

Item 1 is the interface to my Apache ANAN 100D.

_____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, March 10, 2016 11:46 PM
To: HamApps@...
Subject: Re:: Re: [HamApps] Is logging to HRD v6 Database fixed?

 

 

OK, that is very good.   I am running JT-Alert ver 2.6.30 and HRD 6.3.0.483.

Question, since I can't find a user manual for JT-Alert.   Once I configure JT-Alert to use
the HRD logbook, what is the sequence of programs to start?  In other words;
Do I start WSJT-X, then HRD Logbook, and then JT-Alert?   Or do I need to start the full
Ham Radio Deluxe main program (as opposed to just directly starting the logbook app)?

Thanks,

Neal


locked Re: : Re: Is logging to HRD v6 Database fixed?

Neal Pollack
 

OK, that is very good.   I am running JT-Alert ver 2.6.30 and HRD 6.3.0.483.

Question, since I can't find a user manual for JT-Alert.   Once I configure JT-Alert to use
the HRD logbook, what is the sequence of programs to start?  In other words;
Do I start WSJT-X, then HRD Logbook, and then JT-Alert?   Or do I need to start the full
Ham Radio Deluxe main program (as opposed to just directly starting the logbook app)?

Thanks,

Neal


locked Re: Is logging to HRD v6 Database fixed?

Laurie, VK3AMA <groups08@...>
 

Neal,

The history of the HRD API and HRD deleting any running JTAlert process on the users PC is available in the message archives of this group. I wont rehash the true details, except to say that JTAlert was coded to support the HRD Logging API within a couple of hours of the spec being finally made available to me.

The API is used automatically by JTAlert when HRD 6.3+ is detected. You will need visit the JTAlert Settings and set the Log name and the IP address of the PC running HRDLogbook (typically 127.0.0.1 if on the same PC as JTAlert).

NOTE: There is an outstanding defect within the API affecting non-Access (MySQL, MSSQL) logs where the API will report back to JTAlert that a QSO was written to the HRDLogbook Log but it is never actually written. This only affects non-Access logs where there is no configured Access log within HRDLogbook. The workaround is to create a dummy Access log in HRDLogbook.

de Laurie VK3AMA
   


On 11/03/2016 2:58 AM, nealix@... [HamApps] wrote:
Hi Laurie:

When I discovered JTalert and was originally searching for JTalert setup tutorials,
I noticed a number of people reporting that JTalert is not programmed to properly use the HRD database
API (Application Programming Interface) [but instead directly writes to the DB, bypassing the HRD API], and therefore occasionally corrupts the HRD logging database.
 
HRD staff claimed to be aware of this, and said they tried to explain to the author of JTalert how he should fix JTalert to use the HRD API for database writes.   The suggestions from HRD support are to avoid permitting JTalert to directly write to your HRD log database until JTalert fixes their programming.

So for right now, for safety, I am just importing the ADIF log file once a day (if I operate).

My Question:   I imagine some time has gone by.   Has the JTalert code been updated yet to
safely use the HRD database API, so I can turn on direct logging without fearing corruption of
the HRD log database?

I love your program.   Thanks for making such a great helper-app with so many features.

Cheers,

Neal
N6YFM


locked Is logging to HRD v6 Database fixed?

Neal Pollack
 

Hi Laurie:

When I discovered JTalert and was originally searching for JTalert setup tutorials,
I noticed a number of people reporting that JTalert is not programmed to properly use the HRD database
API (Application Programming Interface) [but instead directly writes to the DB, bypassing the HRD API], and therefore occasionally corrupts the HRD logging database.
 
HRD staff claimed to be aware of this, and said they tried to explain to the author of JTalert how he should fix JTalert to use the HRD API for database writes.   The suggestions from HRD support are to avoid permitting JTalert to directly write to your HRD log database until JTalert fixes their programming.

So for right now, for safety, I am just importing the ADIF log file once a day (if I operate).

My Question:   I imagine some time has gone by.   Has the JTalert code been updated yet to
safely use the HRD database API, so I can turn on direct logging without fearing corruption of
the HRD log database?

I love your program.   Thanks for making such a great helper-app with so many features.

Cheers,

Neal
N6YFM



locked Re: Logging from WSJT-X into DXKeeper

Joe Subich, W4TV
 

Nick,

Are you using Windows 10? If so are you using insider preview
versions of Windows 10?

73,

... Joe, W4TV

On 3/8/2016 9:41 AM, Nick Maslon - K1MAZ k1maz@... [HamApps] wrote:
Hi Laurie,

I've tried running everything normally and as administrator and the DDE
test fails both ways. Do you have any other suggestions on what to try?

Thanks,
Nick K1MAZ

On Tue, Mar 8, 2016 at 2:38 AM, 'Laurie, VK3AMA' groups08@...
[HamApps] <HamApps@...> wrote:



Nick,

Sounds like DDE communications between JTAlert and DXKeeper is not
working. You can check that by opening the Settings window, "Applications
-> DXLab Suite -> Test" section.

The usual cause is running DXKeeper with elevated privileges (set to Run
As Administrator) or Launcher is elevated and it starting DXKeeper will
automatically elevate DXKeeper. The Windows security model prevents
processes running different privilege levels from communicating. There is
no reason to run DXKeeper elevated provided it is installed outside the Windows
protected "Program Files.." directory trees as recommended by the DXLab
author.

de Laurie VK3AMA


On 8/03/2016 1:14 PM, k1maz@... [HamApps] wrote:

Hello,

I'm trying to log from WSJT-X into DXKeeper through JTAlert, but I keep
getting this error message: http://imgur.com/XXBxulf . JTAlert appears
to be decoding from WSJT-X and reading DXKeeper's log (it shows QSO B4 in
the bar) but it can't write to the log. DXKeeper is open. Any help would
be greatly appreciated.

Thank you,
Nick K1MAZ




locked Re: Logging from WSJT-X into DXKeeper

Nick Maslon - K1MAZ <k1maz@...>
 

Hi Laurie,

I've tried running everything normally and as administrator and the DDE test fails both ways.  Do you have any other suggestions on what to try?

Thanks,
Nick K1MAZ

On Tue, Mar 8, 2016 at 2:38 AM, 'Laurie, VK3AMA' groups08@... [HamApps] <HamApps@...> wrote:
 

Nick,

Sounds like DDE communications between JTAlert and DXKeeper is not working. You can check that by opening the Settings window, "Applications -> DXLab Suite -> Test" section.

The usual cause is running DXKeeper with elevated privileges (set to Run As Administrator) or Launcher is elevated and it starting DXKeeper will automatically elevate DXKeeper. The Windows security model prevents processes running different privilege levels from communicating. There is no reason to run DXKeeper elevated provided it is installed outside the Windows protected "Program Files.." directory trees as recommended by the DXLab author.

de Laurie VK3AMA
    


On 8/03/2016 1:14 PM, k1maz@... [HamApps] wrote:
Hello,

I'm trying to log from WSJT-X into DXKeeper through JTAlert, but I keep getting this error message: http://imgur.com/XXBxulf .  JTAlert appears to be decoding from WSJT-X and reading DXKeeper's log (it shows QSO B4 in the bar) but it can't write to the log.  DXKeeper is open.  Any help would be greatly appreciated.

Thank you,
Nick K1MAZ



locked Re: JT Alert not alerting on states

Juliean Galak
 

Aha!  That was it.  Thanks!

Juliean KQ2Z 

Sent from my iPad

On Mar 8, 2016, at 2:32 AM, 'Laurie, VK3AMA' groups08@... [HamApps] <HamApps@...> wrote:

 

Juliean,

For US State alerting, JTAlert needs to know to which State a Station belongs. This is accomplished by installing the Callsign Database (see the HamApps.com)
This database provides State data for US Callsigns and LoTW/eQSL(AG) membership data for International Stations.

de Laurie VK3AMA
   

On 8/03/2016 4:44 PM, jgalak@... [HamApps] wrote:
Greetings!

I started usng JT Alert a few days ago (version 2.6.30) with WSJT-X and absolutely love it.  Just one problem though - while it alerts on DXCC entities and continents just fine, it doesn't seem to alert on states.  I have it set to alert on about a dozen states on all bands/all modes, but it doesn't highlight any.  I've manually spotted states on the want list at least twice.

Any ideas?

Thanks,
Juliean KQ2Z


locked Re: Logging from WSJT-X into DXKeeper

Laurie, VK3AMA <groups08@...>
 

Nick,

Sounds like DDE communications between JTAlert and DXKeeper is not working. You can check that by opening the Settings window, "Applications -> DXLab Suite -> Test" section.

The usual cause is running DXKeeper with elevated privileges (set to Run As Administrator) or Launcher is elevated and it starting DXKeeper will automatically elevate DXKeeper. The Windows security model prevents processes running different privilege levels from communicating. There is no reason to run DXKeeper elevated provided it is installed outside the Windows protected "Program Files.." directory trees as recommended by the DXLab author.

de Laurie VK3AMA
    


On 8/03/2016 1:14 PM, k1maz@... [HamApps] wrote:
Hello,

I'm trying to log from WSJT-X into DXKeeper through JTAlert, but I keep getting this error message: http://imgur.com/XXBxulf .  JTAlert appears to be decoding from WSJT-X and reading DXKeeper's log (it shows QSO B4 in the bar) but it can't write to the log.  DXKeeper is open.  Any help would be greatly appreciated.

Thank you,
Nick K1MAZ


locked Re: JT Alert not alerting on states

Laurie, VK3AMA <groups08@...>
 

Juliean,

For US State alerting, JTAlert needs to know to which State a Station belongs. This is accomplished by installing the Callsign Database (see the HamApps.com)
This database provides State data for US Callsigns and LoTW/eQSL(AG) membership data for International Stations.

de Laurie VK3AMA
   

On 8/03/2016 4:44 PM, jgalak@... [HamApps] wrote:
Greetings!

I started usng JT Alert a few days ago (version 2.6.30) with WSJT-X and absolutely love it.  Just one problem though - while it alerts on DXCC entities and continents just fine, it doesn't seem to alert on states.  I have it set to alert on about a dozen states on all bands/all modes, but it doesn't highlight any.  I've manually spotted states on the want list at least twice.

Any ideas?

Thanks,
Juliean KQ2Z


locked JT Alert not alerting on states

Juliean Galak
 

Greetings!

I started usng JT Alert a few days ago (version 2.6.30) with WSJT-X and absolutely love it.  Just one problem though - while it alerts on DXCC entities and continents just fine, it doesn't seem to alert on states.  I have it set to alert on about a dozen states on all bands/all modes, but it doesn't highlight any.  I've manually spotted states on the want list at least twice.

Any ideas?

Thanks,
Juliean KQ2Z