OPERATING INSTRUCTIONS FOR CW-MAESTRO PROGRAM 

VERSION 1.0 (SHAREWARE VERSION)            October 1998



Welcome to my favorite CW sending program.  This shareware 
version provides the basic features you need to send perfect code.  
You don't need anything else.  However, this version has very limited 
logging, embedded command, and customization features although 
many of these operate sufficiently to demonstrate what the full 
featured version provides to registered owners.

For information about becoming a registered owner see Appendix B.  
This manual is written for the registered version.  Appendix C 
provides a description of the differences between the shareware and 
registered versions.

I have written this program to satisfy my own needs.   I wanted a program 
that was easy and natural to use with pop-up windows and which had the 
look and feel of a professionally written program.  I needed the ability to 
easily keep a log in a database without leaving the sending program, 
have the log automatically check to determine if I had previously 
contacted the station that I was calling (or thinking of calling), and  show 
me a record in a popup window of the last previous QSO with that station so 
that I would have instant recall of prior QSO's while sending.  I wanted to 
store any number of messages of any length and have the ability to 
customize keying, key assignments, display and other program 
characteristics.   CWM has added greatly to my enjoyment of amateur 
radio and I hope that you enjoy it as well.  The list of features in the 
following section provide a full summary of the program features.  The 
program continues to evolve and I hope to hear your suggestions for 
additional improvements.


Don Ehrlich	
K7FJ
538  Farrington  Road,  Port Angeles,  WA  98363
 
internet  ehrlich@olypen.com

INDEX


1.0	Features

2.0	System Requirements

3.0	Getting Started

	3.1	CWM Files
	3.2	Installation
	3.3	Connection To Transmitter

4.0	Starting CWM

	4.1	First Time Setup	
	4.2	Command Line Arguments
	4.3	Main Menu
	4.4	Using Setup Screens
	4.5	Speed Adjustment
	4.6	Keying Characteristics
	4.7	Assigning Custom Text Messages To Function Keys
	4.8 	Assigning Codes And Text To Keys
		
		4.8.1	Determining Dot-Dash Elements For Key To Send
		4.8.2	Direct entry of text by coding a key using "+"
	
4.9	Embedded Commands

5.0	Utility Setup

	5.1	Entering Values 
	5.2	Option Toggles

6.0	Logging

	6.1	Log File Utilities
		
		6.1.1	Selecting and Naming Log Files
		6.2.2	Backing Up Your Log Files
		6.1.3	Exporting Log Data
		6.1.4	Creating Text Files Of Log Data

	6.2 	Printing The Log



Index (cont.)

7.0	Tutorials

	7.1	Custom Text Message Tutorial
	7.2	Log Entry Tutorial
	7.3	Editing and Deleting Log Records




Appendix A		In Case Of Trouble
Appendix B		Registration Information
Appendix C		Comparison Of Shareware and Registered Versions



1.0  Features    (* indicates limited or not available in shareware version)

  Smooth type-ahead operation.  Sending speed from 1 to over 500 wpm.

  *User Defined Custom Messages.  Messages of up to 75 characters may 
be created and assigned to each function key.  In addition text up to 15 
characters may be assigned to most other keys, including lower case 
keys.

  *Embedded Commands   Message Calling, Text Insert, Serial Number, 
Speed set, message or file calling, and many others.

  *Reads from disk files as well as from keyboard entry.  Disk files used for 
input can contain embedded commands.  Great for code practice! 

  *User Defined Custom Key Codes.  Any dot dash pattern can be assigned 
to nearly any key on the keyboard and may define extra long spaces or 
other special timing effects.  

  Sidetone            Optional on/off. Adjustable sidetone frequency

  Flexible Setup  (date & time format, universal time offset, speed 
calibration, etc).  Also set dot and dash length, weight, space and word 
space length.   All setup information is stored and reloaded from disk 
when program is started.    Adjustable space settings permit Farnsworth 
timing.     

  S/N  including option of sending 0's as T's, 9's as N's in contest serial 
numbers.

  Data Entry Screens and Help options appear when needed.
 
  *Logging from within the program using a built-in database with search
criteria for call, qth, name, and other information.  Listing of log to
database or text files, management of separate logs under different 
file names, full log editing, and other features.

  *Logging from within the program can automatically check for prior entries
for the current call and provide previous QSO information in a pop-up
window while you are sending.

  Precision timing mechanism allows operation under Windows and is 
unaffected by CPU speed.  (Windows environment may interfere with 
keying through communications port and is not recommended.)

  Interrupt buffer allows you to pause while sending from the main buffer, 
immediately insert other text from the keyboard, and then resume sending 
from the main buffer


2.0  Requirements
IBM PC, AT, 386, 486, Pentium or compatibles.  Floppy or hard drive.
Monochrome, EGA, VGA


3.0  Getting Started

The CW-MAESTRO program consists of the CWM.EXE file together with 
setup and help files.  Only the CWM.EXE  and help files are required. 
Setup files contain custom keycode, message, keying characteristics, and 
other setup information that reflect your own preferences and the needs 
of your station. If the setup files don't exist when you install the system 
then  they will be created automatically once you start CWM for the first 
time and whenever you customize key coding, messages, and other  
functions.


3.1  The files:

3.1.1 CWM.EXE   

CWM.EXE is the sending program.  It creates all of the files that store 
operating characteristics (see 3.1.2 below) and the log files (3.1.4).  The 
help files, logo graphics files,  and this operating manual are the only 
other files provided with the program.


3.1.2 Files That Store Operating Characteristics

These files are not provided with the CWM programs.  They are created 
by CWM.

CONFIG.HAM      Contains last saved speed setting, sending 
characteristics, all of the choices you make when accessing the Utility 
screen, log file information, and other data.  It is revised whenever you 
change operating parameters.

CODEKEY.HAM    Contains the special dot-dash codes or text that you have
assigned to keys.  Example "bt" assigned to the ; key,
"sk" assigned to the ' key, and so on.    (Feature not available in 
Shareware version)

MESSAGE.HAM    Contains the special messages that you have defined 
for the function keys.  (F1 and F2 are the only keys available for 
messages in the shareware version.)

IMPORTANT!    Do not attempt to use a word processor to edit the 
CONFIG.HAM,  CODEKEY.HAM, OR MESSAGE.HAM files 
directly.  Any attempt to do so may interfere with the ability of CWM  
to use the information and could even prevent the  program from 
working.  (If you ever  suspect that this may have occurred then 
just delete the files and  let CWM build them again from scratch 
when you reenter the  necessary setup and message information.)


3.1.3 	Files That Store Help Information

Note:  All of the .HLP files can be read and printed directly from 
DOS.

Help File
Accessed From:

UTIL.HLP
<Ctrl>U Utility screen

MAIN.HLP
 Main Sending screen

LOGUTIL.HLP
 Log Utility screen

LOGEDIT.HLP
 Log Editing screen

LOG.HLP
 <Ctrl>L Log Entry screen

FIST.HLP
 <Ctrl>F Sending Characteristics screen

ENTERKEY.HLP
 <Ctrl>K Key customization screen

EDITMESS.HLP
 <Ctrl>Function Key message recording screen






3.1.4	Log  Files 

LOG       The default name for the log file is LOG.LOG.  The file named 
LOG.LOG (or other name you select) contains all of the log information.   
You may maintain several log files and select the current log using menus 
within the program.  Each separate log file is a data base and the 
program creates key files for each separate log file that you maintain.  
The four key files have the same name as that selected as the name of 
the main LOG file but have suffixes  .kcy, .kdy, .kny, and .kqy.  These key 
files contain sorted call, date, name, and qth information to allow rapid 
searching and listing of log data.  The log file name always has the suffix 
.LOG.

Note:  If the key files are lost  or corrupted but the main log file is 
preserved then, when first accessing that log file the program will 
automatically recreate the missing key files.

The name that you select for a log file cannot contain a suffix but 
otherwise there are no restrictions for the choice of names other than 
those imposed by DOS.  CWM will automatically add the suffix .LOG to 
the name you choose.  The name of the log may contain a drive and path 
prefix to allow access to logs not in the current working directory.  For 
example if you selected the name HOMELOG for your log file then the 
program will create the file HOMELOG.LOG and also the files 
HOMELOG.KCY, HOMELOG.KDY, HOMELOG.KNY, and 
HOMELOG.KQY.

To set the name of your log file press <CTRL-L> while in the sending 
mode to access the log data entry screen and then press function key F4 
to bring up the log utilities menu.  Press F for File Utilities and finally N for 
name.  All log files in the current directory will be displayed for reference.

3.1.5  Graphics Files For Introductory Screen

Three files with the .GRH suffix provide introductory screen graphics.  If 
these files are not available CWM will substitute another view and 
operate normally.




3.2  Software Installation:

3.2.1	Config.sys File

	There must be a statement in your config.sys file that sets the 
number of file handles to a value greater than 25.  You probably already 
have a config.sys file and it may already have the "files=##" statement 
where ## is 25 or greater.  If not, then add the line "files=25" to your 
config.sys file and reboot your computer.  Your DOS manual can help you 
with config.sys file functions if you need more information.


3.2.2	Hard Drive Installation:

If using a hard (fixed) drive then create a directory for the files and copy 
all of the files into that directory.  For convenience it is recommended that 
a batch file be created and placed somewhere on the DOS path so that 
the program can be started any time just by typing a short name of your 
choice (the name of the batch file).

3.3  Connection to the transmitter

The program provides output to the DTR  pin of either the COM1 or 
COM2 communication connectors. For 9-pin connectors this is pin 4,  for 
25 pin connectors it is pin 20.

The keying signal depends on the computer hardware but typically 
changes from about -10 volts (key up) to +10 volts (key down).  COM2 is 
the default choice but you may change the selection to COM1 using the 
Utility screen. 

Most solid state rigs may be keyed with a simple transistor-relay interface 
to the computer.  The ARRL handbook suggests some circuits to use. 
One way of making the connection is suggested below for those who like 
to build their own.  
                                              + 9 Volts
                                                  |
                            ____ K1*  coil  ______|
                           |   |___CR1____|
                           |
                           C            * K1 contacts connected
DTR Line-------- R1----- B                to transmitter key jack.
(pin 20 or 4)              E
                           |
                           |
(Pin 7)  Ground____________|_______________ Ground & -9 Volts


CBE represent the collector, base, and emitter of an NPN transistor such 
as 2N2222.   K1 is a reed relay selected to operate from 9 volts and have 
a coil current of less than 50 ma or so.  R1 is a 10K resistor and CR1 is a 
general purpose silicon diode such as 1N914.  CR1 anode is connected  
to the collector of the transistor and cathode is connected to +9 volts.

The relay contacts are used to key the transmitter.  Radio Shack carries 
all components.  I found that a reed relay with a 12 volt rating was 
sensitive enough to work in this circuit powered by a 9 volt battery.  Of 
course, you can use a power supply providing more than 9 volts, but I 
found that the use of a 9 volt battery was convenient.


4.0 Starting CWM

To run the program just enter the directory where the program resides
and type 'CWM' followed by the <Enter> key.  When the copyright notice 
appears then press any key to switch to the send mode.  At this point any 
character you press results in that character being sent.   The `CWM' 
command can be followed by optional characters as described below in 
4.2 but normally these should not be necessary.


4.1 First Time Setup:

The very first time you start up the program there will not be a config.ham 
configuration file available to CWM to use for initialization.  In this case, 
immediately after the introductory screen CWM will create this file with 
default values for speed, sending parameters, file name, and other 
characteristics.  You will see a notice that the Config.ham file is being 
created.

Once you have the program running for the first time you should access 
the Utility screen with <Ctrl>U and set any of these conditions to those 
that fit your preferences.  This is especially true of the output port if you 
are planning to use COM1 instead of COM2 (the default).  See section 
5.1.


4.2 Command Line Arguments:

Some special characters (an argument) can be added after `CWM' to 
cause CWM to behave is a special way.

4.2.1  `Mono' and `Lap' Arguments:

The argument "LAP"  can follow the "CWM" command to cause the initial 
color settings to be white on black.  The argument "MONO" will cause the 
initial colors to be black on white.  (See examples below.)  These colors 
will assure a readable screen for laptop or monochrome monitors that 
might otherwise interpret the default color settings into a form that could 
not be read.  One of these arguments could also be used in the event that 
you have accidentally set the foreground and background colors to those 
that do not display well on your color monitor and, once set, make it 
impossible for you to see well enough to reset the colors using the cOlor 
setup screen.  (See In Case Of Trouble, Appendix A).

( Examples:  CWM MONO     or    CWM LAP )


4.2.2  `/T'  Timing Argument:

The normal means of timing characters is by using an internal hardware 
clock in the computer to maintain a precise measure of the length of each 
element, character, and word space length that does not depend on CPU 
clock cycles.  With this normal mode of timing CWM can send precision 
code even when operating within the Windows environment or when the 
CPU is managing other programs in the background.

However, it is possible that some computers will not have compatible 
hardware clock signals available or some genius may design future 
computers without the necessary compatibility.  In this case an alternate 
timing mode may be used by starting the CWM program with the `/T' 
argument after the `CWM'.  This will force the timing to be derived from 
the CPU clock and that will work with any computer ... but with some 
compromises.

If the /T argument is used then CWM sending speed will depend on the 
speed of the computer and must be calibrated by using the Utility screen 
to set the `Recalibration' toggle.  Also, CWM will no longer run under 
Windows which periodically interrupts the CPU for other background 
tasks.  Even if running under DOS there may be timing problems if there 
are background programs running (TSR's).  See Appendix A for 
troubleshooting information.


4.2.3  INTRO  Argument:

The INTRO argument suppresses the introductory copyright notice and 
graphics presentation.



4.3  Main Menu

Any time the Alt, Ctrl, or Shift keys are pressed while in sending mode 
the main menu appears at the bottom of the screen.  The separate 
commands  are activated by pressing the first character of the command  
while pressing the Alt, Ctrl, or Shift keys.

Note:  The examples in this manual refer to the use of the Ctrl key 
such as <Ctrl-B>.  In all such examples either the Alt or Shift keys 
may be used instead of the Ctrl key.


Main Menu Commands 

Buffer Clear
Clears the type-ahead buffer and erases all unsent characters from 
the screen

Clear 
Screen
Clears the screen and places the cursor at the top.  When the screen 
is cleared the type-ahead buffer is also cleared and all sending stops.

Fist
This old fashioned term for the way your sending sounds is the name 
of the screen that allows you to set the spacing between dots and 
dashes, the length of time  between characters, and the length of time 
between  words.

Help
Displays a brief summary of what the main menu commands do ... 
similar to this listing.

Interrupt 
Buffer
You may interrupt sending from the buffer at any time by pressing  
<Ctrl>I which will open a window in the center of the screen so that 
you can insert a short message.  This is useful during a long 
transmission to ask the other station if you are still being copied 
easily.  Sending from the main buffer resumes when you exit the 
interrupt buffer mode.

Key Code
Displays a screen allowing you to create definitions of what dots and 
dashes a key is to send.  (Not available in shareware version)

Log
Displays a screen for recording the call letters and other log data for 
the  station you are sending to.  Once the station call letters have 
been   entered CWM will automatically send those call letters when 
the embedded command {C} is encountered.  See Embedded 
Commands later on.  Suggestion: Assign  the message '{C}'  to a 
function key and then whenever you press that key the currently  
logged call sign will be sent.
See the Log tutorial in section 7.2 for more information.

Messages
This key will cause the Messages Reference Menu to be displayed.  
This is a toggle, and pressing it again  will make the Messages 
Reference Menu disappear.  The  Messages Reference Menu is a 
listing across the bottom of the screen that shows you what messages 
are assigned to each function key.  If the automatic log search feature 
has identified a prior QSO with the currently  logged station then data 
from this prior QSO is  accessed as a third option of the Menu toggle 
key.  (Automatic Log Search not available in shareware version)
Note:  If you press <Ctrl>M while sending then the Messages 
Reference Menu will not appear until the next space occurs in your 
sending ... to prevent delays in the code characters being sent.

Number
Causes the current serial number to be sent.

cOlor
Pressing Ctrl-O presents a screen for selecting the colors of the 
display.  Colors for typed text, screens, border,  and header may be 
set independently.  Monochrome monitors  may respond in brightness 
or shading to these settings.

Pause
Causes all sending to stop while you type ahead.   A flashing 
'PAUSE' sign appears at the top of the screen whenever you have 
paused.  This same key toggles the program back into the sending 
mode.

Tone
Causes the sidetone to toggle on and off. A flashing `TONE' sign 
appears at the top of the screen whenever the sidetone is off.

Utility
Displays the utility setup screen.  This screen allows you to set the 
way the program displays date and time,   the sidetone frequency, 
your call letters, and many  other things.  Note:  If you press <Ctrl>U 
while sending then the Utility screen will not appear until the sending 
buffer is empty.

Xmit
Disables/Enables the keying of the transmitter.  A flashing "KEY" sign 
appears at the top of the screen whenever the keying is off.


4.4  Using Setup Screens 

The following screens may be used to enter setup information that will be 
permanently stored in disk files for use each time the program is started.

Screen
Access and Function
Notes

Color
<Ctrl>O     Sets display 
colors.
Saves to config.ham file upon exit from 
screen.

Fist
<Ctrl>F      Sets element and 
character time & spacing.
Saves to config.ham file upon exit from 
screen.

Key
<Ctrl>K      Sets dots and 
dashes or text to be sent for 
any key.
Saves to codekey.ham file upon exit 
from screen.

Log
<Ctrl>L      Enter log data, 
edit log, display log contents, 
and other log functions.
Saves to log file only when deliberately 
saved using the F2 key or the <SAVE> 
button.  Also saves current frequency, 
mode, and power settings to the 
config.ham file to be used as default 
values until changed.

Message
<Ctrl><Function Key>  Stores 
a custom message for the 
function key pressed together 
with the control key.
Can save up to 75 characters for each 
message.  Messages are stored in 
message.ham file.  (Only function keys 
F1 or F2 may be programmed in 
shareware version.)

		

4.4.1	Moving From Item To Item on Data Screens

Use the Tab and Shift-Tab keys to step forward and backward between 
items on  the screen.  The PgDn, PgUp, and arrow keys also move you 
forward or  backward through the screen.

You may exit from the screens at any time with either the [Esc] or [Enter] 
keys.  The [Esc] key causes exit without saving any of the changes.  
Pressing the [Enter] key saves all of the changes.  As an alternative you 
may tab down to the <OK> position and press enter, which saves all 
changes, or <Quit> which does not.  The <Help> option will open a 
window explaining each option.



4.4.2	Entering and Editing Information

4.4.2.1  Typing In Information

The first keystroke pressed after entering a field erases any existing 
information in that field.  To edit existing information first press an arrow, 
home, or end key to position the cursor to the point you want to edit and 
then type in changes.


4.4.2.2	Buttons For Toggling Some Options

Buttons appear at the bottom of screens for functions such as Saving, 
Exiting, Help, or access to additional menus.  These buttons may be 
activated by either tabbing through the screen until the button is 
highlighted and then pressing Enter, or by pressing the Function Key 
identified in the label of the Button.  

Note that if have already started editing a field then the applicable 
Function Key must be pressed twice to activate it  .. the first time to exit 
the field and the second time to activate the button to which the function 
key is assigned.


4.4.3	Saving The Screen Information

For most screens information entered will be saved to disk file upon exit 
from the screen.  The exception is log data, which is saved to the log file 
only when instructed by using the <Save-F2> button or control key.


4.4.4	Help Information

A HELP screen appears whenever the F1 key is pressed while in any of 
the screens.  To exit the HELP screen press ESC.


4.5  Speed Adjustment
  
The sending speed is adjusted by pressing either the '+' key to increase 
speed or the "-" key to decrease it.  The '=' key may be used instead of 
the '+' key  for the convenience of those using computers that do not have 
a separate '+' key. 

You can watch the speed indicator in the upper right corner of the screen  
change as you hold down one of these keys.  The speed will not  
automatically be saved to the CONFIG.HAM file.  However, if the Utility 
screen is accessed and then the Utility setup is saved (whether or not any 
of the  values were changed) then the current speed setting is also saved 
to file  and will be in effect the next time the program is run.  

Note:  The '+' and '-' speed changing keys are not used in 
combination with the Alt, Ctrl, or Shift keys.

For information on calibrating the display speed see section 5.0, Utility 
Setup.


4.6  Keying Characteristics (Fist Setup Screen)
  
A setup screen that adjusts dot-dash, word space, and other 
characteristics may be accessed from the main menu by pressing Ctrl-F. 
This 'Fist' screen allows you to set the keying weight (time between dots 
and dashes), the length of the space between characters, and the length 
of word spaces.

The basic unit of measure for these settings is the length of one dot.  For 
instance, a dash length is typically set to 3 dot lengths and a word space 
is usually set to 7 dot lengths.  A weight of 1 causes 1 dot length between 
elements.  All settings may be set to fractional values such as 0.9 or 3.2. 

Default values for these settings are those recommended by the ARRL 
handbook and provide the best readability at higher speeds.  Some may 
feel that, at lower speeds, a reduction in weight from a value of 1 to .8 or 
.9 provides a smoother sound, and some transmitters may induce delays 
in keying that can be compensated by reducing the weight.  In general, 
though, it is better to stick very close to the standard settings.

For code practice using Farnsworth timing (extra long pauses between 
characters) set the character spacing to a value much larger than the 
default value of 7.  This will exaggerate the spacing between characters 
which are sent at a code speed much higher than the average speed, a 
technique many believe enhances learning.


4.7  Assigning Custom Text Messages To Function Keys

Any function key can be programmed with a message of up to 75 
characters (only F1 and F2 keys in shareware version of CWM).  The 
stored message is sent by pressing the applicable function key by itself ... 
NOT in combination with Alt, Shift, or Ctrl keys.

To enter or edit a message for one of these keys press the Ctrl or Alt key 
in combination with that function key.  This will bring up the Message Edit 
screen.  This screen allows you to:

*	Enter the message which can be up to 75 characters and  contain  
embedded commands (See 4.9 below for more about embedded 
commands).

*	Enter a short descriptive label for this message.  This label will be 
displayed as a convenient reference whenever the Message menu is 
displayed by pressing <Ctrl-M>.

(Note: Text stored on disk files of any length may be also be used as 
storage of custom messages or for code practice.  See  the {Fname} 
embedded command description in section 4.9  (not available in 
shareware version).  

The registered version of CWM allows short messages to be assigned to 
other keys as well.  See section 4.8.2. 

The following stored messages are recommended.  Assign them to 
function keys of your choice or create your own versions.  (Section 4.9 
provides more information about the embedded commands shown in the 
following examples.)

{L}	When typed immediately after the call letters of the other station 
        this embedded command will start a log entry for that station.  The 
        station call letters will appear in the header and on the log 
        entry form when it is accessed with <CTRL>-L.  In the registered
        version CWM will also check the log to see if the call has been
        previously logged and, if so, will display information from the
        prior QSO in a pop-up window.



{X}{SU200}{B30}{L}{SD200}{X}	Begins creation of a log entry and 
	checks for a prior contact for a station call without going on the air 
	with the call.  The series of embedded commands:
	
        {X} first toggles off transmitter keying with an {X}
        {SU200} then increases keying speed by 200 wpm to make sure 
          keystrokes are processed very quickly
        {B30} accepts a keyboard input of the other stations call
        {L} starts a log entry and activates a search of the log for any 
          prior contacts with the station.
        {SD200} reduces sending speed by 200 wpm to the original 
         value.
        {X} toggles transmitter keying back on.

{C}	Sends other stations call once a log entry has been started for that 
	station.  The call appears in the header whenever a log entry has 
	been started.

{DE mycall}	Sends your call.  Program this one next to the key to which 
	you have programmed {C} because you usually use them together.

CQ CQ CQ  DE yourcall  yourcall  CQ CQ CQ  DE yourcall yourcall 
{P100} {Mn}	

The CQ above may be programmed to any Function key.  {P100}  
causes a delay of 10 seconds.  Following the pause {Mn} calls for 
the message assigned to function key n to be sent.  In this case n 
is the number of the function key to which the CQ is assigned and 
so the message continues calling itself over and over with a 10 
second pause each time to listen for a reply.  You may substitute 
{B1} for the {P100} which results in the CQ being repeated only 
after you touch the space key.

A more complete explanation of embedded commands is presented in the 
following section.


4.9  Embedded Commands

Embedded commands are designed to be written into the text of custom 
messages.  However, instead of being sent as code along with the rest of 
the message, they are recognized by CWM as a command to perform an 
operation such as incrementing the serial number, pausing for keyboard 
input,  or changing sending speed.

The program recognizes the start of embedded commands by the 
presence of  a special character.  The special embed start character is 
normally the {   character but can be changed to any character of your 
choice using the  Utility Screen.  The last character of the embedded 
command is followed by the embed end character, normally the matching 
} character.  The start and end characters must be different. 

Any  embedded command can be entered directly from the keyboard.  To 
do so just type the embed start character, the embedded command, and 
the embed end character just as you would if embedding it in a custom 
message.  As soon as you press the embed start character the embedded 
command  reference list pops up in case you need a little coaching ... and 
then disappears once the embed end character is entered.  Normally, 
however, you will use embedded characters as part of custom messages 
assigned to one of the function keys or as part of a file used as input to 
CWM.




EMBEDDED COMMAND SUMMARY

Note:  In the following examples the small 'n' signifies a number that you 
enter.

{Mn}
Causes insertion of message number n. (n between 1 and 12)

{Ffname}
Causes the program to search for a file with the name you specify and 
start sending the contents of that file.  The file does not need drive and 
directory path prefixes if it is in the  same directory as the sending 
program.  The source file may contain embedded commands such as 
speed changes but cannot contain the {Ffname} embedded command to 
get input from some other file. (Not available in shareware version)

{Sn}
Sets the speed to n WPM  (n between 1 and 999)

{SUn}
Increases speed by n WPM (n between 1 and 999)

{SDn}
Decreases speed by n WPM (n between 1 and 999)

{Gn}
Inserts a gap of n dot lengths before the next character to be sent.  A 
value of 3 results in a normal character space (and therefore has no 
effect) but increasing the value increases the length of time prior to the 
next character being sent in order to give greater emphasis  to that 
character.  For example, if your call letters are K5EEI you might wish to 
program one of the function keys to send K5{G7}E{G7}E{G7}I and use 
that function key to send your call so that the letters will be separated a 
little more than usual.

{Pn}
Causes a pause of n tenths of a second.  Value may be up to 9999.  
{P100} will cause a pause of 10 seconds.  A moving scale appears 
during the pause to indicate elapsed time.

{Xn} or 
{Kn}
Causes key down for n/10 seconds  ( n between 1 and 999)

{Bn}
Break for keyboard entry.  The program stops sending and awaits entry 
from the keyboard.  The break is canceled automatically n/10 seconds 
after your last key is pressed or may be canceled anytime by pressing 
the <Esc> key.  For example, a custom message could read "UR RST 
{B20} HR IN WALLA WALLA".  The program will pause after sending 
"RST"  and wait indefinitely for you to start typing something.  Once  you 
have  entered the other station's RST the program will continue on with 
the "HR IN WALLA WALLA" text without  requiring you to cancel the 
break with the <ESC> key.

The value of 20 sets the pause time to 2 seconds. This means that, while
typing in the RST value (example: "579") you must type the 5 and the 7 
and the 9 quickly enough so that  no more than 2 seconds elapses between
each keystroke.  Otherwise the program may continue on with the "HR IN WALLA
WALLA" before you had finished entering the "579".   Set n to a higher
or lower value according to your typing speed.

You could place a {BB} just before the {B} to cause the  computer to 
beep-beep at you if you want to be notified that  keyboard input is 
needed.  (Some of us are more absent minded  than others).

{BB}
Causes the computer speaker to beep-beep at you.  May be used as a 
chime in some custom messages where you need a reminder such as 
the  example in {B} above.  It is handy when using a looping message 
with a long time delay between loops (such as a CQ with 20 second wait 
before restarting) ... you can place the {BB} 5 seconds before the {Mn} 
command to alert you that you are about to send the CQ again.  This 
would occur if the  following were stored as message number 1 
(assigned to function key #1)
            CQ CQ CQ DE K5xx K {P150}{BB}{P50}{M1}
{P150} causes a 15 second pause ... followed by a beep-beep from  the 
computer speaker caused by the {BB}...followed by a 5 second  pause 
caused by the {P50} command ... followed by a repeat of the  whole 
message as the {M1} causes the message to call itself again.

You could replace the {P150}{bb}{50}{M1}  with  {B1} which would cause
the program to pause after the CQ until you pressed any key to manually
cause message M1 to run again.   

{N}
Sends current serial number   

{I}
Increments serial number

{D}
Decrements serial number

{C}
Sends call letters of other station currently logged

{L}
Causes the log to be searched for prior contacts with the station whose 
call immediately precedes the {L}.  Used by typing {L} immediately (no 
intervening spaces!) after typing the call letters of the other station.  
Easily used by assigning {L} to a function key as a stored message and 
then, after typing the call letters of the other station, press that key to 
initiate a search.  (See 6.0 and 7.2 for more Log Information).


4.8  Assigning Codes And Text To Keys    (Not available in shareware ) 

4.8.1  Determining Dot-Dash Elements For Key To Send (Registered version
        only)
You may wish to send special characters such as dah-di-di-di-dah  di-di-
di-dah-di-dah, di-dah-di-dah-dit, and so on.  You can define any 
combination of dots and dashes you like, assign them to just about any 
key (including the arrow keys), and have them display on the screen with 
a symbol of your choosing.  These strings of dots and dashes can contain 
extended dot spacing or complete character gaps if you wish.

To program a key just press <Ctrl>K from the main menu  to gain access 
to the key definition screen and press the key that you intend to program.  
Fill in the blanks to define the dot-dash code and the symbol to show on 
the screen when the key is pressed.  The key information will be saved to 
the CODEKEY.HAM file when you exit the screen and be reloaded 
automatically whenever you start the program. 

Default key code assignments are:

                [  =  kn       ] = sk      ; = sk     ' = ar  

Note:  Keys reserved for special functions such as the speed control or 
embedded command delimiter keys cannot be programmed.


4.8.2	Direct entry of text by coding a key using "+":

Assign text to be entered into the buffer by first entering a + followed by 
the characters you wish to send.  This causes any key to behave like a 
function key except that the buffer for the key is limited to 15 characters.  
If you store the message +{Ffilename} then, whenever the key is pressed 
the characters stored in the file named filename will be sent.  This 
effectively extends the number of buffers to approximately the number of 
keys on the keyboard and the 'buffer' (actually a separate file you have 
prepared earlier) can be of any length. 

Example:  Assume that, before starting CWM, you have created a text file 
and saved it with the file name CQ.TXT.  CQ.TXT contains the characters    
CQ CQ CQ DE mycall mycall  CQ CQ CQ DE mycall mycall  


Now, assign the following to the ! key by pressing <Ctrl>K and then the ! 
key ( <Shift>1 on most keyboards).  In the first field of the key entry 
screenenter  +{FCQ.TXT} . That is 10 characters including the + and curly 
brackets.  After storing this key coding and exiting the screen you can 
send a CQ by pressing the ! key.  That causes the key to issue an 
embedded command calling for file input from the CQ.TXT file which 
is where you have stored the characters to send CQ.  See the manual for 
a description of how embedded commands work. 

Of course, you can store short key sequences such as  +DE mycall  to a 
key without using embedded commands for external file input.

You may assign these key sequences to most of the lower case keys as 
well.  In the examples above you could have assigned the CQ to the lower 
case c key and the  DE mycall   sequence to the lower case d  ...or almost 
any other key.


5.0  Utility Setup

Note:  See section 4.4 for general instructions on using the screens.

A number of setup parameters may be set from the Utility Setup screen.  
The first 7 items all accept a typed-in entry.  For example the characters 
you wish to use for embed start and embed end symbols may be entered.

The options in the center section of the screen simply toggle a choice on 
and off by pressing the <Space> bar.  For example, the time display will 
toggle from Local Time to Universal time, and back again.

A summary of the options is listed below.  The following is similar to the 
help screen that appears when you select the help option.


5.1	Options Requiring A Value To Be Entered

EMBED START AND END CHARACTERS:  These are the symbols that 
are used  to identify the beginning and end of an embedded command.  
Defaults are { and }.  Note that these two character must be different. 

HOURS OFFSET TO UT:  The number of hours that must be added to  
local  time to obtain Universal Time (UT).  Default is 0.  Value may be 
either positive or negative.

SERIAL NUMBER: The current value of the serial number counter. 
Displays the current value and allows setting to a beginning value of your 
choice.  The serial number counter is used during some contests. 
Embedded commands [SN], [I], and [D] display, increment, or decrement 
the counter.  Default is 0.

DISPLAY WPM:  Allows you to manually calibrate the sending speed that 
is displayed in the upper right hand corner of the sending screen.   For 
instance if you know that the program is currently sending at 20 wpm but 
the display shows another value for sending speed then you can set the 
DISPLAY WPM: value to 20 to assure an accurate display.

SIDETONE FREQUENCY: Enter the frequency that you want for the
sidetone.  Default is 800 Hz.

PORT ASSIGNMENT:    Choose COM1 or COM2.  Selects the connector  
where  the send signal will appear.  The signal will appear at  the  pin 20 
for 25 pin connectors or pin 4 of 9 pin connectors.  Voltages depend on 
your computer hardware but generally will be about  -10 volts key up and 
+10 volts key down.


5.2	Toggling Options

DATE FORMAT:   Controls the date display at the top of the screen. 
Choose either month-day-year (MM-DD-YY) which is commonly used in 
North America or day-month-year (DD-MM-YY) as normally used 
elsewhere.  Default is MM-DD-YY.

TIME FORMAT:   Controls the time display at the top of the screen. 
Choose either local time (LOCAL, as determined by the clock in your PC) 
or universal time (UT).  Default is LOCAL.

SIDETONE AT STARTUP:     Choose ON if you want the sidetone when 
you first start up the program.  Whatever you choose you can toggle the   
sidetone on and off anytime with CTRL-T.  Default is ON. 

RECALIBRATE:  Recalibration is necessary if you have started CWM  
with the /T argument (section 4.2.2) to force timing using microprocessor 
clock cycles.  The preferred timing method (no argument after the CWM 
command) uses a hardware clock and recalibration can not be done.  
However, with either timing method you can set the speed display as 
described above for WPM DISPLAY.

If Recalibrate has been selected then, upon exit from the utility-setup 
screen, the computer will measure its own speed and set variables 
appropriately to calibrate sending speed.  This should be necessary only 
if the CPU speed of the computer has been altered or when installing the 
program on a different computer.  It is done automatically whenever the 
computer is turned on with the  /T argument and a config.ham file with 
setup information is not in the current directory.  Default for recalibrate is 
NO.  If the DISPLAY WPM: value has been changed then the 
RECALIBRATE option is disabled.  

To exit the Utility screen either tab down to the <OK> button or press 
ENTER at any point after you have entered data in a field and tabbed to 
the next field .  Either of these exit methods will result in storage of the 
selected parameters in the disk file CONFIG.HAM for automatic 
installation the next time you start up the program.


6.0  LOGGING

The log screen is accessed by pressing Ctrl-L.  Log functions include:

  Entry of other station call as you send while on the air or 
without sending,  by typing {L} immediately after his call or by 
using embedded commands (see examples).
 
  Automatic lookup of any prior QSO's with currently logged 
station.  If found, information from the last prior QSO pops up 
for reference while you are sending. (Not available in 
shareware version)
 
  Listing to screen of all log entries, sorted by date.
 
  Listing for specific Call, QTH, or Name show all log entries 
where the Call or QTH contain the string of characters that you 
have given as search criteria.   You may therefore conduct a 
search even when you don't remember exactly what you are 
looking for or by call prefix, state, city, etc.
 
  Select the name of the file to be used for log data.
 
  Backup log file
 
  Automatically checks for duplicate log entries where the same 
call is being logged on the same day.
 


  Automatic entry into log of current date and time.  Start time is 
initially the time when a new call is first entered to the log 
screen.  The start time remains fixed thereafter but the end time 
is refreshed each time the log screen is accessed. The last 
entered Mode, Power, and Frequency are retained and 
reentered automatically as defaults to minimize the amount of 
data entry you have to do.  Log data may be edited before 
sending it to the log file.
 
  Downloading of log data to separate files in text or database file 
formats for use with other database or word processors.
 
  Editing or deletion of entries previously stored in the log file. 



6.1	Log File Utilities

The file options menu provides the following choices:

  Selecting a log file to use or naming a new one
  Backing up the currently selected log
  Creating a new file in database format for use with external 
    database managers
  Creating a Text File with all of the log information in it

Access this menu from the main sending screen by pressing <Ctrl>L for 
the log entry screen and then pressing function key F4 for the log utilities 
menu.  Finally, press F for file utilities.


6.1.1	Selecting Or Naming A Log File 

From the file utilities menu (see above) press N.  If there are any log files 
already in the current directory they will be listed in a window.  You are 
invited to enter the name of a log file.  If a log file already exists with that 
name then it will become the log file that CWM will use.  If no log file 
already exists then a new empty log file of that name will be created.


6.1.2	Backing Up Log Files

From the file utilities menu (see 6.1 above) press B.  You will be prompted 
for a name to use for the backup log file.  After entering the name of the 
backup file CWM will create a duplicate of the current log file with the new 
name.  

CWM will continue using the currently selected log file.  Creating a 
backup log does not cause CWM to switch over to using the new log file.


6.1.3	Exporting Log Information To 	Another Database

You may wish to use your log data with another database manager or a 
spreadsheet program.  Although most database managers save 
databases in their own special format they will all import data in comma 
delimited format.  CWM creates such a file where each log record ends 
with a carriage return and each field (call, name, qth, etc) is separated 
from other fields by a comma.  Each field is surrounded by a double quote 
indicating to the importing database program that the field is in text 
format.  There are 16 fields.  This is not something for the faint of heart. 
If you really want to do this it is suggested that you create a small log file 
and then create from it a database format file as described below and 
look at the database file with your word processor to be sure you 
understand what is in it and how it is organized.  Then follow the file 
import instructions provided with your database manager.

From the file utilities menu (see 6.1 above) press D.  You will be 
prompted for a name to use for the database file.  After entering the name 
of the database file CWM will then ask you which data you wish to appear 
in the file.  You can select:

All		Will download all log information beginning at a date 	
		that you specify

Call		Downloads data for only those calls that you specify

Name		Downloads data for only those names that you 
specify

Qth		Downloads data for only specified qth


6.1.4	Creating A Text File Of Log Data

A text file may be created by pressing from the file utilities menu.  
The text file may then be edited and printed using your word processor.  
The procedure is exactly the same as that described for creating a 
database file.  The resulting text file presents each record in two lines and 
some fields are shortened if necessary to fit on those two lines.

6.2	Printing The Log

CWM does not provide for direct printing from within the program.  
Instead, first create a text file as described above and then print it from 
DOS or from within your word processor.


7.0	TUTORIALS


Start these tutorials while in the sending mode.  The actual keystrokes are
shown to the left of the paragraphs which provide the explanation for what
you are doing.  <BackSpace> indicates the backspace key, <Enter> 
indicates  the Enter key, <space> indicates the space key, etc.  
DUMMYNAME and other capitalized words in the left column should be 
entered literally as shown.   Ctrl-x indicates the Ctrl key pressed at the 
same time as the key indicated.   (Example Ctrl-L indicates the Ctrl key 
pressed while holding down the L   key).


7.1	Custom Text Message Tutorial


This tutorial will create the custom message {L}  and assign it to 
function key F2.  This is the embedded command that, when typed 
immediately after a stations call letters, starts a log entry for that 
station and also searches the log for any prior contacts with that 
station.   By assigning this message to function key F2 it will only be 
necessary to press F2 following the call letters instead of typing it 
out each time.

Begin by pressing the control key and function key F2 at the same time to 
access the screen that allows you to create and edit custom messages.

  <Ctrl-F2>   
             
Enter {L}. Then press the TAB key.

  {L} <TAB>

The cursor advances to the label field.
                 
Create a label for the function key by typing Log again followed  by the 
Enter key.  Note that the label field is for your reference ... you can put 
anything that you wish into it.

Log<Enter>
                 
The Message programming screen disappears and you are back in 
sending mode.

Turn on the message label screen at the bottom of the screen.  Ctrl-M 
toggles the Message Label  listing at the bottom  of the screen on and off.

<Ctrl-M>

You should see the effect of programming the F2 function key.  The label 
you entered should appear below the F2 position of the display.  Now 
make sure the screen is clear by pressing the <Ctrl-C> key combination.

<Ctrl-C>



7.2	Creating A Log Entry

Note:  Before starting this tutorial be sure that the F2 key has been 
programmed with the custom message  {L}  .   If this has not been 
done then follow the tutorial example of 7.1.

Assume that a station K0ABC has just responded to your CQ.  When you 
answer the first thing you type is K0ABC DE mycall ... right?  Instead of 
doing that you could type K0ABC followed immediately by the F2 function 
key and then the 'DE mycall'.  Don't do that now.  First,  lets see what 
happens when you type just his call followed by the F2 function key.
		
K0ABC<F2> 



You might have seen a brief screen flicker but not much seems to have 
happened.  Actually, you have just started a log entry for a QSO with 
K0ABC.  If this were a real QSO you would just continue sending after 
pressing the F2 key and switch to the log later when you had the time.  
But you are not really sending now so go ahead and bring up the Log 
screen with the Ctrl-L key combination.

<Ctrl-L>
The Log screen appears with K0ABC already entered.  The starting time 
(the time when you first pressed F2) is also there together with default 
values for Frequency,  Mode, and Power.  An ending time is also shown 
but this is updated to current time each time the log screen is accessed.  
After a few  moments press Enter to exit the Log screen.  Then press Ctrl-
L to call up the Log screen again.

<Enter><Ctrl-L>

The Log screen reappears.  Note that the call letters are still there.  If 
more than a minute has passed since the log was initialized then you will 
notice that the End time has been revised to the current time.  Chances 
are that, for most QSO's, you will not have to enter the start or end times 
at all. Also, the Frequency, Mode, and Power fields will be those that were 
last entered because they are stored in the CONFIG.HAM  file each time 
a log entry is stored.  If you don't change these conditions the default 
values will be those that you want without having to re-enter them.

Let's fill in some of the other data for this imaginary  QSO.  Tab over to 
the QTH field and type in DUMMYVILLE.

<Tab>DUMMYVILLE

Note:  If you made the mistake of hitting Enter after typing the QTH 
the Log screen will have disappeared and put you back into the 
normal send mode.  If that happened just press Ctrl-L again to get 
back to the Log screen.  

For practice navigating the Log screen use the up and down arrow keys 
and the PgUp, PgDwn keys to move from field to field.  These keys move 
the cursor around from field to field in the same way as the <Tab> and 
<Shift- Tab> keys.

NOTE:  Notice that the fastest way to get to the buttons on the 
bottom of the screen from the upper left corner Call field is to press 
the PgUp or Up-Arrow key to tab backwards to the bottom right of 
the screen.

Arrows, <PgUp><PgDn>

By now you should be navigating the Log screen pretty well.  Move to the 
Name field and type in BILL.

BILL

Move to the Frequency field and type in 7050

<Tab><Tab><Tab><Tab><Tab>
<Tab>7050

Then move to the Power field and type in a value of 150

<Tab><Tab>150

Finally, go to the comments line just below and enter some gibberish of 
your choice such as "UNCLE BILL IN DUMMYVILLE".

<Tab>UNCLE BILL IN DUMMYVILLE

Finally, it is time to save this log record to the file.  Tab to the <File Save> 
button at the bottom of the screen and press <Enter>.

<Tab><Tab><Enter>

OK ... When you pressed <Enter> the Log screen disappeared and you 
are back in normal send mode.

Let's pretend that it is another day and you have contacted K0ABC again.  
As you did before type in his call at the left side of the screen (or any 
other place as long as it is after a space) and then immediately press 
function key F2 to invoke the embedded Log command.

K0ABC<F2>

Notice that a window opened at the bottom of the normal sending screen.  
This alerts you that there was a previous QSO with K0ABC and shows 
you a summary of the data from the most recent contact.  You can use it 
for a reference as you continue talking to him.  (Everybody will think you 
have such a wonderful memory for QSO trivia.)   This feature is not 
available in the shareware version.


There is another way to initialize a log entry and do the same checking for 
a prior QSO.    First, access the Log screen and clear it of information.  
<Ctrl-L> brings up the Log screen, <PgUp><PgUp><PgUp> tabs 
backward to the "Clear" button, and <Enter> activates the button to clear 
the screen.

<Ctrl-L><PgUp><PgUp>
<PgUp><Enter>

After clearing, the Log screen is still there and the cursor is in the first 
field  ready to enter the call letters.  Type in K0ABC and press the Enter 
key.

K0ABC<Enter>

The Log screen disappears and you have returned to the main send 
screen.  The window at the bottom shows you information from the 
previous QSO with K0ABC just as it did before when you used the F2 key 
with the  embedded {L} command.
			
NOTE:  It is easier and faster to clear the Log screen by entering a 
single space in the Call field and pressing the Enter key.  The 
single space erases any prior call letters and, because all other 
information is deleted whenever a  blank Call field is created ... the 
effect is the same as when the Clear button is activated.  Pressing 
the <F3> key would also clear the screen.

Now that you are back in the sending mode with a window open at the 
bottom with prior QSO information in it you may be wondering if the Ctrl-M 
screen toggle still works.  Try it now by pressing Ctrl-M a few times.

<Ctrl-M><Ctrl-M><Ctrl-M>

The previous QSO information now appears as a third option for the Ctrl-
M menu toggle.  When there is no previous QSO information for the 
currently logged call letters there will just be the two Ctrl-M menu options 
.... (1) A full screen with nothing showing at the bottom  and (2) the 
Message reference showing the labels for the messages you have 
programmed for the Function keys.

One more thing.  Access the Log screen again, make sure the call K0ABC 
is in the call letters field, and then press <F2> in an attempt to save it 
again.

<Ctrl-L>K0ABC<F2>

The Warning message telling you that you are attempting to save a 
duplicate record to the file has appeared because those same call letters 
for the same date already appeared in the log.


7.3	Editing and Deleting Log Records

You can change existing log entries by selecting the Edit screen and then 
defining which log entries you wish to view and edit.  You can select by 
call, name, date, qth, or qsl.  

This example first creates a dummy log entry for K7dumm/7 and then 
opens the log edit screen to demonstrate how the log entry can be 
changed.

Create a new log record for K7dumm/7.  From the main sending screen 
open the log screen by pressing the <CTRL> key and L key at the same 
time:
				<Ctrl>L

In the first field enter the call letters:

				K7dumm/7

Tab to the qth field and enter qth:

				<TAB>CITYVILLE

Tab to the name field and enter name:

				<TAB>CLARENCE

That is enough for now. Save the record by pressing function key F2 
twice (once to exit the qth field and a second time to activate the F2 key 
to save the record).  

				<F2><F2>

This will return you to the main sending screen.  Now you are ready to 
edit the record.

Access the log screen again.

				<CTRL>L

Then go to the log utilities screen menu which displays a menu of log 
utilities functions.

				<F4>

Choose Edit by pressing E.

				E

You now have a choice of choosing which log records to view for editing.  
You can select records by All, Call, Name, Qth, or QSL.  If you know the 
call for the record you wish to edit then press C.  Do that now.

				C

You are asked for the call to search for.  You only need to enter enough 
of the call to narrow the search to the one call that you are looking for.  In 
this case you can remember that the call contained the characters DUM 
so just enter that much and press the <Enter> key.	

				DUM<ENTER>

At this point you can edit any of the fields you wish and then save the 
record in the same manner as when you create a new record with the 
main log entry screen.  The edit screen allows you to delete records as 
well and you may want to do that for this record to get it out of your log.  
Press function key <F4> to delete the record.

				<F4>

If more than one record had been selected by your search criteria then 
each time you finish with a record another from the selected group 
appears for editing.   


APPENDIX  A

IN CASE OF TROUBLE

A1	In Case Of Trouble

A1.1	Log Problems

A1.1.1 {L} doesn't seem to work.

Various file error messages.  Note that the config.sys file in the root (boot) 
directory must have files=25 or greater to be sure enough file handles are 
available to support the program.  

The shareware version does not support lookup of prior QSO's but {L}, 
following a call typed on the screen should result in the call appearing in 
the header and a log entry started with that call.

Note that when logging a call from the screen by entering {L} immediately 
after the call you must be sure that a space occurs before the call or that 
the call is at the left hand margin or else characters on the screen before 
the call will become part of the call.


A1.1.2  {L} takes a long time to search for prior records in the log.

The first time a search is conducted after starting CWM the key files must 
be loaded from disk to memory and that may take a few seconds (more for 
large logs with many records).  Once that has been done other searches 
are done very quickly because the information is already available in 
memory.

If your computer does not have adequate memory installed to hold the 
key files then information must be taken from disk every time a search is 
conducted.  In this case you will see the "Loading Key Files" message 
during every search.
  

A1.1.3  `Problem with <logname>. K_Y'   message.

This kind of message indicates a bad log file structure.  Correct this by 
backing up the log file and then using the new backup log.  When a log is 
backed up CWM analyses and fixes many log structure problems in the 
process of creating the new log file under a different name.



A1.2	Noise In Receiver

If disconnecting the keying circuit from the computer helps:

Some computer noise is being conducted through the keying wiring.  Try 
inserting a small inductance in series with BOTH the ground and keying 
wire to interrupt the noise.  Ferrite beads may be sufficient.  Bypass 
capacitors may help. 

If disconnecting the keying circuit from the computer does not help 
enough:

The computer noise is probably being radiated directly from the 
computer to the radio or is being conducted through the ac power 
wiring of the hamshack.  Place the computer as far as possible 
from the radio and from the receiving antenna.  Use coaxial or 
other form of shielded lead-in from the antenna to keep the 
sensitive part of the antenna as far as possible from the computer.   
Try isolating the computer from the ac power wiring with ac line 
filters designed to trap TVI.

A1.3	Incorrect Characters Result From Function Keys or Other Keys 
That Have Been Programmed For Text Entry

If the stored text for Function Keys or other keys is not reproduced 
accurately when the key is pressed then reprogram the key.  If the 
problem continues then the file that stores the text may have 
become corrupted and must be removed from your system and 
created once again.  For function key programming the file is 
MESSAGE.HAM and for other keys it is CODEKEY.HAM.  When in 
the DOS environment the command to remove a file is:
                            DEL filename
 CWM will create a new file once the old one is deleted.

A2	Program Will Not Run

A2.1	No copyright notice ... doesn't seem to start at all
	
Corrupted CONFIG.HAM or other files. Erase CONFIG.HAM and 
try again.  If that doesn't work then erase all of the .HAM files and 
try again.

The graphics portion of the introductory screen may interfere with 
some computers.  Try starting the program with CWM MONO 
command to disable the introductory graphics.


A2.2	Screen blank but can hear sidetone code

May have color foreground set to the same color as background.  
Try starting with the mono or lap argument to force default 
monochrome mode.  (Example: Start program with the command    
CWM  /LAP  or CWM  /MONO)

A2.3	Program Stops (with or without error message) 

The most common cause of a program crash is a corrupted 
CONFIG.HAM file.   This is especially true if CWM operated 
correctly at one time and then began to experience problems later.  
An attempt to edit CONFIG.HAM, MESSAGE.HAM, or 
CODEKEY.HAM with a word processor will surely cause this to 
occur.  To correct the problem remove those files from the system 
as described above in A1.3 and let CWM rebuild them when you 
next start the program.


A3	DISTORTED CHARACTERS

This section applies only if you are running CWM with the optional /T 
timing argument to force element timing by microprocessor clock cycles 
as described in section 4.2.2.

Uneven length of element length and spacing will occur if another 
program is running in the background when you operate CWM.  The 
reason is that when timing is based on processor cycles (/T argument 
used during startup) CWM requires 100 percent of the processor's 
attention to maintain consistent timing.  Many background programs 
`steal' time slices for their own purposes which confuses the timing of 
elements and characters generated by CWM. 

If your computer is generating distorted characters then check to see if 
any background programs are running on your system and eliminate 
them.  The most direct way of doing this is to disable your config.sys and 
autoexec.bat files in the root directory of your boot drive.  This can be 
done by temporarily renaming both of these files (to any other names) and 
then rebooting your computer or turning the power off and then on again.  
This will assure that any background programs normally started by your 
config.sys or autoexec.bat files will not be started.

A4.1	Operation Under Windows

CWMaesto should run fine under windows as long as the default timing 
method (no /T argument is used during startup) is used.  Otherwise, CWM 
cannot be operated under the Windows operating environment because 
the Windows system forces sharing of the processor with other programs 
and utilities which disrupts the timing of character elements.

The windows environment does interfere with keying through the 
communications port.  For this reason CWM must be operated under DOS, and
cannot be operated in a DOS window in the windows environment.

If your computer is running Windows95 or later you can change to the DOS 
environment by taking the following steps:

   1   Click on the START button on the desktop
   2   Click the Shutdown button
   3   Move to the line "Restart the computer in MS-DOS mode" and click YES






APPENDIX  B

REGISTRATION INFORMATION


Order CWM from:


Don Ehrlich    K7FJ
538  Farrington  Road,  Port Angeles,  WA     98363
USA

Specify:



CWM Registered Version Software                             $20 USD                                             ......       $20

Printed & Formatted Manual (no cover )   ($5 US) .........    _______

Type Of Floppy        3.5 inch  (1.44Meg)     _____  
                      5.25 inch (1.2 Meg)     ______
       (or specify other)        ____________________


Shipping / Handling     ($2 US/Canada   $5 Other) ..........  ________

( If floppy not specified then 3.5 inch (1.44 Meg) 
  format  will be provided)

                                                   Total     $________




APPENDIX  C

COMPARISON OF SHAREWARE AND REGISTERED VERSIONS

Assign Text Message To Function Keys:   In the shareware version only the F1 and F2 
function keys may be assigned messages.  In the registered version all of the function 
keys can be programmed with text messages.  Also, in the registered version most of the
lower case keys, arrow keys, and punction keys can be used to send a stored message of
any length by programming the key to take text from an ascii file.  Therefore, in the
registered version the number of custom messages and their length is nearly unlimited.

Text Input From File:  This feature is not available in the shareware version.  In the 
registered version text may be stored in an ascii file and then called to the screen by use
of the embedded command {Ffilename}.

Lookup Prior QSO in Log:  Not available in the shareware version.

Assign Key codes or Text To Non-Function Keys:  Not available in shareware version.
In the registered version prosigns such as ..._._  or ._... can be assigned to any key.  
Short text strings can also be assigned to any key and this is useful in using a single key
to call up input from a file using the {Ffilename} feature.

Number Of Log Entries:  Limited to 100 in the shareware version.  Unlimited in the 
registered version.

Embedded Commands:  {Mn} to call another message is limited to n=1 or n =2 in the
shareware version.  {Ffname} not available in shareware version.  {L} enters call 
into log screen and assigns it to the {C} embedded command but does not initiate
a check for prior QSO's.

