
***** Installing XMLog *****

To install XMLog from an MS-DOS window using pkunzip:

  - Create a temporary directory, for example c:\xyz

  - Move the XMLog zip file to c:\xyz - assume the file name is xmlog123.zip

  - Unzip the file with the command: pkunzip xmlog123.zip

  - Run c:\xyz\setup.exe

  - When setup asks for the destination directory it's easiest to use the
    default value of c:\mlog

  - Delete c:\xyz

  - That should do it, double-click on the XMLog icon to start things up. Use
    the XMLog help menu items for more info.

  - You can create a set of install diskettes if you run floppies.bat after
    the pkunzip step. To install XMLog from these diskettes run setup.exe
    from the first diskette.

To install XMLog using WinZip:

  - Select the zip file using "File/Open Archive"

  - Select the "Install" button

  - You can create a set of install diskettes by doing an "Extract" to a
    temporary directory and then running floppies.bat from that directory.
    To install XMLog using these diskettes run setup.exe from the first
    diskette.

***** General Comments *****

XMLog is a logbook and packet program for Windows. The logbook window
provides features for awards tracking (DXCC, WAZ and WAS) and the packet
window provides features for the PacketCluster user.

For information about changes made for this version check the file
"changes.txt" or use the "Help/Display changes.txt" menu item.

To browse the help screens use the "Help/Display Help" menu item.

XMLog is freeware, not commercial software. There is no charge for its
use and no limitation on its distribution. Resale of XMLog for profit is
prohibited.

If you would like to make a voluntary donation to help support the XMLog
project please send it to the address shown in the Feedback section below.

Although XMLog was created to satisfy my own needs I think you'll find it's
competitive with other logging systems. If you feel that something's missing
let me know.

***** System Requirements *****

XMLog requires at least a 386 PC with 8 megabytes of memory running Windows
3.1 or later.

***** Windows 3.1 *****

Changes made in XMLog version 1.17 require file sharing to be available when
log files are opened. This feature may not automatically be available on
Windows 3.1 systems. When opening a log file, you may get a message directing
you to add the line "\dos\share" to your autoexec.bat file. Use "Help/Display
Help" and check the "Starting XMLog" section for more info.

***** Options *****

XMLog is shipped with the options set to the values I use. Browse through
the various "Options" menu items and make any appropriate changes.

The node files shipped with XMLog are ones used locally to connect to the
PacketCluster and various bulletin boards. These files are provided as
examples, feel free to delete them and create your own.

The PacketCluster alert feature is initially turned off. We assume you don't
want alerts enabled until you've brought your log up to date (otherwise every
spot will give an alert). Use "Help/Display Help" and check the sections on
PacketCluster Support for more info.

***** CW *****

The XMLog packet window supports a CW keyboard mode, can send files as CW,
and can give PacketCluster spots as CW. The CW controller used for these
features can't always maintain perfect timing on slower 386/486 machines. It
works well when nothing else is going on, but other system activity can cause
imperfect timing on these machines. If you have timing problems try limiting
what's going on in the background - shut down any clocks (including the one
in XMLog's status bar) and any animated screen savers, etc. The more resources
available to keep the CW going, the better.

***** International Settings *****

Versions of XMLog prior to 2.16 required setting the decimal point to "."
in the Windows "Regional Settings" setup. Now XMLog can handle "," as the
decimal point.

XMLog supports dd/mm/yy date formats and metric distances. Use the
"Options/Log Options" menu to enable these features.

***** Importing Logs *****

XMLog has built-in importing for files written by CT or files that conform to
ADIF (Amateur Data Interchange Format). There are also utilities available that
convert logs from other programs (NA, TRLog, CT, dBase) to ADIF. See the help
section on "Importing/Exporting Log Entries" for more information.

The strategy for importing log entries from other sources is to create a text
file that contains the entries and then reformat these entries for XMLog.
Most log programs can either backup their logs as text files or produce reports
that contain all log entries saved in a text file. I've included some QBasic
programs (import.bas, import1.bas, import2.bas, ...) to make reformatting
these text files a bit easier. For more info check the internal documentation
contained in these .bas files. Also check the help file section
"Importing/Exporting Log Entries".

Since importing entries from other log programs requires some programming
expertise it's not for the casual user. If you modify import.bas to handle
files from another log program I'll be glad to include your file with future
XMLog releases.

Note: It seems that some Windows systems do not include QBasic. If you need a
copy it's available at www.xmlog.com/qbasic

***** Prefix File Format Change in XMLog 3.00 *****

This section is primarily for users who maintain a custom prefixes file.
Since version 3.00 includes format changes to the prefixes file these
users may not want XMLog to replace thier custom file or to perform automatic
prefix updates to thier logs.

Version 3.00 added information to the prefixes file that allows automatic
updates of logs to use new 'main' prefixes to identify countries. This update
(optionally) occurs if the 'PrefixesVersion' defined in the prefixes file is
newer than the last version used when the log was opened. You can also perform
this update by choosing "Edit/Automatic Prefix Update". Within the prefixes
file countries with new 'main' prefixes are flagged with "OldPrefix=xxx" fields.

Previous to version 3.00 XMLog maintained a list of ADIF indexes in the file
'adifinfo.txt'. These values provide a unique ID for each DXCC country and are
used by the ADIF import/export feature. In version 3.00 these values were
moved to the 'prefixes' file.

Version 3.00 also has a new menu item "DX/Show Callsign List". This feature
allows you to assign DXCC countries to callsigns that XMLog can't guess
correctly.  This feature should reduce the need for editing of the prefixes
file.

To accomodate users who are maintaining a custom prefixes file XMLog will still
read old-style prefix files and also read the ADIF indexes from adifinfo.txt.
The adifinfo file is no longer distributed with XMLog and it will be up to
users with custom files to keep adifinfo.txt in sync with their custom prefix
file.

It may be best for custom file users to bring their files in line with the
current format.  The new file is always available as 'prefixes.new' even if
you choose not to replace the current file at install time.

If you decide to stop using your custom file and move to the standard file
you may wind up with 'main' prefixes in your log that XMLog does not
recognize - even after the 'automatic prefix update' is complete.  The
easiest way to get a list of these prefixes is to do a "Awards/DXCC Totals".
Any unrecognized prefixes can be changed using "Edit/Change Prefix".  To
find the current main prefix for a country use "DX/Show Country List".

***** Fonts *****

Logbook reports directed to the screen or printer support all fonts. The packet
window also supports all fonts but it's usually best to use a fixed width
(non-proportional) font so that columns will align correctly. For most systems
this means the using Courier, Courier New, Terminal or FixedSys fonts.

***** On-Line Callbooks *****

XMLog can do callbook lookups or create mailing labels using the QRZ, the
Buckmaster and the Radio Amateur Callbook (Flying Horse) CD's.

  - The Radio Amateur Callbook CD is by far the most complete.

  - The QRZ disk has limited support for non-US calls.

  - The QRZ support file "qrzdll.dll" has gone through several changes.
    If you are getting error messages searching a QRZ disk, try replacing the
    file C:\WINDOWS\SYSTEM\QRZDLL.DLL with the one supplied on the QRZ
    CD. After replacing the file reboot your system and try again.

  - The Buckmaster disk for 5/95 has a different format from previous
    Buckmaster disks, XMLog doesn't handle older disks.

  - Note that the Buckmaster disk doesn't contain entries for all countries,
    it's missing things like Germany and Japan. Also, Buckmaster entries have
    not been "sanitized" - some countries have entries with the last name
    first, etc.

XMLog can access callbook data that has been copied from the CD to your hard
disk.  See the help file section on Callbook setup for details.

***** Feedback *****

Anyone who wants to keep up to date, wants more info, or has suggestions
should check my home page http://www.xmlog.com or contact:

   Michael McAmis
   433 Hanover Center Road
   Etna, NH - 03750

   m.mcamis@valley.net      (e-mail address)

***** History *****

The original XMLog was written in MAD (the Michigan Algorithm Decoder) for
the IBM 7094 back in the keypunch era. It was then moved to UNIVAC 1100
machines (timesharing mainframes at the U of Md). I moved from D.C. to the
Hanover, N.H. area and moved the code to DOS using True Basic while I was a
True Basic employee. (True Basic, Inc. was founded by John Kemeny and Tom
Kurtz, the inventors of Basic). The current version is implemented using
Visual Basic and Borland C++.
