  ***** Installing XMLog from a .zip file *****

  Move the zip file to a temporary directory, unzip it, and
  use Windows to run setup from that directory. Here's the
  details:

  - Create a temporary directory, for example c:\xyz
  - Move the xmlog126.zip file to c:\xyz
  - Unpack the file with the command: pkunzip xmlog126.zip
  - Use Windows to run c:\xyz\setup.exe
  - When setup asks for the destination directory it's easiest
    to use the default value c:\mlog
  - That should do it, double-click on the XMLog icon to start
    things up. Use the XMLog Help menu items for more info.
  - Delete the files in c:\xyz, delete c:\xyz

  After the pkunzip step, you can optionally create a set of
  install diskettes by running the floppies.bat file.

  ***** Installing XMLog from diskettes *****

  Just run a:\setup, or to be more precise:

  - Use Windows to run a:\setup.exe
  - When setup asks for the destination directory it's easiest
    to use the default value c:\mlog
  - That should do it, double-click on the XMLog icon to start
    things up. Use the XMLog Help menu items for more info.

  ***** 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. The logbook window also allows you
  to import files created by the CT contesting system.

  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 or double-click on the "XMLog Help" icon.

  XMLog is "freeware", not commercial software. There is no
  charge for its use and no limitation on its distribution.
  Originally it existed to satisfy myself and other local users.
  Still, I think you'll find it's very competitive with what's
  out there. If you feel 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 a Windows 3.1 system.
  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.

  ***** Windows for Workgroups 3.11 *****

  A problem with older versions of XMLog that caused the packet
  window to freeze when using Windows for Workgroups 3.11 has
  been fixed.

  ***** Options *****

  XMLog is shipped with most options set to the values I use.
  Look 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,
  they're only useful 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 send PacketCluster spots as CW.
  The CW controller used for these features can't always
  maintain perfect timing. It works well when nothing else
  is going on, but other system activity can cause imperfect
  timing on slower 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), shut down
  any animated screen savers, etc. The more resources available
  to keep the CW going, the better.

  ***** Windows 95 *****

  I had hoped Windows 95 was going to improve CW timing with
  better resource sharing which would make CW more immune to
  other system activity. However, CW sounded fine on my 486/66
  machine using Windows 3.1, but is a bit choppy using Windows
  95. (Though it seems to work fine on many other systems
  using Windows 95).

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

  Some International settings for Windows set the decimal point
  character to comma rather than period. This causes a few
  problems (frequencies are displayed as 14001,95 and double-
  clicking on a frequency for rig control just gives a beep).
  To set the decimal point character to period...

  - For Windows 95 check the Control Panel "Regional Settings"
    under the "Number" tab and set the decimal point character
    to "."

  - For Windows 3.1 check the Control Panel "International"
    setting under "Number Format" and set "Decimal Separator"
    to "."

  ***** Importing logs *****

  XMLog can only import text files written by CT or by XMLog.
  The strategy for importing from other sources is to create a
  text file containing the log data and then reformat the data
  for XMLog. Most other 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 a little QBasic
  program (import.bas) to make reformatting these text files a
  bit easier. For more info, check the internal documentation
  contained in the file import.bas and 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
  would like XMLog to have built-in support for importing logs
  from specific sources, let me know. If you modify import.bas
  to handle files from another log program, let me know the layout
  of the text file and I can add support for that format in a
  future release.

  ***** 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 or FixedSys fonts.

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

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

    - The QRZ disk is only useful for US calls.
    - 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.
    - The Radio Amateur Callbook CD is by far the most complete.

  ***** 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

     W1ECT @ W1ET.NH          (packet)
     m.mcamis@valley.net      (internet mail)

  ***** 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 True Basic when I worked for them. True
  Basic, Inc. was founded by John Kemeny and Tom Kurtz, the
  inventors of Basic. This Windows version is implemented using
  Visual Basic and Borland C++ and includes my packet control
  program MPkt.
