>> Sysinternals.com / however I have never heard of it before <<
Indeed...
Yes, AutoRuns does not come with XP while MSCONFIG does. MSCONFIG in a pinch, AutoRuns any other time.
>> Virtual Memory - if you do not clear it out it bloats up to fill the hard drive, a waste of space. <<
Not how I would word it - Windows can manage the page file size, and it won't grow larger than the maximum size you tell it to. This is not "bloat", but how Windows manages memory.
>> have seen a few rare cases where the details of VM info had been reloaded into RAM following a reboot <<
??? I wouldn't be so sure it was "details of VM info". There are a lot of things going on behind the scenes in Windows (prefetcher, etc) that can "load" stuff that had previously been loaded into memory.
>> clearing VM is a good maintenance activity that may or may not affect your RAM operation - but should still be done <<
If, by VM, you mean the page file, note my original post. It's not performance related, but can have security implications, and can also impact shutdown times significantly. Generally speaking, let Windows manage the paging file, and forget about it.
>> I have yet to see a memeory manager that provides a moment to moment system performance enhancement as they do need resources to run <<
:) Much like "virtual memory uses some RAM to note what is in the VM" (in other words, Windows virtual memory manager requires some system resources in order to do what it is designed to do, much like any other program will consume system "resources").
>> I have seen them improve longer term system performance by eliminating most BSODs and the like <<
If 3rd party memory "optimization" utilities (such as this MemTurbo that you talk of) eliminated most BSODs, why doesn't MS buy / build one and shove it into Windows? The fact of the matter is, the memory management / "optimization" routines / algorithms in Windows are sufficiently complex and purposely constructed to be efficient - they have to be. Further, BSODs are caused by faulty drivers or hardware. Period. User-mode programs (running in ring 3) cannot, by design of Windows, cause a BSOD. Thus, the claim that a memory "optimizer" utility can prevent a BSOD seems a bit odd.
>> many of which are caused by insufficient RAM to run a program or part of a program. <<
BSODs caused by insuffucient RAM? See above. If an application requests the allocation of more memory, and Windows informs the application that Windows cannot satisfy the request for an allocation of the requested size (E_OUT_OF_MEMORY), and the application wasn't written to handle that type of condition, the application is likely to crash, possibly with an access violation (0xc0000005) or some other error. If a driver running in kernel mode (ring 0) fails to handle the allocation failure properly, this can cause a BSOD. The problem, though, is a bad driver - the driver didn't properly handle a condition it could feasibly be faced with.
>> Students found that opening and closing Word several times caused the system to crash with a general protection fault due to 'insufficient memory' <<
The _SYSTEM_ crashed with a GPF? What do you mean by system? The operating system? Talk of GPFs takes me back to the days of Windows 9x / ME, and yet you indicate this happened on an NT4 system. If it caused the _SYSTEM_ to crash (BSOD), I would suggest a driver issue, as (again) drivers or faulty hardware cause BSOD crashes, not user-mode programs. If it was MS Word that "crashed" with the "GPF" (in NT, this type of error would likely be called an access violation) I would expect Dr. Watson to have kicked in and created a log and a USER.DMP. One could then analyze the log or dump file to determine what module was causing the crash, and that could potentially indicate how the problem might be fixed (MS Word add-in causing a problem? AV or other program hooking the process? Something that an Office service pack would fix?)...
>> Installation of MemTurbo set to recover when available RAM below 25 MB resulted in MemTurbo running and clearing the RAM and the system did not crash. <<
I don't suspect MemTurbo would fix this type of problem. Certainly, its function could alter (indirectly) the execution path of Word so the "thing" that caused the problem was "avoided"...
>> Every time he ran it the system crashed. <<
Again, what is meant by "system" - the OS? Windows Explorer? The game? What was the "crash" (what was the error code, and in what manner was it presented)? Was it always the same?
>> Investigation suggested a memory problem <<
What type of investigation? How is "memory problem" defined? Insufficent RAM? Bad RAM? I don't think MemTurbo truly fixed the problem...
Certainly, you are able to recount scenarios where MemTurbo seems to have positively affected problems you witnessed. But I suspect that further / more detailed investigation into the problems would have turned up alternative solutions that would not have required MemTurbo or similar programs / "utilities".
I recommend checking out the book "Windows Internals by Mark Russinovich (Sysinternals / Winternals guy) and David Solomon.
http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?z=y&isbn=0735619174&itm=1