I don't know what your achieving by altering the column widths. The overall window size doesn't change so you end up with a lot of empty window space without any net gain in available

I've been shrinking the band activity columns that I don't use, thus it's about half the size for just FT4&8. Would also like to cancel out the bands I can't use. Sent from Xfinity Connect

"C:\ProgramData\HamApps\Databases\fcc_lotw_eqsl.sqlite" I advise against trying to modify the data in the file. If there is an error in the data report it here so it can be corrected for all

Vladimir, Very likely that for the scans affected your adif log file doesn't contain the required information. Does it contain the <CONT> and <PFX> fields? Please send me direct (not via this group)

Dave, Sounds like the shortcut your using to start JTAlert is referencing an incorrect path or file. Is this a user-created shortcut or one automatically created during the

Ed, While possible, coloring is unlikely to be implemented. An alternative is to use the Alternate Build of JTAlert which does away with this abbreviation, instead using plain

RR73

Dennis, It is on the todo list, added by myself when I first coded the F4 support as I knew the user request would be coming ;-) Until it is implemented, I suggest you

Laurie, there is at the time of writing, a day of activity sponsored by the Russian Digital Radio Club. RDRC. Look here,http://www.rdrclub.ru/dni-aktivnosti-rtsrk/825-jt9-activity Best wishes and

Laurie, Speaking of the "!", it might be nice if it were in red to make it more noticeable. Ed, K0KC k0kc@... http://k0kc.us/

Hi Laurie, Russian JT9 activity w/e. 73 Bill G4WJS. -- 73 Bill G4WJS.

I have noticed over the last 2 days, a significant increase in JT9 activity as shown in the JTAlert Band Activity popup and on HamSpots and PSKReporter. Is there a JT9 specific contest

It indicates an Update is available, either JTAlert or the Callsigns database if installed. BTW, the "!" symbol is an exclamation mark, not an apostrophe. de Laurie

Barry, Looks like the file holding version information on the current installed version did not get updated during the update. Simply rerunning the JTAlert setup again

Was working fine, but after a freeze and reinstall of both WSJT-X and JTALERT 2.14.3, WSJT-X starts and runs fine. When I start Jtalert, I get the message: Windows cannot access the specified device,

Updates available Jim N6DVR

What does the (!) mean on the title bar of JT Alert? Running JT Alert 2.13.10 and WSIT-X 2.1.0. I am not seeing many DX callsigns in the grid like I used to, mostly USA/VE.

In addition to the work around I recently posted I have used this one and it works just fine. Somewhat of a chore if you have a great number of confirmed LOTW QSOs. Hopefully. the HRD

Please let me explain that item 1 was the only change I made in HRD5.0 and no other changes were needed to do correct upload and verified download. cheers de Barry

The callsign database is C:\ProgramData\HamApps\Databases\fcc_lotw_eqsl.sqlite de Mike W9MDB