SUCCESS. You were right on the fix, that CLSID
{23170F69-40C1-278A-1000-000100020000} in RegSeeker did the trick, it found 7
keys, 2 were drophandlers, I deleted them, got back my simple menu w/o 7zip.
Please forgive my posting a followup so very late. Since I'm resurrecting
a thread that has aged during my major tardiness, I'll try to refrain from
rambling too much.
Mainly, I wanted to say I'm glad to see you stuck to it, and got success.
And 7zip works in the normal contect menu nearly as before, I can live with it.
I'll hope that they allow more specific choice in the future. First of
all, to allow, via the prefs interface, that which you wanted, separate Y/N
on context vs dragdrop.
As well, to provide for what I wanted: to make a dragdrop menu that is
pertinent to the context. That is, per filetype (ie compressed filetypes),
and not obtusely global, apppearing everywhere, anytime you perform a drag
drop operation, as it is now. It turns out, to my surprise, that the regkey
insertion technique that I expected to work, it does not, an unfortunate
(and odd) limitation of the DLL's coding.
Not that I feel strong sense of complaint towards 7-zip. Not long ago
(~15 months ago), I decided that I wanted was ready to leave PowerArch,
to find something that was equally capable (very happy with its capabilities
and style of shell integration), but that behaved itself properly regarding
the registry. Mainly, that did not autocreate on run an obnoxious slew of
filetype keys; I really hate that behavior. One after another on trying the
majors, almost everyone in the group committed atrocities of this kind. I
even became desperate for a while, and set an ancient Winzip 6 (I've a
licensed copy - present from msft, strangely), as my default, since it at
least behaved itself. Naturally that did not last too long, functionality
limits due to vintage. Anyway, to get to the point: one after another of
the majors all failed to meet my criteria of clean behavior, with the sole
exception of 7zip.
Regarding 7zip, it does these days have a problem situation, IMO, with the
installer. Unless I overlooked (?), it is available strictly in installer
form. And that installer, NSIS (Nullsoft Scriptable Install System), as
far as I can tell, cannot be manually extracted. You have to run it and
let it do its thing. What that means is that when upgrade 7zip, Mike, you'll
have to repeat the operation you did, to remove those dragdrophandler keys.
For the near future, the installer has the same plans. I found a directory
showing the raw scripts for current releases.
http://www.7-zip.org/dl/
eg
http://www.7-zip.org/dl/7zip436.nsi
: WriteRegStr HKCR "Directory\shellex\DragDropHandlers\7-Zip" "" "${CLSID_CONTEXT_MENU}"
: WriteRegStr HKCR "Drive\shellex\DragDropHandlers\7-Zip" "" "${CLSID_CONTEXT_MENU}"
I personally think it'd be easier to keep a .reg file in the directory where
you keep 7-zip.
-------------Delete7zipDragDropMenu.REG--------------------------
REGEDIT4
[-HKEY_CLASSES_ROOT\Directory\shellex\DragDropHandlers\7-Zip]
[-HKEY_CLASSES_ROOT\Drive\shellex\DragDropHandlers\7-Zip]
-------------Delete7zipDragDropMenu.REG--------------------------
Or naturally you could use RegSeeker as you did. (Regseeker does only delete
the value and not the key, which it leaves empty, but ok, at least that
achieves the end result that you need.)
I tried the Export feature on RegSeeker, don't know how it works.
I tried to illustrate that in the pic thing I put up. I wasn't trying to be
cryptic, just too lazy/hurried to type explanations.
http://www.redshift.com/~omega/clips/regseeker/searchkeys/searchexport.htm
The mystery part is that when you click the export command, it silently
creates a file in its Backup directory. So you need to access that export
..reg file from outside RegSeeker, to then do with it what you will.
What is unnatural there is that you'd reasonably expect a File SaveAs
dialog to pop up when you hit the export command. But that is lacking;
instead the op is silent, as described.
Wish it copied to Clipboard.
I'd like that, too.
One workaround, lieu of that, is to click RegSeeker's context command "Open
in Regedit." Regedit then has the command "Copy Key Name."
(Btw, I personally prefer to see targeted keys in their full context given
by aregistry editor interface, instead of deleting values blindly in a "reg
cleaner" program.)
.......
// OOOOOPs. So much for my goal to keep this post brief!
........
Many thanks for the help, Karen, and as always, I save your posts for reference.
Thanks for the flattery.
Btw, your new computer arrive?
I have to get one myself...but, bizarre as might sound to some, I am utterly
traumatized by the idea of "moving." 8-o
As to OS. I'll likely install w98 in one partition to lessen the drama of
transition. As to primary OS, though, I'm poised to take a Big Leap ahead
thru Time and install Windows 2000.
