SHACKLOG HISTORY

This page tracks the update history of SHACKLOG since the release of v5.1. Updates to SLIM, SAM-I
and SLRESTOR are tracked on  separate pages.

SHACKLOG v5.7.02

Released March 14th, 2007
Bug fixes
Exporting QSOs to an ADIF file when the length of the data in the GENERAL field was 1, 2 or 3 caused an incorrect data length to be stated in the ADIF file. This caused the offending QSOs to be rejected by TQSL. This is now fixed.
 
Functionality changes
On the QSO screen <ctrl N> takes you to the NAME field and <ctrl L> takes you to the GENERAL/LOCATOR field. This allows quicker movement around the fields.

SHACKLOG v5.7.01

Released June 1st, 2005
Bug fixes
ADIF export now exports mode G1B as PSK31 rather than PSK, in line with version 2 of the ADIF spec.
SHACKLOG crashed on start-up if IOTA was enabled and the IOTA path was pointing to a non-existent drive. This was only likely to happen when moving the SHACKLOG installation from one PC to another. This is now fixed.
Functionality changes
When EXPORTING the results of a SEARCH, new option of 'Q' added. This produces an ADIF file not including QSL SENT data, and updates QSL SENT data in the log from 'C' to 'B', 'E' to 'D' and 'Y' to 'X'. The purpose of this option is to allow export of QSO data to BV7 for QSL printing, whilst updating the SHACKLOG log to show the QSL data has been printed.

SHACKLOG v5.7.00

Released March 25th, 2005
Bug fixes
When exporting the results of a search, could not include '-' in the file name. This is fixed.
Functionality changes
Can now use 'L'  in the QSL RECEIVED field. This is intended to be used to indicate confirmations via Logbook of the World (LOTW).
CAT support for Yaesu FT857 added

SHACKLOG v5.6.01

Released August 27th,  2004
Bug fixes
When exporting an ADIF file, the field length of the IOTA data field was incorrectly specified as 5 characters instead of 6. This is fixed.
Functionality changes
None

SHACKLOG v5.6

Released June 1st,  2004
Bug fixes
SL normally forces the first character in a data entry field to uppercase. In the case where data had been entered, and then the <Home> key had been depressed to take the cursor to the start of the field, the next (=first) character was entered as lower case. This is fixed.
When updating CLOSE or NOTE entries, the data entry cursor would stick on the empty TIME OFF field. This is fixed.
 
Functionality changes
Logs or parts of logs may now be exported in ADIF format as well as tab-delimited format. This functionality is available on the EXPORT LOG SCREEN and also on the DEFINE SEARCH SCREEN and UPDATE SEARCH SCREEN.
FT857 CAT control is now supported.

SHACKLOG v5.5.04

Released August 4th, 2002
Bug fixes
On the Print Log  screen, the QSO number of the last QSO printed never changed (bug introduced in V5.5.00, so the last number printed would be the last number printed using a release prior to V5.5.00)
On the Print Log  screen, the QSO number in the first data entry field never changed.
On the QSO screen, in Update QSO mode, <ctrl Home> did not work when Previous QSOs with a specific station were displayed (bug introduced in V5.5.03)
On the QSO screen, in New QSO mode, editing the callsign so that the revised callsign is a callsign that has been worked before, the RST R/S fields were cleared.
On the QSO screen, in New QSO mode, working a station in a different country to that when previously worked (eg work CT3/G3PMR after having previously worked G3PMR) displays some QSO information for the previous QSO that is not appropriate for the new QSO (eg IOTA reference) 

SHACKLOG v5.5.03

Released January 1st, 2002
Bug fixes
In New QSO mode, changing the callsign set the signal reports to blank
In Contest QSO mode, if the start time of a QSO was before the contest start time, but the finish time of the QSO was after the contest start time, the contest QSO number was incremented (correct) but the QSO did not display in the list of contest QSOs in the log panel
In Contest QSO mode the contest QSO counter sometimes gets reset to 1. I have never been able to reliably reproduce this although I have seen it happen. I have modified the code, which may have fixed this, but I cannot be certain.
In New QSO mode <ctrl A> would move the input cursor to the next field
On the Print Log  screen, the callsign of the last QSO printed was missing
Functionality changes
Yaesu FT817 CAT control support added. When reading the mode from the radio, and the radio mode is "DIG", SHACKLOG will set and display the mode according to  the HF and VHF settings in the MODE column on the Set Packet Cluster Alarms & Filters Screen.

SHACKLOG v5.5.02

Released September 4th, 2001
Bug fixes
SHACKLOG crashes when receiving a DX Cluster spot with a frequency that doesn't contain a decimal point.

SHACKLOG sometimes crashes when receiving a DX Cluster spot with a one or two character callsign

Functionality changes
None

SHACKLOG v5.5.01

Released August 21st, 2001
Bug fixes
When a QSO is marked as confirmed by entering "B", "D", or "X" into the QSL R field, and is for an island having "Rejected" status in the SAM-I islands database, the new QSO now updates the islands database, removing the "Rejected" status.
Functionality changes
None

SHACKLOG v5.5.00

Released January 28, 2001
Bug fixes
On the Config Comms screen, a '-' character is now accepted in the Initial Command setting.
In Stats, when searching with DATE as the primary key, some dates were not found.
After QSO logging has been started by entering a valid callsign, and you return to the CALL FIELD, with INSERT/OVERWRITE set to INS, and a single digit is entered, SHACKLOG no longer crashes on <F1> LOG.
After  QSO logging has been started by entering a valid callsign, and you return to the CALL FIELD, with INSERT/OVERWRITE set to INS, and two digits are entered, SHACKLOG no longer saves a QSO in the log which cannot be retrieved. This bug and the previous bug could occur when entering QSOs retrospectively and entering TIME ON or TIME OFF data beyond the end of the field.
The above two bugs could also have caused SHACKLOG to crash if receiving a DX Cluster spot with a spotted callsign of only one or two characters long.
Functionality changes
On the QSO screen, operation of <F3> Mode now does not reset the signal reports to their default settings.
On the QSO screen, editing a callsign now does not reset the signal reports to their default settings.
On the QSO screen, an incremental adjustment to the MHz field and CAT-connected radio's frequency is provided by entering data into the empty callsign field as follows:

Number followed by +. Sets increment to number and QSYs the radio HF (eg 5000+ sets the increment to 5kHz and QSYs up 5kHz)
Number followed by -. Sets increment to number and QSYs the radio LF (eg 5000- sets the increment to 5kHz and QSYs down 5kHz)
Number followed by !. Sets increment to number but does not perform QSY.
PgUp - QSYs radio up by  increment. (Works from any field)
PgDn - QSYs radio down by increment.  (Works from any field)

The increment can be set up to a value of 32767 Hz. The resolution is 10Hz. Settings of 9Hz, 13Hz, 125Hz etc will be interpreted as 0Hz, 10Hz and 120Hz respectively and so on. The resolution will probably be increased to 1Hz in V6. These changes are applied to the main VFO only, giving an instant split capability.

The current increment setting is saved so that next time SHACKLOG is started the increment will be set to the last used value. The first time you use this version of SHACKLOG, the increment will not be set on start up.

CAT system operation has been speeded up. In previous versions, change of frequency or mode on its own caused updates to be sent to the radio for everything. Now only the changed parameter is sent to the radio. However, on SSB, a band change will be accompanied by a mode change if the sideband needs to change.
The frequency boundaries of some bands have been widened to allow entry of frequencies that, although no longer valid, were valid in the past.
The frequency is now always displayed on the QSO Screen with full kHz appended eg previously 14.260 would have displayed as 14.26, but is now displayed as 14.260.
The <Page Up> and <Page Down> keys no longer control scrolling of the log panel. Now use <Ctrl Page Up> and <Ctrl Page Down> instead.
<Ctrl B> toggles the initial data entry point position in the TIME ON and TIME OFF fields. The position is indicated just to the right of the TIME OFF field. A letter B indicates that the cursor will be positioned at the start of the field, whereas an 'E' indicates that the cursor will be positioned at the end of the field.

SHACKLOG v5.4.02

Released September 28th, 2000
Bug fixes
1. You work a simple callsign such as CE0Z.
2. You then work a complex call containing the simple call, eg
CE0Z/OH3JF, WHERE THE SIMPLE CALL IS NOT THE HOME CALL. This bug
does not occur if you work G9XYZ and then TK/G9XYZ as G9XYZ is the
HC, whereas CE0Z is not the HC in the case of CE0Z/OH3JF.

In QSO Update mode, you can only access QSOs for the complex call.

SHACKLOG v5.4.01

Released September 4th, 2000
Bug fixes
Entering a call for which SHACKLOG cannot determine the country, and terminating the call by <up arrow>, caused the COUNTRY field to be left blank. This later caused a crash.
Signal report increased to 3 characters for PSK31 (G1B).

SHACKLOG v5.4.00

Released August 22nd, 2000
Bug fixes
None
Functionality changes
Updated to handle the new IOTA Directory format. Minor change to displayed information.

SHACKLOG v5.4.02

Released September 28th, 2000
Bug fixes
1. You work a simple callsign such as CE0Z.
2. You then work a complex call containing the simple call, eg
CE0Z/OH3JF, WHERE THE SIMPLE CALL IS NOT THE HOME CALL. This bug
does not occur if you work G9XYZ and then TK/G9XYZ as G9XYZ is the
HC, whereas CE0Z is not the HC in the case of CE0Z/OH3JF.

In QSO Update mode, you can only access QSOs for the complex call.

SHACKLOG v5.4.01

Released September 4th, 2000
Bug fixes
Entering a call for which SHACKLOG cannot determine the country, and terminating the call by <up arrow>, caused the COUNTRY field to be left blank. This later caused a crash.
Signal report increased to 3 characters for PSK31 (G1B).

SHACKLOG v5.4.00

Released August 22nd, 2000
Bug fixes
None
Functionality changes
Updated to handle the new IOTA Directory format. Minor change to displayed information.

SHACKLOG v5.3.01

Released August 9th, 2000
Bug fixes
JA and US spot filters would only work in snoop mode
Functionality changes
US spot filter
The US spot filter also now filters VA, VE and VY spots
IOTA panel
The IOTA panel now does not display the island latitude/longitude. This is in preparation for a new IOTA directory update, which will include all the new islands, but which will not include latitude/longitude information.

SHACKLOG v5.3.00

Released May 25th, 2000
Bug fixes
If, after entering a callsign in New QSO or Contest QSO modes on the QSO Screen, SHACKLOG prompts for the country name, and <F3> MODE is pressed before entering a country name, SHACKLOG crashed.
Truncated DX cluster messages (ie with no callsign in the spot) now handled correctly (ignored).
The B/M DX Cluster alarm would operate correctly for a country worked but not confirmed on the band/mode, but would not work if not worked on the band/mode.
New functionality
Capturing DX Spots
The use of <Alt 2> and <Alt 3> to capture DX spots and transfer the data to the logging screen now also transfers the IOTA number if present in the spot.
CAT System - FT847
For the Yaesu FT847, SHACKLOG previously supported the CAT system radio setting functions only. Reading data from the radio was not supported. The reason for this was that early versions of the FT847 did not provide the facility to read data from the radio. This version of SHACKLOG supports both types of FT847. 
DX Cluster Regional Filters
It is now possible to filter out DX spots from Japan and/or USA. Use <ALT j> to toggle the filter for Japanese originated spots, and <ALT u> to toggle the filter for USA originated spots. The status of these two filters is indicated at either end of the tram line bar separating the packet receive window and the packet transmit window.
Printing to sheets of labels
You can now specify the number of label rows per sheet of labels. This is used in conjunction with the EJECT CARD setting to determine when to issue a page eject command to the printer. 
Omit Blank Lines
To make room for the above, the Omit Blank Lines configuration option has been deleted. Blank lines are now always omitted.
Printing Labels to a File
When printing labels to a file, the new label text is now appended to the end of the file (if the file exists) rather than overwriting the file as before.
Update QSO
To make it easier to recognise that you are in Update QSO mode rather than New QSO or Contest mode, the screen title for Update QSO now flashes (but if running in a window rather than full screen, the background colour changes, and the title doesn't flash - this is an oddity of Windows and something I have no control over)

SHACKLOG v5.2.04

Released March 10th, 2000
Bug fixes
Lists now saved correctly when saving Macros.
When the following conditions are all true:
  • QSO logging is active (i.e. in New QSO or Contest Mode, with a callsign entered)
  • DX cluster is running and a DX spot has been displayed since entering the callsign
  • Some action is taken which causes the country/band/mode message to be updated, e.g. <Ctrl O>

The update of the country/band/mode message would refer to the country of the last spot rather than the country for the QSO being logged. This is now fixed.

When displaying a locator for an already logged station, the locator now does not overwrite the end of the word "LOCATOR"
The cursor now goes to the end of the TIME ON and TIME OFF fields as it used to in V4.

SHACKLOG v5.2.03

Released January 31st, 2000.
Bug fixes
Entering a single space into the IOTA field and then editing the call sign in NEW QSO mode, with IOTA enabled, could cause SHACKLOG to generate the message "IOTA index file not found. Run IOTAINDX.EXE to generate". SHACKLOG would also create a zero length file called _index.pmr . All now fixed.

SHACKLOG v5.2.02

Released January 16th, 2000.
Bug fixes
When executing a search and the number of QSOs checked exceeds 32,767 the number displayed no longer becomes negative.
When executing batch macro which prints a report to a file, SHACKLOG no longer crashes.

SHACKLOG v5.2.01

Released January 3rd, 2000.
Bug fixes
FT100 CAT frequency control problem fixed.

SHACKLOG v5.2.00

Released December 18th, 1999
Bug fixes
In SWL mode, 'View QSL' in CONFIGURE LABEL PRINTER now displays a call sign for the station being worked - it used to erroneously display a signal report!
New functionality
SHACKLOG now provides an interface to the BuckMaster HamCall CD-ROM, in addition to the existing Flying Horse RAC interface.
There are now hot keys to toggle the status of the Packet Cluster Audio Alarms (<Alt A>) and Snoop Mode (<Alt S>) from any screen, with visual indicators of the status on every screen.
The setting of the RST field sequence (R or S) on the QSO screen is saved for use next time SHACKLOG is started.
The toggling of RST field sequence is disabled in SWL mode.
You can now have SHACKLOG send a page eject command after printing each QSL - useful if you are printing directly to the QSL rather than to a label.
You can now specify your own text on the QSL label.

SHACKLOG v5.102

Released November 21st, 1999

Bug fixes
In SWL mode, 'View QSL' in CONFIGURE LABEL PRINTER now displays a call sign for the station being worked - it used to erroneously display a signal report!
Reading frequency from FT900 now working correctly.
Printing SWL report ackmowledgement labels now prints rig and antenna when selected.
Contest QSO number now saved after every QSO - previously in the event of a power failure or other crash, the current contest QSO number could be lost.
New functionality
CallBook CDROM now not referenced in Contest mode - to avoid slow down by CDROM access for US calls.

SHACKLOG v5.101

Released October 27th, 1999

Bug fixes
In CONTEST MODE, entering a call for a new QSO, and then moving back to the call field to edit the call sign, caused the contest serial number to be incremented twice.

In CONTEST MODE, entering a call for a new QSO, and then moving back to the call field to edit the call sign, caused the contest serial number to be incremented twice.

SHACKLOG v5.1

Released October 3rd, 1999

Bug fixes
In CUSTOM REPORTS, RST SENT and RST RCVD headings were reversed
SHACKLOG would very occasionally crash on PacketCluster spots. This was caused by an illegal IOTA reference (eg AF-0), which could be caused by truncation of the comment field in the spot.
On the QSO screen, deleting an IOTA reference with the <Del> key caused SHACKLOG to crash.
New functionality
SHACKLOG now supports logging of QSOs in the new PSK31 mode (G1B). If you enable this option, the mode G1B replaces the G3E mode.

When using the CAT system with this mode, the mode data sent to the radio is J3E as it is assumed that the phase modulated signal is connected to the patch audio input of the radio. It is set to USB for all bands, regardless as to whether they are above or below 10Mhz. This is necessary when using the QPSK FEC mode of PSK31 as then the 90 and 270 degree signals get inverted on LSB.

Enable this option in CONFIG MISC.

On the QSO screen, by using <Ctrl A> you can now change the order in which SHACKLOG goes to the RST Received and RST Sent fields. The first field in the sequence is indicated by the letter "R" or "S" displayed in the title row of the QSO screen just to the left of the screen title.
Fed up of getting a BAD CAT message, because you tried to use your CAT system with the radio switched off? Now you can restore the BAD CAT to the correct radio setting by <Ctrl C> - no need to go back to CONFIG COMMS.
On the QSO screen, you can now increment or decrement the date field by one day by entering + or – into an empty CALL field. This is especially useful if you forgot to enter CLOSE at the end of the previous day’s operating.
You can now control whether or not dummy QSOs (those with calls CQ, CLOSE, NOTE, TEST) are ignored or not when performing a search. Do this with <Ctrl D> from the DEFINE SEARCH or UPDATE SEARCH screen. The status is displayed in the title row, just to the left of "First". D indicates that dummy QSOs are required, <space> that they are not.