There was probably another problem. There is ALWAYS another problem.
I don't disagree. There is always something else.
3. The KB article explicitly mentions fragmentation.
So it does. However it doesn't say that you could fix that by running a ram defragmenter. If you could, MS would have included a little ram defrag routine into the hibernate code :)
Just like Microsoft included a full disk defragmenter with XP? The way they included anti-spyware software with it? The way they included anti-virus with it?
Nope, It's not the MS way to include the full suite of tools needed to keep your box running. That's what they 3rd part market is for!
4. In my experience, use of the ram defragmenter tool eliminates the hibernation issue.
I'd be shocked if it did anything like defragmenting....
Despite this, it IS possible that this could help with the old hibernating with over 1GB of ram issue, as only physical ram needs to be saved to disk when hibernating. If you've just forced everything into the pagefile, there will be very little to write. However, this is a side-effect of what the program actually does, not it actually working, and the problem with hibernating with lots of ram has been fixed now.
Nope. Thinking that perhaps you were right, I disabled the "questionable" software. After going into standby twice during the workday, it blue screened on the third "wake up."
Could be mere coincidence, or it could be that the software adds value. I'm going with the latter.
The problem is not fixed. Windows does not wake reliably.
5. Windows is STUPID when it comes to seeing more than 1GB of RAM. Look into the gyrations required to to enable the PAE settings. Yikes!
PAE is enabled by default in Windows these days, it just doesn't use the extended address space feature on the desktop versions, only things like NX.
PAE is required to see more than 3 to 3.5 GB of ram, not 1GB.
Bzzt! Wrong answer! My machine did not see more than 2GB until I enabled PAE.
PAE was not enabled by default on my machine! There were arcane incantations required in order to make the configuration change.
What you state simply does not match my experiences over time. You may be right for some use cases, but they seem to be exclusive of *my* use cases.
Respectfully,
Anomaly