Uwe said:
Hmm. I read the CacheSet docs again. Now I think that it's
possible that SetSystemFileCacheSize is not more than a
Win32 function that wraps the NT API functions used by
CacheSet. In this case SetSystemFileCacheSize is not better
than CacheSet and I made my litte tool in vain.
Lol. These things happen. I think the Sysinternal CacheSet works with
all NT versions not just Server 2003 and Vista. The strange thing is
that with almost anything Windows everything is picked apart by all the
experts and non experts alike and almost all flaws and warts are usually
discovered and exposed in a somewhat timely manner. I find it hard to
believe that if an important bug like this was such a prevalent problem
that the experts would have not blown the whistle a long time ago and
that Microsoft would have been able to keep this a "secret".
This problem was first reported in the early NT4 days and apparently was
"supposed" to have been fixed with Service Pack 4 or 5. Surely with the
subsequent releases of other NT4 service packs and then all other
Windows versions up to Vista, Microsoft should have by now fixed such an
important problem. But then Microsoft sometimes says that it fixed
problems when actually little changes. Microsoft's advice when
commenting on System Cache and performance has always been to add more
RAM, not to limit it to something like 256MB. Here is an interesting
read on the subject:
http://attrition.org/security/denial/w/ntfilec.dos.html
And this detached thread is an interesting bit on the same subject:
http://www.rage3d.com/board/showthread.php?s=&threadid=33658212&highlight=delay+write+failure>
That is an interesting post that may explain some of the reasons for the
often missing or damaged registry hives problem or damaged file system
and accompanying BSOD at boot up. This busted hive problem and the
often damaged files system seems to me to be too frequent without an
underlying cause, for quite a while now I have thought that the XP NTFS
version was inherently flawed but have never once said so because that
is just a gut feeling that I have, I cannot find information to
substantiate that. I find it a bit far fetched that a perfectly good
registry set or file system on a properly shutdown computer should be
completely scrambled without any good reason on the next boot! Few
things have been conclusively answered in this thread but interesting
questions have been raised.
John
