jo said:
I'm happy with the changed key; Edxor loads as fast as Notepad and is
much better.
Since it's common for us to put our preferred text editor in the windir
with name notepad.exe (as you had it), makes it best that other developers
have not taken the pre-judgement course that is apparently in effect here.
And, unimportant, but my thought is that HostsToggle's route shouldn't
even be necessary, its automatic call for Wordpad; that is, not even for
systems that do in fact have the MS Notepad in place there and in a w9x
environment. As I remember, the MS Notepad pops up a message on its own
about not being able to handle file size exceeding X kb, while offering
to load it with Wordpad.
This workaround we've arrived at for using HostsToggle, to point to a
different editor name, it's good at least that it does the trick. And
there are no disadvantages.
Even perhaps a couple of small advantages, in having specific text
editor name there. For ex, I change my "txtfile" default handler around
periodically, when I want to provide some new editor with that extended
auditioning opportunity. While I do this, I leave my solid standby
"notepad.exe" binary (Win32pad for me) in the windir, still handling
various other filetypes and roles. In other words, I enjoy allocating
some division of labor, and not have my current notepad.exe alone for
all the various textual filetypes.
I'd say too that having the specific editor entry in the txtfile key
could reduce the immediate impact of experiencing a nasty editor installer
overwriting the notepad binary in the windir. Well, ok, I can remember no
examples of that specifically. (Maybe only because the MS SystemRestore
thingy would often make that futile). Instead where I see hostile takeover
behaviour occur as a pattern, its reg association changes committed by
installers. Well, as far as file overwrite method, do have one story ...
Name of the criminal in this tale is ScriptPad*. This is not a report
about an installer. Those often do lots of bad things. But at least they
only do them once. How a program behaves each time it is launched, that
is the serious matter. ScriptPad, on any run, it does a couple of small
nasties, and then one major one. First, it always forcibly copies an lnk
to itself into the sendto folder. Second, it writes an entry into the
registry trying to demand to be put in an htm openwith list. Now, the
biggy. Whenever it is launched, it automatically copies its huge 1250kb
corps into the sysdir. When it does this, it names that file notepad.exe.
Since the order of path lookup is such that sysdir is first, before windir,
the consequence is that ScriptPad immediately takes over everything where
"notepad.exe" is associated and/or called.
In an area where you see a lot of megalomania already, editors who pull
tricks to try to seize take-over of Notepad's position, ScriptPad surely
wins top prize, in its audacity.