Charlie
Thu May 08 22:14:33 PDT 2008
Yes, I'd forgotten that workaround - running a 32-bit explorer window side
by side. Heck, I even blogged it way back when! Thanks for the reminder.
--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel
""Darrell Gorter[MSFT]"" <Darrellg@online.microsoft.com> wrote in message
news:xuxaAvWsIHA.4284@TK2MSFTNGHUB02.phx.gbl...
> Hello,
> That's right however you may want to try loading the 32-bit version of
> Windows Explorer:
> we always default to the 64-bit Explorer.
> Something like this:
> Drive_Letter :\windows\syswow64\explorer.exe /separate
>
> This articles I think talks about this.
> 895561 Some Windows Explorer extensions and some Control Panel items are
> not displayed on computers that are running an x64-based version of
> Windows
>
http://support.microsoft.com/default.aspx?scid=kb;EN-US;895561
>
>
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> | >From: "Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org>
> | >References: <48232a0b$0$2986$ba620e4c@news.skynet.be>
> | >In-Reply-To: <48232a0b$0$2986$ba620e4c@news.skynet.be>
> | >Subject: Re: Context menu problem
> | >Date: Thu, 8 May 2008 09:56:17 -0700
> | >Lines: 30
> | >Message-ID: <84C4ED90-F89F-48EF-B7AE-2A5BB4528694@microsoft.com>
> | >MIME-Version: 1.0
> | >Content-Type: text/plain;
> | > format=flowed;
> | > charset="Windows-1252";
> | > reply-type=response
> | >Content-Transfer-Encoding: 7bit
> | >X-Priority: 3
> | >X-MSMail-Priority: Normal
> | >X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
> | >X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
> | >X-MS-CommunityGroup-PostID: {84C4ED90-F89F-48EF-B7AE-2A5BB4528694}
> | >X-MS-CommunityGroup-ThreadID: 630E852B-1CA6-4860-812B-8F7EC9E6A4F4
> | >X-MS-CommunityGroup-ParentID: 630E852B-1CA6-4860-812B-8F7EC9E6A4F4
> | >Newsgroups: microsoft.public.windows.64bit.general
> | >Path: TK2MSFTNGHUB02.phx.gbl
> | >Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.64bit.general:17318
> | >NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
> | >X-Tomcat-NG: microsoft.public.windows.64bit.general
> | >
> | >You'll need a 64-bit version of the DLL. The problem is that a 64-bit
> EXE
> | >(Explorer, in this case) can't make an "inproc" call to a 32-bit DLL.
> (And
> | >the same is true in reverse, I might add.)
> | >
> | >--
> | >Charlie.
> | >
http://msmvps.com/blogs/xperts64
> | >
http://mvp.support.microsoft.com/profile/charlie.russel
> | >
> | >
> | >"Paul C" <me@somewhere> wrote in message
> | >news:48232a0b$0$2986$ba620e4c@news.skynet.be...
> | >>I run Server 2003 64 bits.
> | >> Before, I used Windows 2000 Pro. I had a small hexedit program (Yuri
> | >> Software HEdit), that installed in the context menu without problem.
> | >> This 32 bits program consists of 2 parts: an .exe and a .dll file.
> | >> I recently installed the same program under Server 2003 64 bits.
> | >> The program works fine, except for the fact it does not appear in the
> | >> file's context menu.
> | >> In the registry, it is present in HKCR\*\shellex\ContextMenuHandlers.
> | >> On the other hand I installed a compression program, 7zip (64 bits
> | >> version), that do appears in the context menu.
> | >> Anybody an idea of what I have to do to make the program appear in
> the
> | >> context menu? Do I have to put the dll elsewhere?
> | >> Thank you.
> | >> Paul
> | >>
> | >>
> | >>
> | >
> | >
>