|
If you have not looked for your answer in LOGic's help, please
do so. It contains answers to most questions about how to use LOGic.
Use the Find button in the help screen to search for keywords.
You may also search our web site.
If you do not find the answer to your question here, try our Infrequently-Asked Questions!
Problems related to bugs that have been fixed, obsolete products and operating
systems, etc. are covered.
Our most-asked
questions...
I cannot open LOGic's help.
See http://support.microsoft.com/kb/902225/
I get an error:
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
or something similar when installing LOGic.
There is a problem with your installation of Windows.
See
http://support.microsoft.com/kb/324767
Note: LOGic is a 32-bit program.However, the InstallShield
installation program we use is 16-bit. This should not be a problem on Windows
XP. However, we have run into several cases where the above-referenced fix
needs to be performed on your computer.
FYI, we are in the process of upgrading to a new install program
is 32-bit in order to be compatible with Windows 64, which will not run 16-bit
stuff..
I get an error "Incompatible Version of the RPC Stub"
This error occurs when starting LOGic and at other times. It is caused by
incompatible versions of a group of Windows library files. We have had
infrequent reports of this error, only from customers using versions of Windows
prior to Win 2000.
Please download and install the update from the following Microsoft web page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321915
I get an error "Unknown member OREGQTH"
This error occurs when opening the callbook or spot log. It is caused by a
Windows library that is missing or not registered. We have had infrequent
reports of this error, only from customers using versions of Windows prior to
Win 2000.
Please download and install the update from the following Microsoft web page:
http://www.microsoft.com/downloads/details.aspx?FamilyID=0a8a18f6-249c-4a72-bfcf-fc6af26dc390&DisplayLang=en
I get a "Backup Compression Failed" error when doing a backup.
What gives?
This error is caused when LOGic is installed in a directory path
that contains a space, and the shortcut used to start LOGic uses DOS notation to reference the
Working Directory.
For example, suppose that you have LOGic installed in
(note the space). Right-click the shortcut that you use to
access LOGic and select Properties. Note that the Working Directory looks
something like this:
This is the DOS name for the LOGIC 6 directory. To
fix the problem, change the Working Directory to the normal Windows format
with the space:
Simply deleting the shortcut and recreating it by right-clicking
LOGic.EXE and selecting Create Shortcut may fix the problem. Backup also
works if you run LOGic directly (without using a shortcut) from Windows by
double-clicking LOGIC.EXE, or from the DOS command prompt by typing LOGIC.
We're not sure how the "incorrect" shortcut gets
created, or why it doesn't work. The only way we have been able to get a
shortcut with the DOS path notation is to manually create one. If you want
to find the DOS name of a file or folder, go to the DOS Command prompt and type
DIR /X.
We are using Win XP.
Running LOGic on Win 95
LOGic 7 apparently runs fine on Win 95. However, HTML help must
be installed. Otherwise, you will get an error Cannot load 32.bit DLL
hhctrl.ocx on startup, and you cannot view Help.
Note that HTML help may already be installed on your
system. If you can view Help, you do not need to install HTML help.
Installing HTML Help
You need Internet Explorer version 3.02 or later. Check
your Internet Explorer version in Help/About. If you need to update
Internet Explorer, you may download it from
http://www.microsoft.com/windows/ie/downloads/recommended/ie55sp2/default.asp
After verifying that Internet Explorer version 3.02 or later is
installed, download hhupd.exe
and run it. This installs HTML Help on you computer.
LOGic should now run fine!
I need to add a mode that is more than 5 characters, such as QPSK31.
How do I do this?
Go to Tools/Misc Utilities. Choose "Change size of
log fields". Change the size of the mode field. The Log and
Mode table will both be adjusted.
I get an error INDEX DOES NOT MATCH TABLE..., or RECORD OUT OF RANGE...
To fix, do a CLEAN (see below).
No data is not lost. Only the Index files are bad. This can happen if Windows crashes, the
power fails, or Windows is not shut down properly. In the case of a catastrophic failure
such as a power outage, you will probably lose only the last QSO entered.
It is a good idea to run SCANDISK occasionally to make sure your hard
drive is healthy.
How do I do a CLEAN?
If you are running LOGic, close it. Go to the Windows Start Menu, Programs, LOGic 5, and click the CLEAN icon.
This will recreate all indexes. Clean also removes all temporary files. A Clean is
done automatically every time you install LOGic or an update.
Callbook Interface does not automatically log info
Click Log/Setup, and make sure auto logging from the callbook is
turned on.
Also, make sure that you are using the correct procedure to add a new QSO.
- Add a new QSO by clicking the + button or using a keyboard shortcut.
- Type a call in the call field
- Press {Tab} It is important that you press {Tab}.
My awards progress tallies are incorrect
You need to run Update Awards Progress Info. This is
normally updated automatically, but certain operations such as importing data or restoring
from a backup require you to run Update Aeards Progress Info. See section 6.3.3 of the
manual.
Also, the band and mode must be logged for a QSO to tally.
Additionally, make sure that the entity being tracked is logged--to track
DXCC, the DXCC field must be filled in. To Log CQ Zone, CQZ must be filled in.
These are normally filled in automatically when logging or importing data, but it
is possible to turn off auto logging of DXCC, CQ Zone, etc., or manually blank or
enter a value into these fields.
How do I import data from programs not listed in
LOGic's tools/import menu?
Most programs currently on the market support ADIF
(Amateur Data Interchange Format). Any program supporting ADIF can transfer data
using a common format. The CT ADIF program may be found at by
clicking here.
If the program in question does not support ADIF,
look in the IMPORT subdirectory
of the LOGic 5 FTP site. If no luck there, send your data to PDA. We have programs
to import most other programs. We can also import data from most homemade loggers,
spreadsheets, etc.
LOGCONV is a handy utility for converting between several log file formats.
I have a lot of duplicate QSOs entries in my log. How did this happen, and how
do I fix it?
Duplicate records can appear in your log when you import the same data more than
once, or restore a backup and use the APPEND option.
To remove the duplicates, go to tools/misc utilties. Select the Delete Duplicate
QSOs option. This utility compares callsign, date, and time, and will NOT delete a
record simply because you have worked the same station more than once. When
selecting which QSO to keep from a group of duplicated records, it will choose the one
with the best QSL Rcvd status.
Missing ARRL SECTION LIST
Some LOGic 7 CDs were sent out with the ARRL Section list missing. This has been
corrected.
If you are missing the ARRL SECT list, and yours is missing, please download
arrl_sect.dbf
to anywhere on you computer. Run LOGic, go to tools/setup/list of valid values.
Click the Import button. Select the arrl_sect.dbf file that you
downloaded, and click the Open button. This is not included in the maintenance
update, since we didn't want you to have to download the entire lists table!
©
15-Oct-08 10:46file:///X:/WWW/PDA/HoseNose/radio/support/logic7/faq/default.asp
©
2005 Personal Database Applications, Inc. All rights reserved.
LOGic ham radio software support - FAQ and troubleshooting. |
