UE v11.00 crashes on delete while using split window (fixed)

[keithscarfe]

I am using version 11.00 and have a problem which I am not sure if it is a bug (does anyone else suffer from this) or if it is me.

When I have the window split, editing a single file, e.g. a big file with one part in the top window and somewhere else in the same file in the bottom part, sometimes UE bombs out with no warning or message, no windows general error type window. It just disappears. The file that was being edited is not saved. I have lost a lot of work up to now and this is very annoying. I now have learned to pres ctrl-s after every couple of lines of edits. It never happens when the window is not split.

Any ideas anyone? Does this happen to anyone else? Should I Email IDM to ask? Would a newer version fix it?

[Mofi]

In readme.txt of UltraEdit v13.10 I can read for UE v11.00b:

- Crash with split windows and delete

So it is a known bug and it was fixed.

[keithscarfe]

Ok thanks for that. I suspected this. Where did you read this please? Can I get this read.me from somewhere without upgrading? It looks like I will have to get the latest version. Problem is it is a corporate license so will be a nightmare to do.

[Mofi]

To get a specific file without installing UltraEdit you can use the MSI installer packages of UltraEdit.

Download the ZIP archive and unpack the file ue_english.msi.

With WinRar you can now select the file ue_english.msi and click on button "Extract To" to extract all the files in the package to a temp directory. The file you are interested in is readme.txt121

If you have Total Commander you can do same when you have installed also the MSI packer plugin. Then a simple double click on ue_english.msi opens the MSI archive. You can see some files and the important one is Cabs.w1.cab. A double click on this file and the MSI plugin extracts the cab file to a temp directory and then Total Commander reads its content with its built-in CAB unpacker. Pressing key F3 on the selected file readme.txt121 forces Total Commander to unpack this file from the CAB archive and displays it with the lister.

If you don't have WinRar or Total Commander with the MSI plugin, I'm sure, all you need is already installed on your Windows computer to unpack the MSI archive without installing it. But I don't know the commands and command line parameters to unpack a file manually from an MSI package. I have purchased WinRar and Total Commander, so I'm not interested in the complicated way to unpack a file from an MSI archive.

Well, you can also contact IDM support per email and ask for the readme.txt of UltraEdit v13.10a.

[pietzcker]

And since the bug was fixed in 11.00b, you won't need a new licence (if you don't need UE's new features since V12/13). Just ask IDM support for the latest version of the V11 UE "family", telling them your registration details.

[jorrasdk]

Question to Mofi:

Well, you can also contact IDM support per email and ask for the readme.txt of UltraEdit v13.10a.

Since some of the postings in this forum has simple anwers in readme.txt for later versions than the version the user is using, could it be an idea to place the readme.txt from the latest version in the forum as a sticky in the general subforum?
Or is there perhaps reasons why this would be bad, say IDM would object for some reason?

[Mofi]

Well, many history lines are already available on this website. A user just have to look into the news archive (News Topics) for the news articles which start with "Announcing" or search in the forum for topics IDM created when a new major release is published.

But a page with full history as in readme.txt of UltraEdit and UEStudio would be fine, especially for UltraCompare and UltraSentry where there is no readme.txt with a history.

However, I think, such a full history page should not be a forum topic. IDM itself should host it. I have had temporarily posted a full history for UltraCompare (with the lines from the UltraCompare news), but I have already deleted this forum topic. IDM should have the control over what is made public in WWW and what not.

But as requested by IDM as you can see at top of the page, a user should first contact IDM support per email when he has found a bug. And a crash is definitely a bug.

Contact IDM per email and make the suggestion to host 1 page for every product with full history because of users with a version not the latest one often run into a well-known problem already fixed with a later version and then ask for help in the forums.

[jorrasdk]

I sent the suggestion to IDM about hosting an online readme.txt for each product. They forwarded the suggestion to the webmaster for consideration.