On Sun, 20 Jun 2004 23:33:28 GMT, "Wesley Vogel"
Agreed! Drag it out and shoot it until it stops twitching, then
scorch the corpse! (De-analogy: Remove it via IE Tools, Options;
double-check via Regedit after a shutdown/restart, then rename away
MDM.EXE from within your maintenance OS of choice)
Watch your back with this basket, because even when IE's "front door"
settings say it's suppressed, you may find it running anyway. It's
(re)inflicted as a siede-effect of installing MS Office or (less
unreasonably) any software development tools e.g. MSDN.
The reason why it's bad news, is that it pollutes the Windows base
directory with zero-byte files; sometimes thousands of them.
Why does that matter, if they are after all zero bytes?
Because each pair of directory entries (the "real" 8.3 plus an LFN)
bloats up the cluster chain of the Windows base dir as time goes by -
making that critical directory chain longer and fragmented, thus
increasing the critical window period when it has to be updated.
Although this location should should be updated seldom, it isn't -
think registry flushes in Win9x, for example - even if you don't have
a brain-dead MDM continuously creating junk files there.
And as the Windows base dir is likely to be "always in use", it may be
that Defrag can never repair the fragmentation of the dir, even after
the gunk build-up has been cleared away.
Don't you just hate bad software design?
-------------------- ----- ---- --- -- - - - -
Tip Of The Day:
To disable the 'Tip of the Day' feature...
