This release - correctly determines a QSO's "need" for VUCC and WPX realtime award tracking (tnx to Bill G4WJS) - prevents the "Capture Clear" function from being invoked while a previous invocation of "Capture Clear" is still running (tnx to Joe W4TV) - when automatically submitting a QSO to eQSL after logging a QSO via the Capture window or accepting a QSO from another application, properly expands substitution commands in its "QSL Message" item (tnx to Laurie VK3AMA) - performs a user-abortable LotW connectivity check before proceeding with a "Sync LotW QSOs", "Sync LotW QSLs", or "Update from LotW" operation; if DXKeeper cannot connect to LotW within 60 seconds, the operation will not proceed (tnx to Larry W8LIG and Joe W4TV) - updates the QSLConfiguration.htm and QSLMedit.htm documentation files Note: when an application is waiting for a lengthy input/output operation to complete, Windows 7 and Windows 8 can erroneously place a "not responding" message in the application's title bar, misleading you into concluding that the application is "hung" or has "crashed". DXKeeper 12.1.3's new "check to see if LoTW is accessible and responding before directing it to report information" mechanism should reduce the incidence of this message appearing when executing a "Sync LotW QSOs", "Sync LotW QSLs", or "Update from LotW" operation. DXKeeper 12.1.3 is available via the DXLab Launcher and via 73, Dave, AA6YQ