2025/3/16
CheckSpot ver4.01 released.
In this version, DX spot for specific callsigns are displayed in the table. Clicking any DX spot will transfer it's callsign and frequency to Logbook entry window.
2025/3/4
CheckSpot ver4.0 released. This program is written in VB6.
2025/2/12
Looup4CNTY ver2.5 released. Minor changes in the menu. Help PDF can be available.
2025/2/8
USACA_MARAC ver1.2 released.
This will be used for USACA_MARAC application. See below.
2025/2/6
Lokkup4CNTY ver2.4 released. See below.
2025/1/26
CheckCallMini ver7.2 released. Minor change.
CheckCall ver8.2 released. Minor change.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. See here When/How you should run my utility as administrator ?
2. Most utilities are written in VB2019 and VB2022. Settings are saved in the following folder.
c:\Users\"User Name"\AppData\Local\"Utility name" See here.
In the case of utility which is written in VB6, setting are saved in xxx.ini in the same folder as xxx.exe.
All have been checked with my Windows 10/11 PC, however no test with other OS.
3. My utility program are not required to install. Place exe file (and packaged files) anywhere. Simply double click exe file or configure as one of utility program in Logger32. (Tools/Utility program setup)
4. Utility programs below are currently supported. However, if you have interest in discontinued program then let me know by email.
5. Auto start failure
If you configure some utilities to run automatically on Logger32 startup, these utilities may fail to connect to Logger32. In this case, try new utility, "utlStart". See below.
6. There are utilities which has not Windows title bar and menu bar. In this case drag "title" to move position and right-click on "title" to show menu.
7. If you are using Chrome as browser you may not download the file when clicking Download button. In this case try following way.
(a) Right click on Download button and click "Save as..."
(b) Use other browser like Edge or FireFox.
If you have any question on my utility program, then post to Hamlogger reflector or send me direct email.
Click any item to see detail.
CheckCall ver8.2
CheckCallMini ver7.2
CheckSpot ver4.01
Lookup4CNTY ver2.4
LookupMaster ver1.16
ModeConverter ver1.01
NixieClock ver 1.3
SummaryV2 ver2.04
SummayBandMode ver1.14
SummaryThisMonth ver1.2
SummaryThisYear ver2.2
SummaryIOTA ver2.72
UDP decoder ver1.04
USACA_MARAC ver1.2
utlStart ver1.2
When callsign is populated in Logbook entry window then it will check whether matched callsign are listed in the text file or not. If it finds matched callsign then data are displayed. If it does not then "not found" is displayed.
You can send data to one of user fields in Logbook entry window. Check "Enable to transfer data to Logger32 User_1/2 field" in the menu. Click "Field to transfer" to select field you send.
New feature in ver8.1
a. Settings in previous version are restored automatically.
New feature in ver8.0
a. CheckCall has two windows, main window and lookup window.
Main window display status info. It can be minimized on startup if you want. Click on CheckCall icon to show/hide main window.
Lookup window display lookup result when the callsign is found. It is hidden when the callsign is not found or Logbook entry window is cleared.
b. Two files are supported. (File #1 and File #2)
c. Lookup result can be transferred in Logbook entry window when just clicking any record.
d. COMMENT field is added as transferred field.
e. Audio alert is added.
The text file
Text file should contain several words separated by space or "=" or "," or ";"
The first word must be his callsign.
sample
JA1NLX,Aki,Logger32 Beta tester
You can download member's list (text file) for various club like FOC, CWOPs etc
https://ok1rr.com/software/club-membership-lists/
https://www.g4bki.com/club_call_history.htm
CheckCallMini is revised version of CheckCall ver7.0.
a. It supports ONE file. If you want, you make your own combined file.
b. It has main window only. Height/width is resized automatically when text length/font size is changed.
c. File format should be same as one used for CheckCall.
d. Lookup result can be sent to either adif field of Logbook entry window. (USER_1, USER_2, USER_3, COMMENT and NAME) Simply click the line you want to send to Logger32.
How to run ?
1. Run Logger32.
2. Run CheckCallMini. You have to select the file you want to use. (ClubMember.txt, CWOPS.txt and FOC.txt are attached as sample file)
3. Move anywhere dragging title bar.
4. Right click on title bar to show menu. Check/uncheck several options.
5. Type callsign and hit TAB key in Logbook entry window. Lookup result is displayed if matched callsign is found in the file. "not found" is displayed instead if matched callsign is not found.
6. Simply click any displayed line to send to Logbook entry window.
7. "Ready" is displayed when Logbook entry window is cleared.
8. Click "Exit" in the menu to close CheckCallMini.
9. Selected file, window size/position, several options status (checked/unchecked) are saved/restored automatically.
What is "Always visible" ?
If this is checked then CheckCallMini window always stay there unless you click CheckCallMini icon in task bar.
If this is unchecked then CheckCallMini window is minimized in task bar when Logbook entry window is cleared. It appears again automatically when it display lookup result.
This is checked as default.
CheckSpot receive DX spot from Logger32. It displays DX spot only if the callsign is listed in the CheckSpotCall.txt. If he is "New any Band/Mode" or "New this Band" or "New this Band/Mode" then it displays alert message and play alert sound. (Option/Enable audio alert for specific callsign)
CheckSpotCall.txt can be edited. Click "Specific callsign list" in the menu bar to edit interested callsign.
Received interested DX spots are displayed in the table.
See details in the Help PDF (Click Download Help below)
This is dedicated for users who are challenging USACA award and works for QSO only with KH6, KL7, or W.
Callsign lookup using QRZ XML or HamQTH ADIF service. It send State and County data to Logbook entry window. (You need to subscribe QRZ XML service if you want to use. HamQTH ADIF service is free.)
Check if his/her county is new or not. It send “new county” if it is not worked, or “not confirmed” if it is not confirmed yet to QSLMSG field, USER_1 field or USER_2 field in Logbook entry window. You may play audio alert. Lookup4Cnty read exported ADIF automatically when it runs.
Changes in ver2.4
USA-CA award rule has been changed by new sponsor, MARAC (Mobile Amateur Radio Awards Club). It does not require any confirmation (QSL or eQSL)
a. Checking on eQSL is removed.
b. Checking on confirmation is removed.
c. It shows "new", "granted", or "worked" on lookup.
d. USACA summary shows total worked number and total granted number.
e. Changes in appearance.
Changes in ver2.2
a. All info/data are displayed in main window.
b. New option "Show popup window on lookup" added. If this option is checked, then small popup window appears and shows "new county" or "not confirmed" or "confirmed" or "not valid county". This window disappears when Logbook entry window is cleared.
c. New option "Always visible" added. If this option is unchecked, then main window is hidden in task bar several seconds after startup.
d. Clicking Look4CNTY icon in task bar display or hide main window.
e. Change made in main window coloring.
f. "X" and "_" buttons added in the main window. Clicking "X" button close Check4CNTY and clicking "_" button hide main window in the task bar.
g. Settings in previous version are restored automatically.
Changes in ver1.16
a. Settings are restored automatically on every update.
b. Minimized and closed button are added in main form.
LookupMaster support QRZxml, HamQTHxml, HamQTHadif, HamCall, QRZRUxml and QRZCQxml. It only works together with Logger32. You can use either of them by selecting from the menu.
It supports CheckCall. Select proper text file you want to use. Text file should be placed in the same folder as LookupMaster.exe.
CheckCall status appears only if "Enable CheckCall" is checked.
ModeConverter replace "
Changes made in ver1.3.
a. change the way to select GIF folder.
b. settings in previous version are restored automatically. (selected GIF folder, window's position etc)
c. Title bar moved to right side of the form.
d. bug fixed
This is old-fashioned clock for your fun. NixieClock.exe, 5 Images folders and BetterFolderBrowser.dll should be in the same folder.
Right click on title bar text to show menu. Hold left click button on title bar text and drag to move location. New location is saved always automatically.
If "Show time in UTC" in the menu is checked then UTC time is displayed. Otherwise, Local time is displayed.
You can select either of 5 different Images folders. Click "Select GIF folder" in the menu.
You can select title bar text font/color and backcolor"
If "Exit" in the menu then NixieClock close.
This is revised version of previous Summary.
SummaryV2 shows worked number in selected year and mode in main form. If you prefer you can see various all time charts and all time award summary.
SummaryV2 need to read Logbook ADIF exported by Logger32. When you run SummaryV2 for the first time, you are prompted to select the Logbook ADIF.
Download SummaryV2.zip, unzip. Place SummaryV2.exe anywhere you like.
This is simple summary utility which shows QSOs by Band/Mode and DXCC/WAZ/WAS worked/confirmed by Band/Mode. (Confirmd by QSL+LoTW only)
SummaryBandMode need to read Logbook ADIF exported by Logger32. Download SummaryBandMode.zip, unzip. Place SummaryBandMode.exe anywhere you like.
It read your Logbook adif exported by Logger32 and shows simple chart. QSO/Band/Day, QSO/Mode/Day, QSO/Continent/Day and QSO/Mode/Month. You can select Year and Month if you need.
Changes made in ver2.2
a. Settings in previous version are restored automatically. (ADIF file path, window's location/size etc)
b. Table can be sorted by clicking header. Table is sorted by Total number by default. (ADIF, DXCC and Total column in QSO/DXCC country this year statistics. WAS and Total column in QSO/US State this year statistics)
This small utility shows summary by Mode/Month of this year with various charts. Default this year is current year. You may select any year. You are asked to select logbook adi file when you first run updated SummaryThisYear. When you want to change logbook adi file then you need close/open SummaryThisYear.
You should place Prefix.csv and WAS.csv in the same folder as SummaryThisYear.exe.
You must select the file path for export.csv and Logbook adif exported by Logger32 when you run SummaryIOTA at first time. Click File in the Menu bar. export.csv can be downloaded at IOTA page.
Place attached files, ai.txt, bi.text and wi.txt in the same folder as SummaryIOTA.exe.
This is a utility which decode UDP message distributed by JTDX/WSJT-X and display decoded message, DT graph and dB graph. It receives UDP message at UDP port from Logger32 RPTR UDP port or JTDX/WSJT-X UDP port directly.
This is the utility which read adif exported from Logger32 and show the lists of US Counties (granted, worked not granted etc)
The list can be saved as text file and used for the award application.
Lists:
All Counties worked
All QSOs by Counties already granted
All QSOs by Counties not granted yet
All QSOs by Counties not granted. This is a suggested QSO list for application.
Change in ver1.2
(1) Running utilities will close automatically when utlStart close.
If you configure some utilities to run automatically on Logger32 startup, these utilities may fail to connect to Logger32.
In this case, use "utlStart"
(1) Configure utlStart utility to run automatically on Logger32 startup.
(2) Run "utlStart"
(3) Setup caption and utility exe path.
(4) Check the utility you want to run.
(5) "?" button browse your PC (to find exe path)
(6) "Run" button will run the utility.
(7) Delay to run the first utility is selectable (1000ms as default)
There are two types of utilities.
Utility which use registered message to communicate to Logger32 like CheckCall, LookupMaster, Lookup4CNTY etc. If you run this type of multiple utilities at same time, then you may have connection failure.
Utility which does not use registered message like SummaryThis Month, SummaryThisYear etc.
CheckCallPartial ver2.01
CheckCNTY ver1.03
CheckFriend ver1.0
Clock ver2.01
ClubLogUpload ver4.14
LookupEQSL ver1.0
ViewAppDataDirectory ver1.0
WorkedConfirmedSummay ver1.03
yourRado ver1.04
1. How to run as administrator
a. Right click on abcXYZ.exe.
b. Click Property.
c. Select Compatibility tab.
d. Check "Run this program as administrator"
e. Click "OK"
2. How to configure as one of utility program in Logger32
a. Click Tools
b. Click Utility program setup.
c. Configure menu item and utility program path.
d. This utility program can be run from Utilities menu.
3. Does utility program work in this case?
In the case that utility run from Logger32 utility menu,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> NOT work
In the case that utility run directly,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> NOT work
Run Logger32 as NOT administrator, Run utility as NOT administrator---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> NOT work
In the case that utility run from Logger32 utility menu,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> OK
In the case that utility run directly,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> OK
It is suggested that Logger32.exe (and Logger32autoinstaller.exe/autoinstaller.exe) should be run as "Run as administrator.
No Code Website Builder
