![]() Second, before Windows Vista and Windows 7 with UAC the shell extension was always registered during installation as system key (except when a custom installation was executed with the option for Explorer integration unchecked). And please verify also before import if the 64-bit shell extension of UltraEdit is not registered with exactly the same keys.įirst, your post reads like you want to tell your opinion IDM, but this is a user-to-user forum as stated at top of every forum page. I have taken this path from another forum page and I don't know if this is correct and can't verify it. HKEY_CURRENT_USER\Software\Classes\Wow6432Node \CLSID HKEY_CURRENT_USER\Software\Classes\Wow6432Node C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit \\ue32ctmn.dll"īut before you import this to your registry, please check with Regedit.exe if the key HKEY_CURRENT_USER\Software\Classes\Wow6432Node \CLSID\] I don't have any 64-bit computer, but from what I have read on other pages, copying following into an ASCII file, adapting the path to ue32ctmn.dll according to your installation, saving it as UE32ShellExt.reg and double clicking on this file to import it to your registry should be enough to register the 32-bit shell extension too. Instead of HKEY_LOCAL_MACHINE now HKEY_CURRENT_USER is always used to make it possible to add/remove the shell extension registration from within UltraEdit at Advanced - Configuration - File Associations also by a user without administrator privileges.Īnd the default path to ue32ctmn.dll is now different. UltraEdit v17.10 registers the 32-bit shell extension DLL ue32ctmn.dll on a Windows XP SP3 x86 (32-bit) like posted in right click to "open in UltraEdit" with 2 differences:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |