Next version status
- File/Import/Log data: ARRL 10m contest imports serial number in WAS and WACP. Fixed
- Entry/Standard: modified the way the "DXCC Status" field works
- Entry/Standard: added a seperate field for "DXCC Status for callsign"
- Contest/Run: added support for "IRTS 80m Counties", "QP Texas" outside TX, "Thracian Rose Club", "AGCW VHF/UHF"
- Contest/Run: added search for callsign in LL database
- Contest/Run: modified serial number generator
- Contest/Run: adapted ARRL 10m to allow XE multipliers
- Contest/Run: multiplier display error in "Canada Day/Winter". Fixed
- Contest/Run: correction for "Coupe du REF" when operating from French side
- Contest/ASCII File Generation/Cabrillo format log file: adapted AGCW HNY to export all data
- Contest/ASCII File Generation/STF format log file: added QTC export for WAE contest
- Contest/ASCII File Generation/STF format log file: multis for WAG are not calculated correctly
- Query/by Continent: first continent in list is selected
- Query/by Continent: double-click on row allows to modify QSO data
- Print/Label/Assign picture to QSO: when no description is entered, text 'Picture:' is not printed
- Print/Label/QSL label: when printing generic SWL card, QSL-S is set to 'Y'. Fixed
- Award/10-10: added awards
- Settings/Prefix / DXCC list: modified DXCC R1M to be RI1MV and R1F to be RI1FJ
- added HamQTH.COM Callbook support
- Modifying window: if multiple WAS entries exist, adding US-CY does not work. Fixed
- some cosmetics
frequently asked questions
Q.: Which files do I have to save when doing a back-up?
A.: There's just one single file that holds all your data, be it QSO data or award data. The name of the file is LUX_LOG.DB.
If you use the contest module, you will also need to back-up CONTEST.DB
In order to keep your configuration settings, take a back-up of LUX_LOG.INI. If you received a registration key, add LUX_LOG.PWD to the list.
Q.: What do I need to do to register, what does it mean and how much does it cost?
A.:Check the Help/Generate registration key section in the manual for detailed information.
Following the given instructions, you will then need to tell me your first and last name and your call-sign. Additionally, I'm interested in knowing the type of your operating system and screen resolution. The later two are for my personal use only. In return, you receive an archived file (LUX_LOG.RAR) which includes LUX_LOG.PWD. This file has to be extracted into your LL folder.
It means for you that the UNKNOWN user gets removed from the start-up screen and it means for me that I know who is using LL. I think that's a justified relationship. Furthermore, if a registered user has a problem, I can judge from the version he uses if the problem has been fixed. Of course, you should keep me informed when you switch to another version.
Registering your version of LL is free of charge, as LL is.
People who want to use older versions of LL than the current one will not get a registration file.
To simplify the registration process, please fill-in this form.
A.:That's a correct behaviour of LL. You forgot to unpack the file LUX_LOG.RAR with includes the registration file LUX_LOG.PWD.
In order to unpack this file, use WinRAR.
A.:Check your Windows screen settings. You are most likely using the "large fonts" setting. Switch to "small fonts" and the entry window will appear correctly.
Q.: I'm a new user and whenever I start LL, I get that yellow screen for a long time?
A.: Because you are an unregistered user, LL will display this information screen for 15s. After you have registered and you have received your registration file, LL will start with normal speed.
Q.: I get an "integrity constraint violation" error.
A.: If the error message shows up right after you want to save QSO data, it's most likely that you either did not define a log-book or you defined a log-book but you did not activate it.
Read the Lux-Log Quickstart instructions in the help file. Since your database data might be in an unknown state, best would be to uninstall LL and reinstall from scratch, then carefully follow the instructions given in the help file.