Expierence of Enhancing existing projects with mORMot

The original blog with the same title is from one of the mORMot author here

What I want to add to the list are:

1. You can use SynZip to replace your Zip library. In my case, I use Abbrevia component set for Zip and Unzip, but Abbrevia contains many units and if only the Zip and Unzip of functionality are used, it might be worth to using much more small SynZip
2. You can replace your base64 routines with mORMot's as it is much faster when the data to be encode/decode is big

A disadvantage of UPX

UPX (Ultimate Packer for Executables) is a free and open source executable packer (https://en.wikipedia.org/wiki/UPX). It makes your executable smaller thus speed up the loading and transfering. I have been using it for many years and have had no problem at all until few day ago I discovered an serious issue with it.

When UPX compress your executable, it not only compress the code inside the executable, but also compress the resource data in the executable, thus the resource data becomes not readable for other applications, one scenario is that you compile message table into your executable and use this executable as the resource file for some settings such as use it as the value of "EventMessageFile" for defining your own Event Log source in the Windows registry, unfortunately, if you do so, firstly, the Event Log view will not find the descriptions for your event's ID and category, secondly it might crash your Windows Event Log service and even worse, the service might not be able to recover even its Recovery setting has been set up.

You can reproduce what I have say in following steps:

1. Download UPX from https://github.com/upx/upx/releases/tag/v3.91 (latest release at the time this blog is written)
2. Find an Event Log source from within "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application",  whose EventMessageFile is an EXE and it has some events you can see them in Event Viewer
3. Use UPX to compress the EXE you have found in step 2
4. Restart the Event Log viewer if it is open
5. Check the event then you can see that the first sentence is something lik "The description for Event ID xxx from source yyy cannot be found"
6. Try to filter on current log to show event only from that chosen source, the event view might crashes because the Windows Event Log service has crashed by now in some cases.