I. THE SUPER MORSE MANUAL The Super Morse user manual is contained in two files, SM1.DOC and SM2.DOC. The manual can be printed out with the following commands: COPY SM1.DOC PRN: and COPY SM2.DOC PRN: II. DATA FILE LOCATION Versions prior to 1.04 required that all data files (those with HLP and SM extensions) be placed in a special subdirectory named \SM. Since this proved very confusing to many users, I have eliminated this requirement. If you already have Super Morse installed with a \SM subdirectory, you should copy all files with an SM and an HLP extension to the directory in which SM.EXE is located. If you choose to leave SM.EXE in the \SM subdirectory, no changes will be required. If you are installing Super Morse for the first time, you can ignore the foregoing. III. DATA FILE LOAD PROBLEMS Users have reported that version 1.04, and to a lesser degree version 1.04A, sometimes refuses to load the data files and indicates an installation error. I am hoping that the problem has been corrected in this version. If the data files are not in the same directory as SM.EXE, the error message is correct, and you should move the files. However, if the problem still persists, try rebooting the computer and running Super Morse as the first program after rebooting. Some users have reported that Super Morse will not run properly after other programs such as Lotus have been used. In any event, please notify the author if you have a file load problem that cannot be attributed to the aforementioned installation error. Please tell me the conditions of failure, including type and speed of equipment and peripherals, names of memory resident programs, whether you are using a DOS shell, names of programs run previous to Super Morse, and the like. IV. SPEED CALIBRATION Before you run Super Morse you should calibrate the code speed to suit the clock speed for your computer and to account for any memory resident programs which you have loaded. Each time you change the memory resident program enviroment you will need to recalibrate code speed. When doing so use the following procedure: 1. Select the ools command from the main menu. 2. Select the uto Calibrate subcommand. This will automatically provide an approximate calibration. For best results continue with the following steps. 3. Select the peed test subcommand. 4. Using a clock or watch with a sweep second hand, count the number of times the standard word PARIS is sent in exactly one minute. Since the calibration is done at 20 words per minute, you should count exactly 20 words sent in one minute if the calibration is correct. If exactly 20 words are counted, then no further calibrations are necessary. 5. If the number of words and code speed do not match, then use the ools command and iming subcommand to set the timing constant. Increasing the number slows the send speed down, and vice versa. 6. Repeat steps 1-4 until the code speed shown at the bottom of the screen matches the number of words sent in one minute. In counting the number of times PARIS is send, be sure to include the last word space as part of the last PARIS. In other words, if you are attempting to calibrate at 20 words per minute, start timing when the first word is begins and stop timing when the 21st word starts. On my Zenith Z-150 running at 4.77 MHz. and with no memory resident programs installed, the timing factor is about 1220. With several memory resident programs installed, the timing factor decreased to considerably less than that (in the 600 range).