On 1/17/07, George V. Reilly [EMAIL PROTECTED] wrote:
Phil Edwards wrote:
7.0 is running fine on all my other systems, it's only this 64-bit XP
box that doesn't see the new menu entries. I can't even get an Edit
with... entry to appear; that seems to be gone or restricted or moved
or.
Try saving the following to vim.reg and executing that:
REGEDIT4
[HKEY_CLASSES_ROOT\*\Shell\Open with Vim\command]
@=\c:\\Program Files\\Vim\\vim70\\gvim.exe\ \%1\
On 1/17/07, jk [EMAIL PROTECTED] wrote:
Put a shortcut key to send to...!
Thank you both for your replies.
As it happens, neither of those helps, because the shell extension is
not being used at all. After some more research, I've found that
32-bit shell extensions are not loaded into the 64-bit Windows
Explorer, regardless of registry entries (like the first suggestion).
I would not be happy using the proposed workaround in the second
suggestion, but since the entries will not appear *anywhere* in the
context menu -- it's all or nothing -- it won't matter. :-)
I found after I sent my message that it's not just a Vim thing,
either; any 32-bit shell extension will not be used. Programs like
WinRAR or Winzip have the same problems. The real solution is to
build a 64-bit shell extension, but that's going to be beyond the
casual user.
The most common workaround, it turns out, is to run a copy of the
windows explorer in a 32-bit mode, e.g., a desktop shortcut pointing
to C:\windows\syswow64\explorer.exe /separate. (What does syswow
mean? Don't ask, I have no idea.) The /separate runs the file
manager in its own 32-bit process space, and suddenly all the shell
extensions are working.
This has drawbacks; the 32-bit explorer has its own view of the world
that isn't necessarily related to what the rest of the computer is
thinking. What's more, any software that *has* installed 64-bit shell
extensions will not show up in this copy.
