- SafetyLog™ feature saves a copy of each QSO entered or updated to an ASCII file. To enable, go to Tools/Setup/Misc Ham Setup and click on the General tab. Specify a file name. You should choose a drive that is physically separate from the hard drive containing LOGic 5s data. This way, if the if LOGic 5s hard drive fails, you still have a copy of your data. A Zip drive works well. A floppy may be used too, but it is rather slow.
The file buffers are flushed after every write. Our tests on Win 95 show that no SafetyLog data is lost on a power fail. However, you should conduct your own tests if it is imperative that you lose no data. It is possible that some drivers use buffering methods that cannot be flushed.
Output to a printer is no longer supported, as Windows buffers printer output until a complete page is available to be printed. With no SafetyLog, LOGic usually loses at most the last two or three QSOs, so the buffered printer output of no benefit.
SafetyLog output is in ADIF-compatible format so that it may be easily imported with LOGic 5s ADIF import. There are two minor deviations from the ADIF standard. Look at the beginning of the SafetyLog file for info, especially if importing into a program other than LOGic 5. Notes and addresses are not written to the SafetyLog.
- Index to foreign-language file LANGUAGE.DBF is now automatically rebuilt after doing a clean or installing an update.
- Duplicate (copy) a QSO function. Great for working mobiles on a county line. Rest the mouse pointer on top of the Add button for instructions.
- Displays description (country name, continent name...) in the spot log.
- New compression routines. You will see a new progress indicator display when you back up, restore, install the QSL Route list, or make a QSL Submission file. This fixes problems that a few customers were having with the backup/restore utility and installing/submitting QSL data.
- New hot keys in Windows menu.
- Bug fix: "File is use" error when closing the run report window after running certain reports. Japanese users reported problems in prefix lookup in Japanese versions of windows. This fix may affect other languages as well. I think thats all we found to fix this time!
[ TOP OF PAGE ]