jcnassoc <alex-luyando_at_jcn-associates.com> wrote on 10/30/2008 01:03:12
PM:
> I've had this problem in the past and found the solution on the
Avanquest
> site worked. Since then I needed to reinstall PowerDesk and I am back to
the
> same problem, except when I try to use the fix from the
PowerDesk/Avanquest
> site I find no registry keys that match. I also don't find any
Wow6432Node
> entries. Ugh!!
Lionel works on a 64 bit system. The fix below just disabled the
32 bit version of either TSVN or PowerDesk. 64 bit versions would
be unaffected. That means both won't collide anymore in 32 bit
applications while TSVN would still be available in the standard
64 bit Windows Explorer.
> Can anyone give me some ideas on how to handle this. What a pain! LOL
>
> By the way, even though Avanquest has a "fix" for this, I think that
entry
> is not the same as the one that was on their site a few months ago. In
fact
> the link to the "fix" I found in this thread is a dead-end on their site
> now.. not sure what that's all about.
> Lionel Guilhou wrote:
> >
> > Small update about this, in case someone else is still using PD7 :)
> >
> > After some tinkering in the registry, I found a way to 'fix' the
problem:
> > removing the context menu handlers for either Powerdesk or TortoiseSVN
in
> > both
> > HKCR\Wow6432Node\*\shellex\ContextMenuHandlers and
> > HKCR\Wow6432Node\Directory\shellex\ContextMenuHandlers
> >
> > Of course, Powerdesk's context menu is the one to go :)
> > After that, TSVN's menu shows and works just fine.
-- Stefan^2.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-11-06 16:30:37 CET