We used to have this problem when ENLIGHTEN was multi-process, and sometimes zombie processes stayed up even when the GUI controller closed. We handled this (crudely) by running ENLIGHTEN from a batch file that automatically killed any hung processes:
(If another instance of ENLIGHTEN.exe is running on a different pid, pop-up a messagebox to explain and then shutdown, all before attempting to connect to any spectrometers)
This has happened to a couple users recently.
We used to have this problem when ENLIGHTEN was multi-process, and sometimes zombie processes stayed up even when the GUI controller closed. We handled this (crudely) by running ENLIGHTEN from a batch file that automatically killed any hung processes:
We could probably do this more elegantly with something like this:
(If another instance of ENLIGHTEN.exe is running on a different pid, pop-up a messagebox to explain and then shutdown, all before attempting to connect to any spectrometers)