Does StartWatch point to the WeatherLink exe file or does it point to a batch file that runs WeatherLink? If it points to a batch file then WeatherLink won't get StartWatch's minimize suggestion, the batch file command window will. Also, StartWatch will be monitoring the cpu and memory use of the batch file command window, not the program the batch file runs.
I have StartWatch pointed directly to C:WeatherLink\WeatherLink57.exe
Regarding the port, I would like to find out why it cuts out. But that is a different problem than the one I fixed in the latest version. The problem I fixed (I hope) is one where the port would go red when the port really did go down, but after the port came back up, StartWatch would not detect it, and just keep showing it as red. Having the port go down briefly while because of other stuff going on in the system is something else, and one I wasn't aware of. It was probably reported, but I mistook it for the same problem.
I think I can fix what you're seeing (if I understand you correctly).
Steve
Update, not a StartWatch port monitoring problem. It's in Virtual VP. To test I reconfigured StartWatch to allow the programs to continue to run even if the port monitor showed red and cleared all alerts and logs of both it and VirtualVP. Below is a screenshot of what happened after I run the forecast ticker on the console at 4:58pm our time. Also note the reading on my clock next to the start Windows button when I took the screenshot. (5:12pm) See further notes below screenshot...
I think I was seeing both issues originally. Probably why I'm only seeing this now after running the forecast ticker on the console since it appears you solved the one in StartWatch. After seeing the above in VirtualVP I clicked on disconnect, then reconnect, port monitor went back to geen, programs all started receiving data again. VirtualVP's alerts file is empty, below is the only thing showing in the log file:
11/23/2006 16:58:19:458 Error - VpConsole: Several consecutive failures of console to respond. Will try to reconnect.
And here's what shown in VirtualVP's activity file:
16:58:15:051 Warning - VpConsole: No response after several retries for Wake Up Console
16:58:16:253 Warning - VpConsole: No response after several retries for Wake Up Console
16:58:18:256 Warning - VpConsole: No response after several retries for Get Live Sensor Data
16:58:19:458 Warning - VpConsole: No response after several retries for Wake Up Console
16:58:19:458 Error - VpConsole: Several consecutive failures of console to respond. Will try to reconnect.
16:58:21:040 Warning - VpConsole: No response after several retries for Wake Up Console
16:58:23:033 Warning - VpConsole: No response after several retries for Get Live Sensor Data
16:58:23:153 Warning - VpConsole: Far too long since last loop = 10.335, last command= Get Live Sensor Data
Running VirtualVP 1.1.3.20