This release 

- includes Scomm32x.ocx version 9.1.2, which prevents the RTS signal from being briefly asserted when a serial port is opened (tnx to Salvatore I4FYV)

- detects the presence of an unregistered new version of SComm32x.ocx in its Components folder, and requests that you terminate WinWarbler so that this new SComm32x.ocx version can be registered when WinWarbler is restarted

- displays the installed version of SComm32x.ocx in the Port panel on the Configuration window's PTT tab

- ensures that the PTT serial port's RTS and DTR signals are not asserted when opening the port

- de-asserts the RTS and DTR signals when closing the RTTY modem serial port and the GPS serial port

- prevents the generation of an errorlog.txt file entry when closing a serial port that is already closed

- prevents the generation of an errorlog.txt file entry when double-clicking in the "Channel Monitor" window

- prevents the generation of an errorlog.txt file entry when loading macros from an incomplete or corrupted file

- prevents a "Can't open Clipboard" error when double-clicking on a decoded callsign in a receive pane (tnx to Tony KG4TAH)

- prevents infinite recursion in MMTTYModule.InitializeMMTTYParameters (tnx to Kent NC6B and Phil N9LAH)

- tolerates the SoundStereo parameter not being defined in the MMTTY.ini file (tnx to Giuseppe IT9FGA)

- eliminates an unnecessary suspension and restart of the MMTTY engine on startup

- ensures that the "QSO Info" panel's Notes textbox is properly rendered when running on Windows 10 (tnx to Kent NC6B and Bjorn SM7IUN)

- if open, closes the external RTTY serial port before shutting down the MMTTY engine, and re-opens it after MMTTY engine shutdown is complete


Notes:

1. Depending upon the version of Windows you're running and the level of security that you have configured, WinWarbler's attempt to register an updated version of Scomm32x.ocx may cause the Windows "User Account Control" (UAC) subsystem to seek your permission for the required change to be made to your computer. If this request appears on your monitor, WinWarbler will not run until you permit the change.

2. Update your firewall and anti-malware applications to consider this new version of WinWarbler to be "safe" 

3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of <http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

4. After upgrading, to revert to the previous version of WinWarbler, see <http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


WinWarbler 8.9.4 is available via the DXLab Launcher or via 

<http://www.dxlabsuite.com/download.htm>

    73,

        Dave, AA6YQ