Fixed the behavior of the Show Port Names button on the Config page, Basic tab. On some versions of Windows clicking the button resulted in a null reference exception due to a change to the way the list of ports returned by the OS was handled. The button now correctly lists all physical and virtual serial ports known to the OS.
Note that there will be one more release (1.8.0) that will target .NET framework 4.0 and thus *might* work on XP. Because .NET framework 4.0 is now end-of-life just like XP, releases after 1.8.0 will target a .NET framework supported on Windows 7 through 10. (I say *might* work on XP because there's no technical reason it shouldn't but I no longer test the monitor on XP nor support the monitor on XP.)
The next release will have a "safe mode" capability whereby you can launch the monitor such that it will ignore its' configuration file and will allow you to view the stored config or start with a blank config. The reason this is necessary is that most support incidents of late are due to a COM port being configured that is no longer associated with the amp and the config is set to auto-start. This combination results in the monitor stuck talking to a device it thinks is an amp and won't do anything, not even let you launch the Config page, until it gets a valid amp response. Because that never happens, it's essentially hung. Until safe-mode is released, your best bet is to ensure auto-start is disabled. That way you can at least review the config and change the serial port as needed before the monitor attempts to connect.
Changes after 1.8.0 and safe-mode will likely focus on bringing the program into the current decade from a user interface perspective. I'm using an outdated technology called Windows Forms for what you see and interact with. Windows Presentation Framework (WPF) and Universal Windows Programs (UWP) are current and the latter allows for pre-compilation for the Windows Runtime (WinRT) rather than compiling to intermediate language (i.e. byte code) for a .NET framework. I'm new to these technologies so it might take a while for a release based on these to appear.