This release - properly saves pathnames embedded as arguments within registry settings (tnx to Iain N6ML) - on the Main window, interprets clicking an application's Status Indicator as equivalent to clicking the application's Control button - updates the ControllingApplications.htm documentation file When directed to save an application's Registry settings or update a Workspace, previous versions of the Launcher correctly save pathname settings -- for example, the pathname in which DXKeeper’s Log file can be found, or the pathname where SpotCollector’s “Sub-band Definition” file can be found. However, previous versions did not correctly save settings where a pathname was a part, but not all of the setting. For example, the Launcher would not correctly save the contents of the WinWarbler startup macro when WinWarbler’s settings to a Registry file, or when updating WinWarbler’s settings in a Workspace; note how the pathname appears in the middle of the setting. The defect responsible for this has been corrected in DXLab Launhcer 1.7.2. To my knowledge, WinWarbler is the only DXLab application with settings whose values can contain a pathname combined with other information. Thus if you have in the past directed the Launcher to save WinWarbler’s Registry settings to a file, you should terminate WinWarbler and then direct Launcher 1.7.2 to repeat that operation, replacing the previously-created file. Similarly, if you have directed the Launcher to create a Workspace that includes WinWarbler settings, you should terminate WinWarbler and direct Launcher 1.7.2 to update that Workspace. DXLab Launcher 1.7.2 is available via the DXLab Launcher and via Mirror site operators can obtain this release via 73, Dave, AA6YQ