Frequently asked questions

Trouble loading a QSL format

PROBLEM:
The QSL format somehow gets an invalid filename set so it can't load the format file nor can you get into the format program.

FIX:
Clear out the format settings in the file LOGM.DAT.

HOW:
Use the file FMTCLEAR.EXE.

The utility program FMTCLEAR.EXE is supplied with Master Log version 3.42 and after. If you don't have a copy download one first.

Copy or Save the file FMTCLEAR.EXE to the directory that contains LOGM.DAT (usually \LOG\DATA).

Move to the data directory on your hard disk.

Execute FMTCLEAR.EXE.

Your format settings will be cleared (not the formats themselves). You need to re-select your desired formats from the Format Window inside the program.

Master Log Program Locks or Crashes

PROBLEM:
The amount of conventional memory on your computer is set too low. This affects the Master Log module and not all the others because it is much bigger than the others.

FIX: Make more conventional memory available by running a DOS utility called MEMMAKER.

HOW: Quit any programs that are running. Type MEMMAKER at the DOS prompt and follow the instructions given for "Express Setup".

Version 3.47 Yaesu Rig Control Dosen't Work

PROBLEM:
You updated to version 3.47 and now your Yaesu rig control stopped working.

FIX:
In the process of adding code for the FT-1000MP the routines for the other models was goofed up. Download the program module below or E-mail Jonit for a free replacement module via snail mail. (Or even better - order an update to the most current version!)

HOW: Use the following instructions:

Get the fix file.

Uncompress the file to the directory that contains LOGM.DAT (usually \LOG\DATA).

Your Yaesu Rig Control Never Worked

PROBLEM:
You may not have set the number of stop bits for the communications port to 2. Yaesu is the only rig with this situation as all the other rigs use the default value of 1.

FIX:
Change the parameter in the SERIAL.DAT file.

HOW:
Load the file SERIAL.DAT that can be found in your \LOG\DATA subdirectory into any text editor. You will see complete instructions within the file. Change the number of stop bits on the communications port you are using to 2.

An Improved WB2OPA Import Routine for Version 3.48

PROBLEM:
Upon importing a WB2OPA file you find a lot of extra records that contain 00/00/00 for the date.

FIX:
It was caused by something I wasn't expecting in his file structure. After working with a customer's file I was able to solve the mystery. You need to get a copy of the updated LOGT2.EXE program.

HOW:
Use the following instructions:

Get the fix file.

Uncompress the file to the directory that contains LOGM.DAT (usually \LOG).

My 1998 Edition of Callbook CD ROM Won't Run

PROBLEM:
"I just received my 1998 (or 1999) Edition of Callbook and it will not interface with the Master Log program."
In the interest of adding more data fields the Callbook company decided to change the format of their data structure. This fix is only necessary for WJ2O versions 3.49 and earlier. This fix will not only get your 1998 Callbook edition working but will also access your earlier versions.

FIX:
Download the new TSR program and install it.

HOW:
Use the following instructions:

Get the fix file.

Copy the file called DOSLOGAC.EXE that you just downloaded over the top of the file with the same name in the logging program's base directory (usually \LOG).

The hour is different when I import a CT file

PROBLEM:
When I go to import a CT file, the hour is not correct. CT will jiggle the hour you are logging based on the setting of your TIMEZONE parameter in AUTOEXEC.BAT. Most users are not even aware that this is happening.

FIX:
You can adjust the hour during the import process. When the first CT QSO is displayed on the screen you have the ability to move the hour one way or another. This feature was added to version 3.48 (May 1997) and allowed a +/- 4 hour adjustment. In version 3.50 (August 1998) it was expanded to allow for +/- 12 hours.

HOW:
Start the usual import routine and you will see an additional box on the right hand side of the screen once the first QSO is displayed.

I can't get the times set right

PROBLEM #1:
The times in the box in the upper right hand corner of the screen are not set right.

FIX:
We need to accurately change the settings in the System Parameters screen.

HOW:
From the Main Menu of the program press SP for System Parameters. Then press G for General. You will see a list of 8 different parameter settings. The settings that effect the time box are questions 2 through 4.

PROBLEM #2:
UTC DIFFERENCE FROM COMPUTER CLOCK. 
Not all computers are set to your local time. Some people have their computer clocks set to UTC. In this setting you need to set the difference between UTC and your computer's clock. If your clock is set to UTC then enter 0. If your computer clock is set at Eastern Standard Time (the east coast of the USA) you would enter 5.

PROBLEM #3:
LOCAL TIME ZONE ABBREVIATION.
Here you can enter up to 3 letter of initials that describe your local time zone. For example Eastern Daylight Time might be EDT.

PROBLEM #4:
DIFFERENCE BETWEEN LOCAL AND UTC.
Now we want to set how many hours your time zone is from UTC (this is irregardless of what your computer clock is set at). Here on the east coast of the US we are actually behind UTC by 5 hours when not in Daylight Savings Time so you would enter -5 (that's a minus 5). For PST that's -8.

The Net Operations Module Won't Work With Version 3.50

PROBLEM:
When in the Net Operations module you press E for Edit the program would crash.

FIX:
Replace one of the program files with one you can download here.

HOW:
Use the following instructions:

Get the fix file.

Copy the file called LOGN.EXE that you just downloaded over the top of the file with the same name in the logging program's base directory (usually \LOG).

Mode Selection Not Working With Reports in Version 3.50

PROBLEM:
When in the Reports module any selections based on mode would not take.

FIX:
Replace one of the program files with one you can download here.

HOW:
Use the following instructions:

Get the fix file.

Copy the file called LOGR.EXE that you just downloaded over the top of the file with the same name in the logging program's base directory (usually \LOG).

May 1999 Issue of GoList Not Interfacing With Version 3.51

PROBLEM:
The creators of GoList made a couple changes with their file output program that caused my program to not recognize it.

FIX:
Replace two of your WJ2O program files with ones you can download here. These fix files will only work with version 3.51. If you are not sure what version you have look on the information page (press IN from the main menu).

HOW:
Use the following instructions:

Get the first fix file.

Copy the file called LOGX.EXE that you just downloaded over the top of the file with the same name in the logging program's base directory (usually \LOG).

Get the second fix file.

Copy the file called LOGAM.EXE that you just downloaded over the top of the file with the same name in the logging program's base directory (usually \LOG).