Skip to main content.

New Feature - OTRSP

Logger32 OTRSP Commands  OTRSP Command Macros  New File
Starting with Logger32 version 3.48.55, new OTRSP command macros have been added to RCP panel, CW Machine and Soundcard Data panels. More details are on this OTRSP page. This will enable users of OTRSP supported SO2R interfaces to more fully use both radios.

Automatic Updates

Logger32 Auto Update Help information  Logger32 Auto Update - Help file information  New File
Starting with Logger32 version 3.47 Automated update has been incorporated. This can be setup for automatic notification or accomplished manually. More details are in the Logger32 v3.47 Help file.
NOTE: For this function to operate, you must have an Internet connection available. It is also suggested that you close all programs except Logger32. It may be necesary to temporarily disable any anti-Virus software you are running. Please see the discussions on Hamlogger Yahoo! Group.

Upgrade Version

Upgrades Logger32 3.49.x to 3.50.0  This is the Logger32 Upgrade which updates the software ONLY for users of v3.49.x and above  
Make a full backup of Logger32 using the built-in capabilities of Logger32 (the two zip buttons at the left of the toolbar). Make an ADIF backup of each Logbook you use. This is VERY IMPORTANT. Part of this upgrade rebuilds the logbook to a new format. If errors are encountered, You will need the ADIF files to recover your logbook. YOU HAVE BEEN WARNED! You have downloaded the zip file, follow detailed steps to complete the upgrade. Step 1 will be to replace the Logger32 executable files, help files, and rebuild the Logbook databases. Step 2 is optional, and will replace your Country/Prefix databases with the latest release. Step 3 is optional, and will replace your IOTA databases with the latest release. The upgrade zip file contains three zip files. Upgrade.zip, Country Database.zip, and IOTA database.zip. With every major release of Logger32 there are always a few unhappy users. The fall into two categories: a) There are the really clever ones who have their own way of doing things and don't need to follow instructions, and b) those who do not know how to unzip the content of a zip file into a directory - The instructions are clear, unzip the content of the zip file (not copy the zip file) into the Logger32 directory. I know you're smarter than the average bear, but just do as you're told. Before you start: 1) make a note of the name and full path of your Logbook. Look at the title bar of the Logbook Page window. 2) MAKE ABSOLUTELY SURE YOU HAVE KNOWN GOOD UP_TO_DATE ADIF BACKUPS OF ALL YOUR LOGBOOKS.
UPGRADE INSTRUCTIONS for 3.49.x to 3.50.0 ONLY:
Step 1:
  1. Stop Logger32
  2. Unzip the contents of the downloaded zip file into a covenient location. This will give you 3 Zip files
  3. Unzip the contents of Upgrade.zip to your Logger32 directory
  4. Start Logger32 v3.50
  5. Verify that Everything is working to your satisfaction and that you have actually installed version 3.50 Go to Step 2.
  6. This release requires new version 3.50 Language files which are available on the Support section of this website
When Logger32 completes loading, it will automatically start convert your Logbook to the new 3.50 format. On completion if the conversion, it will automatically recalculate the stats for the Logbook. If Logger32 encounters any errors while converting your Logbook, it will stop with an error message. Make a note of the full text of the error (including the title bar of the error message). Look down this page to the instructions on how to recover.
Step 2:
  1. If you do NOT want to use the new Country/Prefix databases because you maintain your own, jump to Step 3.
  2. Stop Logger32
  3. Unzip the Country Database.zip file into the Logger32 directory.
  4. Run Logger32. It will detect a new database has been loaded and will prompt you to download/install the latest Club Log updates. Even if you have done it already, it will be allowed a second time.
  5. Type the word DATA into the Callsign field of the Logbook Entry Window. The database version number of 3.50 should be shown in the left pane of the upper status bar. Go to Step 3.
Step 3:
  1. If you do NOT want to use the new IOTA databases because you maintain your own, skip Step 3.
  2. Stop Logger32
  3. Unzip the IOTA Database.zip file into the Logger32 directory
  4. Run Logger32
  5. If there is an IOTA field in the Logbook Entry window, and it has a ? to the right do this: Type the word DATA into the Callsign field of the Logbook Entry Window. Click the ? This opens the IOTA information window. The top row is for IOTA AF-000 (a dummy entry). Click on it. You can now see IOTA Database version 3.50 at the bottom right of the Window.
  6. Run Logger32 and verify that you have version 3.50.0 running
  7. Recalculate the statistics for all your logbooks
Additional Log Books:If you have more than one Logbook for other calls or your own call, you can now change to each log book in turn and the automatic conversion will be done. Any error in conversion, read the recovery instructions at the bottom of the page.
RECOVERING FROM LOGBOOK CONVERSION ERRORS:
First, don't panic. The sky is not falling. This is easy, just follow these simple steps:
  1. Stop Logger32
  2. Before you started, you made a note of your Logbook name. Look in the directory where your logbook is, you will see FOUR files with that name they will have extensions of .ISD, .ISF, .ISL and .ISM. Delete these four files.
  3. Run Logger32. It will start with an empty logbook.
  4. Now to import the ADIF file you made before you started, do this: Click FILE | IMPORT LOGS | ADIF and select the backup ADIF file you want to use. You now see the Import ADIF Window. CHECK the REBUILDING LOGBOOK option and then the Start button.
  5. Any errors with the import are saved in the BAD.ADI file, and can be fixed later (it's in the help file how to do it).
  6. Go back to item 5 of step 1 and complete the upgrade.
BLOCKED HELP FILE:
If, after updating/installing Logger32, you can not open the help file, or when you click on a subject you receive the message "The page cannot be displayed. The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings."
You can correct this problem - Using Windows Explorer, go to the Logger32 directory and right click on the Logger32.chm file. Select properties and UNcheck the message at the bottom of that screen saying "this file was downloaded from another computer and may be blocked."

Full Version

The Full download of Logger32 v3.50.0This is the Full Version of Logger32 version 3.50.0 which is intended for New Users   
This package is intended for new users of Logger32 or those attempting to upgrade from a release earlier than the last release.
WARNING:
Effective release 3.24 the default installation directory has changed from C:\Program Files\Logger32 to C:\Logger32 This has been done because of Vista and Win7 issues with virtualization and the \Program Files directory.
If you are a new user:
  1. If you are a Vista or Win7 user, read the notes below
  2. Run SETUP.EXE to install Logger32
If you are upgrading from an old version:
  1. Before installing this software, with Logger32 running, you must
    1. Export all your logs in ADIF format.
    2. Zip your logbooks and user files using the leftmost two buttons on the Logger32 toolbar.
    3. Note the name of your Logbook (it is on the header of the Logbook Page Window)
  2. Stop Logger32
  3. Run Setup.exe - Make sure you install Logger32 in the correct directory (the same directory as your previous installation).
  4. After installing this package, run Logger32 and verify the correct version is running.
  5. Stop Logger32
  6. Delete your four Logbook files (the filename is as noted in step 1c). A logbook consists of a set of four files filename.ISD, filename.ISF, filename.ISM and filename.ISL
  7. Run Logger32 again.
  8. Import the ADIF file(s) you created in step 1
  9. If there are errors during the ADIF import, correct the errors in the BAD.ADI file, rename the file and re-import.
  10. Recalculate the statistics for this logbook
  11. If you have more than one Logbook, repeat steps 7, 8, 9 and 10 for each Logbook you exported in step 1a.
Suggestions for Vista and Windows 7 users:
  1. Turn UAC OFF. Vista/Win7 has a very annoying protection system which keeps popping up messages asking you if you really want to do something. This is known as the (U)ser (A)cess (C)ontrol and is best turned OFF if you want to maintain your sanity. Review the Vista/WIn7 help system to find out how to do this on your machine. See: http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off
  2. Logger32 should be installed in a folder directly off the root such as C:\Logger32 (the installation default).
  3. The CW Machine (in software mode) does not generate sidetone correctly under Vista or Win7. PC freezes and/or BSOD have been reported. Turn off CW side tone.
Installation Error:
If, during installation you receive an error message similar to: "Cannot find the source file C:\temp\@IOTAIsland23.isd to install OR - "Cannot continue installation because the following is not found: c:\temp\logger32\\@mmtty.exe. The path and filename are NOT critical and will change from user to user.
The critical point is that the missing file is prefixed by the @ sign. This results from previously failed installation attempt in which Windows incorrectly uncompressed files into the Windows directory. Search your Windows directory and delete any files with the Logger32 or Logger name and then try the install again.
Blocked Help File:
If, after updating/installing Logger32, you can not open the help file, or when you click on a subject you receive the message "The page cannot be displayed. The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings."
You can correct this problem - Using Windows Explorer, go to the Logger32 directory and right click on the Logger32.chm file. Select properties and UNcheck the message at the bottom of that screen saying "this file was downloaded from another computer and may be blocked."