Considering the fact that GeoDisk uses a few WindowsME files in a
non-supported manner, this can't really be considered a problem with
KB891711, at least not until some genius decompiles the whole thing and
figures out what's going on. Unfortunately, the author (MVP Emeritus
George Geyde) has been AWOL for nigh on a year, now. I seriously suspect
that he's met with an untimely demise and nobody in his "real world"
knew enough to (or how to) pass the news on to us. He was headed to sea,
last I heard, and he and I kept in pretty close touch up until that
time.

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"bobster" wrote in message
...
The previous release of KB891711 caused a BSOD when I tried to run the
scandisk/defrag program, GEODisk2. The "new improved" version causes
the
same problem. I have tried it both with the old and new versions of
KB891711 checked and unchecked in MSconfig/startup and the BSOD always
occurs when it is checked and never occurs when it is unchecked.
Surprisingly, that was the only problem I had with the original
version of
KB891711 and it still seems to exist with the new version.

This is a minor annoyance as I only scandisk/defrag about once a week
and I
can uncheck KB891711 in MSconfig, reboot and GEODisk2 runs just fine.
I
post this just to point out that the new version doesn't fix all the
problems that the original caused.