Thanks for the comments.
1. I'll have to try and duplicate this There are two phases in hang detection. The first is the "Confirming" phase, and after a period of time (seconds) it goes to "Hung". I could bump that time, plus check that I don't use a shorter confirm time during startup.
2. Alerts can be viewed by clicking on the tab at the bottom of the window (there's a status tab - the default, and an alerts tab). Alerts are ordered with the most recent at the top. I'll add a view option for the log in the future (like VirtualVP and VPLive have now).
3. The VM Usage is checked internally at the frequency set in the Check frequency set per program. However, the display is updated every 5 seconds. This is to avoid excessive screen updating (relatively expensive in terms of CPU usage). since the memory values can change frequently.
4. As you probably know, you'd divide the TaskManager KB value by 1024 to get the MB displayed in StartWatch. For most programs, these values should match, but not always. Memory is a complicated topic in windows, and there is no definitive value for a program's memory usage. Although the counter StartWatch uses is not the exact same counter TaskManager uses to display VM Size, the two values should be close. What values are you seeing that don't match?
Steve
