Applied Computing Enterprises -- ACE_LOGGER -- November 12, 1987 This readme file contains some basic operational information about the program pair ACE_LOGGER and ACE_LOGDEF. Together, these two programs will allow you to setup any type of log that you desire, whether it be for contest or general radio operation. With this program, there is no need to buy specific programs to log specific contests as you will find readily for the PC-DOS and MS-DOS machines. These versions are for DEMO only. They are fully operational except that they will not add any new log data to the log files. You may experiment with the definition of new logs, test their layout appearance etc. You may also look at the sample CANAM log file (which happens to be my 1987 actual log). This will give you a sample of the duping and reporting features as they currently exist in the program. These programs are currently written in AMIGABASIC, although they are currently under modification to compiled "C" code. This has the advantage of reduced size, increased speed and greater features (having full access to the ROM Kernel in the computer). The "C" version will be available in about a month. It will contain more advanced file selection and display features via requestors to enhance the ease of use over the current version as well as more efficient use of memory by dynamically allocating duping memory as required. Any person who decides to purchase the current AMIGABASIC version will receive the upgraded "C" version upon completion for the cost of media and shipping. Should you care to purchase the program, because you find it worthwhile, send $39.95 to Applied Computing Enterprises, 924 Westbury Court, Sarnia, Ontario Canada N7T 7R7 This will bring you the logging programs on 3.5" diskette with a printed manual. If you have any comments or suggestions for enhancements, drop me a line and I'll see what I can do. This program was tailored for the features that I felt that I could use. You may some additional ones. ACE_LOGDEF Program This program is used to define the characteristics of the log. It gives you the ability to custom design your log. It allows you to define screen layout, field prompts, field size, field entry order, field default values. It will allow you to define the standard types of duping possibilities. It allows you to define report headers, print order and column position on the printed page. All of this adds up to you defining the log you want. I have included a sample log definition, called CANAMA3. This is the definition that I used for the 1987 CANAM contest, A3 mode. You can add too or delete from this definition to experiment with the log definition utility. You should find the menu items fairly easy to follow. 1) Options -- Display/Modify Definition Look at and modify an existing log file layout and definition. This option has many suboptions once you get in for modifying a definition. Just follow the prompts. -- Create a new definition Create a new definition from scratch. -- Startup options definition Define logging program startup options like default log to use, disk drive (or its label) to find it on etc. It assumes that the file will be found in a subdirectory called "DATA". 2) Test Log This will display a log file layout and entry order so that you can get a "what you see is what you get" type display on your screen. 3) File Operations -- List current files Shows you all current definition files on your selected default drive in the DATA subdirectory. -- Delete a log definition Deletes a definition from the DATA subdirectory on your default drive. 4) Exit Pgm Guess what, this gets you out of the program! ACE_LOGGER Program This program is used to actually do the logging. Once you have defined your log, you need not ever run ACE_LOGDEF again, but use ACE_LOGGER only. The following is a brief description of each menu item. These are discussed in much more detail in the full manual. When the program starts, it will give you a full screen introduction, and then note the definition file that it is reading. If you have duping enabled it will create a second window for duping. The primary window is created with the size that you defined. The duping memory is loaded up with existing log file entries on disk. When this operation is complete, the log entry blank will be displayed with the cursor in the first field for data entry. If you have a time field on the log entry display, it will show the current system time. It is updated each time a field in entered so that you will always show a time close to the current time, but not eating up the system with the overhead of continually updating this field. To stop entering data use the key. This will tell logger to quit accepting data, close all open files and return to the menu. If data has been added the updated files will be written to disk. Menu Items: 1) Data Entry -- Modify/Insert/Delete entry These options work on specific entries in the log file. They have been added so that you can go back and fix a file that has incorrect data entered into it. 2) Start/Stop -- Start/Stop Logger When you want to start the logger in earnest again for entering new data you use this option. When you have the menu up, it will always show stopped. -- Enable/Disabled autoprint This option allows you to print a new log entry to your system printer as soon as the data is entered. This may make you feel better in case of a system disk failure. See note below. 3) Print -- by number Will print your log in ascending QSO number -- sorted log Will print your log in ascending alphabetical order of call. 4) Files -- Select new log Allows you to move to a new log file definition. -- Clear a data file Kills all log entries in this log. Good for clearing out last year's log, to start fresh this year, without having to redefine the log. Use the same definition, just kill the data. 5) Exit Pgm Guess what, this again gets you out!! NOTE: Have you had trouble with read/write errors on your disk? Well I have and in the middle of a contest. Thus I have a modified version of the logging program that will simultaneously write to the DF0: drive plus one other that you define. This way a single drive error will not kill your contest!!. Have fun with this DEMO. I hope you like the program. Would appreciate any feedback that you have. Sincerely Allan Ebert VE3AXV 6)