fitwell said:
omega, thanks! I just wanted to mention that after a reinstall, I go
into registry and delete the two references to RTF that word leaves
then right-click to get the OPEN WITH... context item (since I'm in
Win98SE), and then associate RTF to WordPad and then Word never
bothers me again. Of course, it would if I accidentally opened an RTF
somehow in Word, but that's no easy to do. So just an fyi that Word's
proprietary nature _can_ be circumvented quite easily through rededit
re RTF.
Word taking over RTF, my memory is fuzzy. Whether it is only upon install,
or probably as well when you update its install. Possibility about when
opening an RTF with it, that made me curious, whether it would use that
excuse for a takeover. Just now I tested.
The one I have installed is Word2000, aka Word 9x. I just now watched my
registry for what would happen if I used it to open an rtf. Surprise: it
didn't do anything bad. It's this version that I've had installed for the
past several years, the one who has committed hostile takeovers on me. So
must be it occurred just during times I'd submitted to its update or repair
installation procedures.
Next, for test, I tried Word97, ask Word8...
I've never had Word97 installed on this machine. The MSOffice 97 directory
is extracted from a previous machine, and sits on my removable drive. The
apps run, despited not being installed. They automatically insert a bunch of
CLSID, Typelibs, etc into the registry, change paths of things to point to
themselves, and then are happy to proceed.
Word97's behavior was bad. And the report shows this for the part about
which .xxx associations changed:
HKLM\Software\CLASSES\.doc @ "Word.Document.8"
HKLM\Software\CLASSES\.rtf @ "Word.RTF.8"
HKLM\Software\CLASSES\.rtf Content Type "application/msword"
Since there could be some chance that this behaviour is specific to my
setup - that is, due to Word8 viewing things as "first launch" - I tried
a next step. I cleaned my registry key for .rtf, above, set it back to
normal; but left in all the other stuff that Word97 added. Then relaunched.
This time it didn't change the .rtf key.
So, based on what you said, together with my going ahead to take a closer
look: it seems to be that Word does the hostile takeovers only when it
is being first run, installed, updated, that sort of thing. Therefore,
yes, clean up after Word, reset your associations, only at those times.
After that, all we have left to worry about are all the other ill-behaved
programs out there. 8-o
.. . .
On a different note, want to mention how convenient it was to run this test
using EpsilonSquared's Installwatch. The registry snapshots took less than
twenty seconds.
And I find highly usable its interface, for viewing reports on such things.
There the benefit of using a registry logger, like Installwatch, instead of
a dedicated uninstaller, like TUN.
The prog gives me the original state of any registry keys with changed
values, so I can merge what I want right back to that state. And also gives
me the "after" state of the keys, as a .reg file, in case I later decide
those are changes that I want.
The one part of the prog that is weak, for purposes of this kind of
restoration, is that the removal of newly added keys requires using an
external program, to insert the minus (-) operator through the .reg file.
Still ideal, this prog, to see the before and after states of certain keys.