Hi, Xeno86!Well first of all, not 2 bytes twice but 20 bytes. If I changed 2 bytes I would completely limit maximum cache size setting, while this fix leaves you the freedom and flexibility to set it to whatever value you want (max 800M). It only affects default (automatic) value.
Well, change 2 bytes twice is not much a patch.
Secondly, what kind of fix did you expect for this particular issue? I'm open for ideas and discussion.
If you can do better - prove it
It's certainly better than the "workaround" advised by Microsoft
Reduce the amount of memory that is installed in your computer to 512 MB or less.
... and it can be easily slipstreamed into Windows installation CD.
I now have had time to analyze your patch, and I have to strongly disagree with Tihiy:
You patch is concise, elegant and to the point. And far better than the classic "two bytes twice" aproach, because it alters only the default value, while allowing for "MaxFileCache" values both above an below the default, provided they are not above 800 MB. My compliments!
Keep on the great work! You rock!