UltraEdit not anymore in program list of Windows Explorer

moscaluc · May 04, 2006#12006-05-04T20:15+00:00

Ladies and gentlemen,

I have a question for you.
Why in my program list under windows, I have not the possibility to open a file with UltraEdit, even if I click on "browse" button and I select the exe file?

Since I remove old version (9.2) and I install 11.00, I can do it anymore.

Is someone could help me?

Thanks in advanced.

moscaluc

Mofi · May 05, 2006#22006-05-05T11:07+00:00

Sounds extremly strange. Something is really corrupted on your machine.

First you should update to latest v11 of UltraEdit. I suggest v11.20a for Win9x and v11.20b for Win2k and WinXP. Write an email with your authorization code to IDM support with the request for the installation zip-file you want (localized version?). This update is free for registered v11 users. I can see in readme.txt of v11.20b that there are several crashes of UE v11.00 fixed in next version 11.00a at startup of UE.

Can you start UltraEdit with the shortcut and open the file with the file open dialog or by Drag & Drop? (Test if the installation is OK.)

Can you click on the Windows Start button, select Run and enter the full command line, for example:

"C:\Program Files\IDM Computer Solutions\UltraEdit-32\uedit32.exe" "C:\path to your file\name of your file"

Does this work?

If you previously have had v9.2 maybe the uedit32.ini is the problem. Locate it in the Windows directory and rename all uedit32.* files for example to uedit92.* while no instance of UltraEdit is running. Start UE v11 and it will create a completely new uedit32.ini. This new uedit32.ini is maybe not in the Windows directory anymore. It will be in the hidden directory %APPDATA%\IDMComp\UltraEdit. %APPDATA% is an environment variable which depends on your OS installation. It is something like "C:\Documents and Settings\your windows user name\Application Data".
Open again a file from within the Windows Explorer.

Note: Other UE files at the location of the uedit32.ini are: Advanced.*, Basic.* and uedit32v??.cfg.

If nothing helps, download Filemon and Regmon from SysInternals install both (unpacking the zip-file), run both and capture all disk and registry accesses while you try to open a file with UltraEdit from the Windows Explorer.

moscaluc · May 05, 2006#32006-05-05T14:09+00:00

Yeh,

You save me guy!
Thanks a lot for what you do.
It's working perfectly.
but for your information, I made a mistake in the version of my UE, it is v11.20+5.
Bye

moscaluc

citternist · May 12, 2006#42006-05-12T17:19+00:00

Mofi wrote:Sounds extremly strange. Something is really corrupted on your machine.

This seems like a rather disingenuous (and scary!) response. Perhaps the problem is ultraedit's (lack of clean uninstall or install bug) & not a corrupt machine? Anyway, I've got the same problem. I wanted to update from v11 to v12.00a. Uninstalled v11, got rid of all old uedit files that I could find. Uedit v12 works fine but can't add .sas files to the list:

Right click on file in Windows Explorer/open with/Choose program : UltraEdit not listed and even if I browse & point to the program it doesn't hold.
In UltraEdit: configuration/file associations -- type .sas into FileTypes box but the 'add' button isn't highlighted.
In fact, in the file associations menu -- if I click on a file type already in there neither is the 'delete' button highlighted.

Tried Filemon but can't make much sense of it. About the only thing I thought strange was Windows was trying to access the old area where I had installed UltraEdit:

Code: Select all

FASTIO_QUERY_OPEN    C:\Program Files\UltraEdit\uedit32.exe    PATH NOT FOUND    Attributes: Error

For the new installation, I used the default folder: C:\Program Files\IDM Computer Solutions\UltraEdit-32\

These entries also seemed strange:

Code: Select all

C:\Program Files\IDM Computer Solutions\UltraEdit-32\uedit32.exe.Manifest    NOT FOUND    Options: Open  Access: All
C:\Program Files\IDM Computer Solutions\UltraEdit-32\uedit32.exe.Config      NOT FOUND    Options: Open  Access: All

Mofi · May 12, 2006#52006-05-12T18:26+00:00

I think, it is not a problem of the uninstall and install process. Windows, especially Windows XP, tracks and records many (nearly all) user actions in the registry. I think the keys you post here are from such automatic Windows records or from your user made assignments. For example if you decide once to open a file with an extension not associated with any program and choose a program for open it, but disable the option to always open it with this program, Windows XP still records it and at the next time you try to open again a file with this still not registered extension it suggests you the program you have used once.

Also it is a known problem that NO uninstaller removes file assignments done by the user itself (and most also for the assignments done by the program itself). Well, this is fine if a user uninstalls the program and installs a newer version into the same directory. The user made assignments will work immediately after the new installation again.

But if the user installs the program into a different directory or wants to open the file with extension ??? with a different program, he must fix the assignment always manually. I have not seen till now any uninstaller which is able to uninstall files and registry keys not created by the installer. Nearly all uninstallers do not uninstall registry entries or files created by the installed program itself at first start of it or later during the work with it. They are not logged in the installation log file and so are not removed by the uninstaller when it undos the actions of the installation process.

You have to open Windows Explorer - Tools - Folder Options - File Types and look at the list of registered file types. Broken or invalid assignments can be easily detected by looking at the icon of the file type. If a file type has the standard icon for unknown file and after clicking on the file type you see below the line Open With: nothing, this file registration is broken. I guess, your registration for *.SAS is such a broken assignment. Fix it in Windows Explorer with button Change or Advanced and the appropriate further steps necessary.

If you think you have enough experience with the registry and Regedit you can also start Regedit and search for uedit32.exe and fix all path specifications of uedit32.exe in the registry.

Note: My manually created log of changes of the registry reports following for the UE v12 installation and first start of UltraEdit (post here only the top levels of the keys):

[HKEY_CURRENT_USER\Software\IDM Computer Solutions]

[HKEY_LOCAL_MACHINE\Software\Aspell]

[HKEY_LOCAL_MACHINE\Software\Classes\*\shellex\ContextMenuHandlers\UltraEdit-32]
@="{b5eedee0-c06e-11cf-8c56-444553540000}"

[HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}]

[HKEY_LOCAL_MACHINE\Software\IDM Computer Solutions]

[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\View Source Editor\Editor Name]
@="C:\\Program Files\\IDM Computer Solutions\\UltraEdit-32\\uedit32.exe"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{43B6667D-7520-4186-B05B-F5C0494C495D}]

[HKEY_LOCAL_MACHINE\Software\TOOLSIDM]

Everything else in the registry with uedit32.exe is created by you (manually or with UE) or by Windows and not by the installer of UE.

The search of Windows for program filename.Manifest and .Config is not strange. Windows XP does this for all applications at every start of an executable. These files can have special informations and config settings for the program which Windows must know to handle for example a multi-user environment with more than one user currently active and running the same application. If you are interested in these files use a WWW search engine and search for .manifest and .config.

citternist · May 12, 2006#62006-05-12T19:12+00:00

Well, after searching on the web I found this program that solved my problem:

http://windowsxp.mvps.org/openwithadd.htm

moscaluc · May 12, 2006#72006-05-12T19:18+00:00

Thanks a lot citternist!

ciao

ububba · May 13, 2006#82006-05-13T03:33+00:00

I was helping a user today that was having problems making file associations to UE v11. He had originally installed v10.x in error and then uninstalled and installed v11.10a. Whenever he would try to do an association we noticed the icon associated with UE in his select programs list was the generic windows file icon versus the UE icon. I found the program entry in the registry was pointing to the UE shortcut on his desktop. I doubt UE uninstall or install did this...he probably did it himself, but I'm not exactly sure how. Anyway, I thought I'd share it just the same.

Below is the incorrect registry entry, the path to the lnk file should of course point to the UE executable file. Once I fixed this, his problem was resolved:

[HKEY_CLASSES_ROOT\Applications\UltraEdit-32.lnk\shell\open\command]
@="\"C:\\Documents and Settings\\All Users\\Desktop\\UltraEdit-32.lnk\" %1"

rpurban · May 27, 2006#92006-05-27T02:31+00:00

FWIW - This problem is not an isolated case. I came here looking for an answer to exactly the problems described here. (Could not force an association with standard Windows GUI options; browsing to executable wouldn't 'take')

I had no reason to edit the registry around Uedit, so any gap or corruption came during the install or upgrade. I'm on v11.20b. Upgraded from 10.x

The only 'unusual' thing about my installation is that I install to Drive D rather than C.

-=Rich=-

Mofi · May 29, 2006#102006-05-29T13:15+00:00

Users having problems with the file associations with UltraEdit should read the Microsoft article Understanding MS Windows File Associations.

rpurban · May 29, 2006#112006-05-29T18:30+00:00

The article addresses how to add new types and associate programs, but does not address the problem of adding UltraEdit as the default for existing types; nor does it address why UltraEdit won't 'take' when you attempt to add it. UEdit is a great program, but there is a minor bug somewhere in one of the upgrade paths (unless it's a problem with version 11 installation generally)

May 29, 2006#122006-05-29T21:22+00:00

I did a bit more investigation and discovered the following:

The path to UltraEdit on my computer is:
"C:\Program Files\IDM Computer Solutions\UltraEdit-32\uedit32.exe"

On my computer I discovered that the registry key:
HKEY_CLASSES_ROOT\Applications\uedit32.exe\shell\open\command
was set incorrectly to "C:\Program Files\UltraEdit\uedit32.exe" "%1"

(note the missing IDM directory in the path)

whereas HKEY_CLASSES_ROOT\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32 (default)
was set correctly to point to
C:\Program Files\IDM Computer Solutions\UltraEdit-32\ue32ctmn.dll

This is certainly NOT something I would normally have had reason to edit. When I corrected the first entry I was able to find UltraEdit on the list of choices to associate with files without having to browse to the program.

By way of observation, I also find two entries related to IDM in the registry
HKEY_LOCAL_MACHINE\SOFTWARE\IDM Computer Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\IDM Computer Solutions, Inc.

The first of these includes a key that the second does not
HKEY_LOCAL_MACHINE\SOFTWARE\IDM Computer Solutions\UltraEdit-32\SpellChecker

I don't know if I changed the default location of an earlier version not to point to the IDM subdirectory, or whether the IDM subdirectory came in with a new version - but the difference in the registry made all the difference in how it functions.

-=Rich=-