In an earlier posting I had reported problems with error messages and memory leak when using ShutDownWindows>2.
In version 7.2.033 the problem seems to have been corrected. The error messages are not occurring.
But I was still seeing what appeared to be a memory loss.
My initial tests in 7.2.033 were still showing a loss of about 3% every time I used the script to logoff and then login again. I did some additional tests using the Logoff selection from the Start Menu, and got the same results, average of 3% reduction in System Resources.
Conclusion: I am happy, and embarassed to report that what I had reported as a Macro Scheduler memory leak is really a problem with Windows. This is not a Macro Scheduler problem.
Thanks for resolving the error message problem.
Sorry about any confusion with the reporting of a memory leak.
(Do you think Microsoft will be as responsive as MJT in resolving this problem? Don't bother to answer that rhetorical quesion.)
