User to user discussion and support for UltraEdit, UEStudio, UltraCompare, and other IDM applications.

This forum is user-to-user based and not regularly monitored by IDM.
Please see technical support page on how to contact IDM.
4 posts Page 1 of 1
I just got thru installing the 64-bit version of UE (replacing my earlier 32-bit version). I wondered whether I should uninstall the 32-bit version first. I know that all earlier upgrades were accomplished by installing OVER the prior version, but when going from 32-bit to 64-bit, it is not at all obvious that this will work (i.e. that the installation will take care of it).

I decided to take a chance, and indeed the installer recognized that I had an old 32-bit version, uninstalled it, then installed the new 64-bit version, and managed to keep all my settings intact. It worked great, but I do think that the company should add this info to their FAQ section and mention it in any emails they send out touting the new 64-bit version.

I realize that the FAQ says you should install OVER earlier installations, but the transition to 64-bit is a different kind of animal, and it is not obvious, IMHO. For example, some programs keep BOTH versions of a product on your system (e.g. PaintShop Pro), so it would be nice to have it spelled out.

Anyway, I can report that the 64-bit version does seem to start up significantly faster, which was one of my few complaints about UE. So, great job! :)
Had same experience and simply allowed UE to manage previous version and update. No issues on x64 Win7 or Win10.
I discussed update and upgrade scenarios by email with IDM during beta testing as 3 main use cases must be taken into account when updating/upgrading from a version of UltraEdit < 22.20 to version 22.20 (or in future a later version).

  1. UltraEdit < v22.20 is installed with a definitely different installer than UE v22.20 (or later) uses.
    This means an incremental update/upgrade is not possible at all. Either the user or the new installer needs to run first an uninstall of already installed UltraEdit to get rid off the files and registry keys of the old installer not used further in future.
  2. Installed is currently the 32-bit version of UltraEdit, but installer of 64-bit version is started now as the user wants to replace the older 32-bit by the latest 64-bit version.
  3. A user wants to use 32-bit AND 64-bit version of UltraEdit on same machine.
The installer of UE v22.20 first always checks if UltraEdit is installed already and which version is installed respectively with which installer the existing UltraEdit was installed. In case of detecting that existing UltraEdit was installed with a previous installer, it automatically runs the uninstaller of the already installed UltraEdit to delete all program files of UltraEdit and the files of the previous installer. The configuration files remain as the installers prior UE v22.20 do not even support removing application data, just removing the program files. This is done independent on running 32-bit or 64-bit installer of UE v22.20. So use case 1 and 2 are managed by the installer of UE v22.20.

The uninstall of UE < 22.20 is necessary in any case not just because of old installer removal, or upgrading from 32-bit to 64-bit version, but also because of different structure and file names in program files folder of UltraEdit.

However, it is always safe to first uninstall UltraEdit, restart Windows in case of shell extension DLL was used which can't be deleted immediately by the uninstaller as being loaded by Windows Explorer, and then install new version of UltraEdit. I do this for every application at least on every upgrade, i.e. first number in version (major version) changes. It is always good to uninstall an application from time to time when having made already several incremental updates. Uninstalling an application does not mean to get lost the application data, i.e. the users configuration for the application. All installers leave the application data on disk respectively in registry on uninstall, except the uninstaller has a special option to remove also the application data like new uninstaller of UltraEdit has. But this special uninstaller option must be always manually checked by the user. I have never seen an uninstaller offering an option to remove also application data with being checked by default.

On first start of uedit64.exe v22.20.0.25, the configuration files in %APPDATA%\IDMComp\UltraEdit from a previous uedit32 installation are taken over. So for most users the entire user configuration is kept after an upgrade from 32-bit UE < v22.20 to 64-bit UE v22.20.

But some configurations were overlooked like having stored the user configuration in Windows registry instead of files as by default, or the file associations made with UltraEdit with previous 32-bit version of UltraEdit not being updated automatically to 64-bit version of UE on first start of uedit64.exe, see this post by forum member Everyone.

I'm quite sure that a hotfix version of UE v22.20 or UE v23.00 at the latest will take care also about registry values and registry keys which need to be modified by uedit64.exe on first start after upgrade when all users detecting such an issue report it also by email to IDM support so that IDM Computer Solutions are aware of those migration issue.

Installing both, 32-bit and 64-bit version is possible into different directories, but currently NOT recommended because UltraEdit is not designed for a dual installation of both versions. For example uedit64.exe uses uedit64.ini and uedit32.exe uses uedit32.ini. This is not really useful for a user using both versions of UE at the same time as it can be expected that no users wants to make changes in configuration twice or have different histories for each version of UE. I think, there is also a problem with FTP/SFTP/Telnet/SSH registration when having both versions of UE installed on a machine.

Let's see if there will be enough users really wanting support for dual UltraEdit installation and appropriate data and DLL management, and if IDM Computer Solutions make appropriate adaptations for 32+64 bit installations like my favorite file manager Total Commander supports. In my estimation there will be only a few users who want both versions installed on same machine for same user (in same program files directory). I would like it, but only for making forum support easier for me in future on answering forum questions related to 32-bit or 64-bit version, not for my personal usage. I have currently just 32-bit version of UE v22.20 installed on my Windows 7 x64 computer.
Best regards from Austria
Interesting summary of all the issues, Mofi. It makes me feel good that I was right (such a rare occurrence!) in thinking it isn't as simple as it might seem at first.

As far as dual installations (32 and 64), it is not likely that many people would want it, IMHO, except for people like yourself who do diagnostics and problem solving of UE itself). Image editors (e.g. Corel PaintShop Pro) MUST allow dual installs (if they want to be friendly to their users), because of things like old scan drivers, and 32-bit-only Photoshop-compatible plugins, which will not run properly in 64-bit more. This doesn't seem like it would be an issue with UE (except maybe some kind of OCR use?).

Anyway, my 64-bit installation seems to be working fine, so good stuff.
4 posts Page 1 of 1
cron