File context window

uniden9 · Post by **uniden9** » 10 Jun 2008 16:34

I'm new to the product and love it. I have one question regarding the file context window. Litte forehand information, I'm using Windows Vista SP1 x64. I'm also using XYExplorer v7.10.000, registered.

I can get Take Ownership and WinRar to display consistently, but I can not get ultraedit or textpad to display. I'm not sure if they were before or not.

Ultraedit is present in:
HKEY_CLASSES_ROOT\*\ShellEx\ContextMenuHandler
HKEY_CLASSES_ROOT\Wow6432Node\*\ShellEx\ContextMenuHandler

Winrar has the above and Directory, Drive, Folder which are not necessarily needed for file editor. Am I missing anything to getting this to show up in XYEplorer? For reference, I have no issue getting the context to work correctly with windows explorer. My only goal is to get Ultraedit into the context menu. Some sort of reg hack is acceptable.

Thanks again,

Justin

jacky · Post by **jacky** » 10 Jun 2008 16:52

Well, XY relies on the shell to show extension on the content menu, it does not filter anything obviously, so if you see some you should see all of them.

I don't really know, but I think I've read before that if you're on a 64bits system, XY will only show 32bits extensions -- whereas I assume Explorer would show both. Maybe that could be linked to your problem, and you need to have UE install a 32bits shell extension or something ?

Post by **admin** » 10 Jun 2008 19:35

jacky wrote:I don't really know, but I think I've read before that if you're on a 64bits system, XY will only show 32bits extensions ...

Correct. This is true for any 32-bit application under 64 bit Windows.

uniden9 · Post by **uniden9** » 11 Jun 2008 01:36

Yes, most of my context window are loading 64bit dlls, even for 32bit applications. Textpad, Ultraedit are both using a 64 bit dll. What is strange is WinRar is loading a 32 and 64 bit dll. My attempts to emulate winrar with ultraedit have so far been unsuccessful. For winrar in the shellex\Winrar and shellex\Winrar32, each pointing to the correct class id, which references the 64/32 bit dll. I'm assuming this is why it is working.

Thanks,

Justin

uniden9 · Post by **uniden9** » 12 Jun 2008 05:03

I found a much easier solution to my problem. I could not get the 32bit shellex dll to work, so I tried a more manual approach. This should work for other applications as well.

This requires a registry hack, but is relatively easy. You manually add the commands to registry hive : HKEY_CLASSES_ROOT\*\shell:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\ultraedit32]
@="Open with UltraEdit"

[HKEY_CLASSES_ROOT\*\shell\ultraedit32\command]
@="C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit\\uedit32.exe %1"

Note the double slashes are because this is a registry export and '\\' is really entered as single slash '\' in regedit.
Both the 'ultraedit32' key was added and its sub key 'command'.
The '@' shows up as Default in regedit.
The default/'@' for HKEY_CLASSES_ROOT\*\shell\ultraedit32 is how it will show up in the context menu. Obviously the 'command' default/'@' is what is executed. Every registry value type is a string value.

This information came from another webpage:
http://jameser.blogspot.com/2006/07/tip ... s-for.html

Code: Select all

Warning this is a registry modification.  
Please proceed at your own risk.  It is possible to fatally break your system with manual registry modifications/tweaks.  If you are set on doing this, at least take a manual windows system restore, restore checkpoint before hand. That will allow most registry damage to be undone.

.

Thanks,
Justin