I've installed EurekaLog 7, but do not see any EurekaLog-related items in IDE?

Solution:

1. Use Start/Programs/EurekaLog 7/Manage menu item to launch EurekaLog manager (make sure you close IDE before doing that and make sure to run the Manage tool under administrator account).
2. Select you IDE version and click on "EurekaLog 7 with IDE expert" button to install and activate EurekaLog 7 for your IDE.
3. (Optional) If you work under a different user account - you may need to run Manage tool from that account too.

Additionally:

• If the Manage tool does see your IDE, but says that EurekaLog's DCUs are not installed and "Register" buttons are disabled - please, reinstall EurekaLog and make sure that you have your IDE checked during installation.
• If the Manage tool does not see your IDE or if your IDE is not present as an option during installation of EurekaLog - this means that registry entries to your IDE are missing/invalid/broken. EurekaLog uses registry to locate your IDE, so if your registry does not contain correct information - then EurekaLog will not be able to find your IDE.

You can fix broken registry entries:

1. An easiest way is to run "Repair" or "Reinstall" option of your IDE's installer;
2. Alternatively, you may install EurekaLog manually (e.g. using the /Force* command line switches);
3. Finally, you may repair registry entries for your IDE.

EurekaLog installer looks for path values in the registry. For example: HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\8.0\RootDir=C:\Program Files (x86)\Embarcadero\RAD Studio\8.0\. See also this table.

Important: don't forget about Wow6432Node node on x86-64 machines. Check out both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER.

Additionally, EurekaLog requires personalities to be listed under \Personalities registry sub key for your IDE.

See also:

• Common installation problems
• V6 -> V7 upgrade guide

I'm trying/evaluating trial, but I get this message for my specific application:

---------------------------
Error.
---------------------------
The "MyApplication.exe" program is compiled with EurekaLog 7.8.0.0 TRIAL version.

However it appears that you forgot to configure EurekaLog for your project.

Please, use "Project" / "EurekaLog options" IDE menu item to enable and configure EurekaLog.

See: https://www.eurekalog.com/tutorials_delphi.php

(Note: only full EurekaLog version allows using EurekaLog units without activating EurekaLog).
---------------------------
OK 
---------------------------

Reason:

Normally the message about using EurekaLog Trial edition appears when your application is expired. This happens after 30 days since compilation of the application. However, if compilation date can not be retrieved - then application is also considered expired. 

In other words, if you see this message immediately after compilation - then this means that EurekaLog was not run to post-process your project. This can be due to some kind of installation problem or project configuration problem:

1. A very common reason for this issue is dropping TEurekaLogEvents components on the form without actually configuring EurekaLog for your project;
2. One of another common reasons for this is disabling EurekaLog per specific build configuration (say, 'Release'), but not removing EurekaLog's units from application. You can disable EurekaLog for build configuration by removing EUREKALOG conditional symbol from configuration. EurekaLog is enabled for all build configurations by default (once you configure it for your project), so this can happen only when you change your settings manually. See below for diagnostic;
3. Another possible issue is mixing files from different EurekaLog versions. If EurekaLog code do not match injected EurekaLog's data - then EurekaLog's data are considered to be unknown version and will not be loaded. Thus, compilation data will not be retrieved and your executable will be "expired". See below for diagnostic;
4. Finally, check that your .dpr file does not have any IFDEF that modify project's type (e.g. program/library/package) or hide/duplicate uses clause. EurekaLog uses a very simple source code parser, which is unable to follow conditional defines. Therefore, EurekaLog may not be able to detect output file, because file's extension comes from project's type;
5. This message could also appear if you are trying to disable EurekaLog in your application. For example, you have disabled EurekaLog in the application, but some of your units still contain one of EurekaLog's units in uses clause.

Solution:

1. If you are trying to enable EurekaLog in your project:
   1. If you dropped TEurekaLogEvents component on your form, but did not configure EurekaLog via "Project" / "EurekaLog Options..." IDE menu command - do it now. Please, see this guide on using EurekaLog or watch video tutorial.
   2. You can check output from EurekaLog. Use "View" / "Messages" IDE command to open build log (older Delphi/C++ Builder IDEs do not have such command; introduce non-used local variable to get "hint" from compiler about unused variable; EurekaLog's messages will appear in the same window). Build your project and watch messages from EurekaLog. A sample output of normal compilation may look like this.
   3. For installation issues - please see this guide.
   4. For post-processing issues - please see this guide.
   5. You can check version of EurekaLog's code and data by using Module Informer (PE Analyzer) tool (which is available both in EurekaLog and EurekaLog Tools Pack).
   6. Check-list:
   •  
     • Make clean re-installation (with uninstalling previous version before installation, including re-downloading installer)
     • Clean old .dcu/.obj files of your project
     • Use Start / EurekaLog 7 / Manage tool to verify exact installed and registered version of EurekaLog
     • Check project and IDE search paths
     • Check project configuration (application type)
     • Ensure that your project source does not override program/library/package keywords with IFDEFs
     • Analyze output from EurekaLog
     • Use Module Informer (PE Analyzer) tool to check compiled executables
2. If you are trying to disable EurekaLog in your project:
   1. Go to IDE's "Project" / "EurekaLog options" menu item and click on the "Reset" button to remove EurekaLog from the project;
   2. Simply remove/comment all references to EurekaLog's units from your code. You can use constructs like {$IFDEF EUREKALOG}uses EBase;{$ENDIF} to avoid changing your source code each time you enable or disable EurekaLog;
   3. In particular, if you have dropped TEurekaLogEvents component on your form and then have removed it - make sure to manually remove EComponent unit from uses clause, because IDE will not automatically remove this unit when you delete the component;
   4. Make sure that the error message is actually about your project. Ensure it is not about DLL/package that is being used by your project.
   5. If you are unable to find which of your units references EurekaLog - do the following:
      1. Close your IDE;
      2. Go to "Start" / "Programs" / "EurekaLog" / "Manage EurekaLog in IDEs";
      3. Click on your IDE in the shown dialog;
      4. Click on "Unregister EurekaLog";
      5. Run your IDE;
      6. Open your project;
      7. Use "Project" / "Build Project" (not "Compile", not "Make");
      8. If any of your units contained referenced to EurekaLog's units - IDE/compiler will complain, so you can easily spot this and remove;
      9. Once you have fixed the problem - close your IDE and return to step 3;
      10. Click on "Register EurekaLog (recommended)".

See also:

• Compiling your project with EurekaLog
• Troubleshooting guides

I get "Installer's executable is not signed" / "Installer's executable has not been signed" message when installing EurekaLog on Windows 2000, Windows 2003, or Windows XP.

Reason:

Missing SHA-2 (SHA-256/SHA-512) support is the reason for failed signature check on installer, because certificates for HTTPS and digital signature use SHA-2. 

• Windows 2000: does not support SHA-2.
• Windows 2003: does not support SHA-2 out of the box. Support for SHA-2 can be installed by installing KB 938397 (for Service Pack 1); KB 968730 (for Service Pack 2). We also highly recommend to install KB 2868626.
• Windows XP: support for SHA-2 is available since Windows XP SP3. We also highly recommend to install KB 2868626.

Solution:

• Windows 2000: please, contact our support, we will help you to install EurekaLog manually.
• Windows 2003: install Service Pack 2, install KB 968730, install KB 2868626. Verify that:
  • version of crypt32.dll is 5.131.3790.5235 or higher;
  • version of wcrypt32.dll is 5.131.3790.5235 or higher;
  • version of rsaenh.dll is 5.2.3790.3959 or higher;
  • version of w03a3409.dll is 5.2.3790.5235 or higher.
• Windows XP: install Service Pack 3, install KB 2868626. Verify that:
  • version of crypt32.dll is 5.131.2600.6459 or higher;
  • version of xpsp4res.dll is 5.1.2600.6459 or higher;
  • version of rsaenh.dll is 5.1.2600.5507 or higher.

You can verify that SHA-2 support is available in your system by opening our web-site in Internet Explorer:

• If SHA-2 support is present - you will see our web-site.
• If your system does not support SHA-2 - you will see "The page cannot be displayed" error message.

It is important to use Internet Explorer specifically for this test, as it uses system DLLs as the back-end, while other browsers (like Chrome, Firefox, Opera, etc) cary their own implementation, so they can open SHA-2 web-site even when host system does not support SHA-2.

Download links (English versions):

• Windows XP x86:
  • KB 968730
  • KB 2868626
• Windows XP x64:
  • KB 968730
  • KB 2868626
• Windows 2003 x86:
  • KB 968730
  • KB 2868626
• Windows 2003 x64:
  • KB 968730
  • KB 2868626

You may need to obtain corresponding updates manually. E.g. if you have OS in different language.

Additional notes:

• Please note that EurekaLog's code itself still works on Windows 2000, Windows 2003, and Windows XP systems. For example, you can develop your application on Windows 7 and deploy it on Windows 2000 - it will work just fine. Only installation of EurekaLog is not supported for Windows 2000.
• We used double-signing earlier (e.g. sign with both SHA-1 and SHA-2 at the same time). Unfortunately, our old SHA-1 certificate has expired a long time ago, and all new certificates are available in SHA-2 only. Sadly, we can no longer support installation on Windows 2000 - simply because we can not get SHA-1 certificate anymore. 

See also:

I get "The connection with the server was reset" or "An error occurred in the secure channel support" errors

I get one of the following errors when I visit EurekaLog's web-site, or trying to install EurekaLog:

• 12031 / ERROR_INTERNET_CONNECTION_RESET ("The connection with the server was reset");
• 12157 / ERROR_WINHTTP_SECURE_CHANNEL_ERROR ("An error occurred in the secure channel support").

Reason:

EurekaLog uses WinInet / WinHTTP to make secure internet connections. Therefore, EurekaLog relies on operating system's support for SSL/TLS. The mentioned errors occur when client and server can not negotiate on common encryption protocol or exact details (ciphers).

Solution:

• Install latest service pack for your operating system;
• Install latest Internet Explorer for your operating system;
• Install latest updates for your operating system;
• Enable latest encryption protocols, disable obsolete protocols:
  • Open Internet Explorer;
  • Go to "Tools" / "Internet Options" menu;
  • Switch to "Advanced" tab;
  • Scroll down to "Security" section;
  • Disable "SSL 2.0", "SSL 3.0", enable "TLS 1.0" or "TLS 1.1", "TLS 1.2", and "TLS 1.3" (depending on which options are available; we recommend to disable "TLS 1.0" when "TLS 1.1", "TLS 1.2", or "TLS 1.3" options are available and enabled);
• Download license file manually from web-site using another machine

Important Note: EurekaLog's web-site uses SHA-2 certificate for SSL/TLS connection. Therefore, support for SHA-2 must be present in your operating system when you install EurekaLog. EurekaLog itself does not require SHA-2 support.

See also:

• Unable to install EurekaLog on Windows 2000, Windows XP, Windows 2003

Reason: 

Solution:

External references:

1. Please, make a clean reinstallation of EurekaLog by following these guidelines:
   • EurekaLog 6.
   • EurekaLog 7.
2. Delete all .dcu/.obj files of your project and make full rebuild (Project/Build all).
3. Go to Tools/Options/Environment options/Delphi options/Library and check search paths:
   • EurekaLog 6: check "Library paths" value. There should be path like "C:\Program Files\EurekaLab\EurekaLog6\Delphi16". If path is not present - add it. If path is present - check that file C:\Program Files\EurekaLab\EurekaLog6\Delphi16\ExceptionLog.dcu/pas really exists and it is readable.
   • EurekaLog 7: check "Library paths" value. There should be path like "C:\Program Files\EurekaLab\EurekaLog7\Lib\Win32\Release\Delphi16". If path is not present - add it. If path is present - check that file C:\Program Files\EurekaLab\EurekaLog7\Lib\Win32\Release\ExceptionLog.dcu really exists and it is readable. (substiture Win32 for your platform; read more about proper EurekaLog 7 IDE settings)
4. Go to Project/Options/Directories and remove any paths, which seems related to EurekaLog.
5. Use Project/"View source" command and check "uses" clause of your project. See if there is any EurekaLog-related lines like

   ...
   ExceptionLog in "folder-which-doesn't-exist",
   ...

   If such line present - try to remove it and re-activate EurekaLog in your project via Project/EurekaLog options command.
6. If nothing else helped - use Project/"View source" command, find EurekaLog units in "uses" clause (if it's not present - add it) and manually specify a search path for each unit like this:

   ExceptionLog in 'C:\Program Files\EurekaLab\EurekaLog6\Delphi16\ExceptionLog.pas"

   or like this:

   ExceptionLog in 'C:\Program Files\EurekaLab\EurekaLog6\Delphi16\ExceptionLog"

   Then make a full project rebuild.

• (Re)Installation of EurekaLog 6
• (Re)Installation of EurekaLog 7
• Forum discussion

I upgraded to the new version of EurekaLog and now my old project can not be compiled (there are multiply compilation errors).

Reason:

Two major versions of EurekaLog may contain breaking changes.

Solution:

1. Delete old .dcu/.obj/.hpp files of your project.
2. Study changes in the new version of EurekaLog.
3. Read through upgrade guide or check the reference.
4. (EurekaLog 7 only) Enable "EurekaLog 6 compatibility mode".
5. Make sure that you have the correct version of EurekaLog activated in your IDE.
6. Make sure that your project doesn't have conflicted search paths set.
7. Make a full rebuild of your project (not just compile).

See also:

• Upgrade guides

When I've installed EurekaLog 7 - my IDE crashes on startup, during compilation or when exiting.

Reason:

• Delphi and C++ Builder IDEs are 32-bit processes, which are limited to 2 Gb of address space. There are also other known limits (such as command-line length, environment variables length and search paths length). Probably you have too many components and extensions installed, so when you install or use EurekaLog - these limits are reached.
• EurekaLog may conflict with other IDE extensions that also set hooks in IDE. Known examples are AQTime, madExcept or JCL. We're investigating these issues.
• In rare cases there may be a conflict with other external software. Typically antivirus/firewalls.

Solution:

First of all - upgrade to the latest EurekaLog version (your issue may already be fixed).

1. Try to remove unused components and extensions, try to remove search paths for unused components or re-arrange them to move EurekaLog first. If you can not remove any component or extension - then you can use EurekaLog without using EurekaLog IDE expert. Please read this article fore more information.
2. Try setting the "Project" - "Options" - "Delphi Compiler" - "Use MSBuild externally to compile" option to True. This will cause the compiler to run out of process (as a standalone process), which means a bit more free memory to actually do the work.
3. Go to Tools/EurekaLog/IDE options and uncheck "Catch IDE expert errors" options, then restart IDE.
4. Try to disable checking for updates (Tools/EurekaLog/IDE options).

Note:

Please note that limitations of 32-bit processes do not depend on your installed hardware memory (RAM) and disk space.

See also:

I get "File XYZ was compiled with different version of ABC" error when trying to compile my project with new version EurekaLog (I used the previous version of EurekaLog with fine result).

Reason:

It seems that there was some kind of installation issue, so now your project uses the mix of two different versions of EurekaLog. It also may be that EurekaLog is not registered in your IDE or registered inproperly. Another uncommon reason for this error is using old/obsolete version of the same IDE without installing latest update packs.

Solution:

1. Check your IDE. EurekaLog is compiled against the latest IDE updates/patches/hotfixes. It is possible that the latest version of RTL/VCL for your IDE is not fully binary compatible with older version of RTL/VCL. Therefore, if one of unit names mentioned in the error message belongs to RTL/VCL (like Windows, SysUtils, etc.): 
   1. Check that your IDE has all latest updates/patches/hotfixes installed (recommended). 
   2. If you have Enterprise edition of EurekaLog (comes with full source code) - then you can recompile EurekaLog for older version of RTL/VCL (not recommended).
2. Check virtualization:
   1. If you are using old IDE version on modern OS - see if there is anything related to your IDE, your project, or EurekaLog in the C:\Users\username\AppData\Local\VirtualStore folder. 
   2. Try to run your IDE under administrator account (or visa versa).
3. Clean up the project:
   1. Wipe output folder of your project. 
   2. Check project's search paths. Make sure that your project do not contain explicit search paths to other EurekaLog version.
      • Make sure that your IDE does not contain explicit search paths to other EurekaLog version.
   3. Be sure to clear your project from old .dcu, .obj and other generated files. 
   4. If the error message mentions a specific unit - search your hard drive for that unit with any file extension.
   5. Try to run a disk-wide file search for EurekaLog and your project files. See if there are any unexpected duplicates.
4. Clean up EurekaLog installation:
   1. Try to make a clean reinstallation by following guides in help (EurekaLog 7 guide, EurekaLog 6 guide).
   2. Activate the correct EurekaLog version for your IDE - via Start/Programs/EurekaLog 7/Manage menu item.
   3. Sometimes it's possible that IDE do not update changes in settings. Try to run Start/Programs/EurekaLog 7/Manage tool and click on "No EurekaLog" and then - on "EurekaLog 7 with IDE expert" (make sure you close IDE before doing that and make sure to run the Manage tool under administrator account).
   4. Try to install and configure EurekaLog manually by following this guide.

See also:

I get "Could not compile used unit XYZ" error when trying to compile my project with new version EurekaLog (I used the previous version of EurekaLog with fine result).

Reason:

It seems that there was some kind of installation issue, so now your project uses the mix of two different versions of EurekaLog. It also may be that EurekaLog is not registered in your IDE or registered inproperly. Another uncommon reason for this error is using old/obsolete version of the same IDE without installing latest update packs.

Solution:

1. Check your IDE. EurekaLog is compiled against the latest IDE updates/patches/hotfixes. It is possible that the latest version of RTL/VCL for your IDE is not fully binary compatible with older version of RTL/VCL. Therefore, if one of unit names mentioned in the error message belongs to RTL/VCL (like Windows, SysUtils, etc.): 
   1. Check that your IDE has all latest updates/patches/hotfixes installed (recommended). 
   2. If you have Enterprise edition of EurekaLog (comes with full source code) - then you can recompile EurekaLog for older version of RTL/VCL (not recommended).
2. Check virtualization:
   1. If you are using old IDE version on modern OS - see if there is anything related to your IDE, your project, or EurekaLog in the C:\Users\username\AppData\Local\VirtualStore folder. 
   2. Try to run your IDE under administrator account (or visa versa).
3. Clean up the project:
   1. Wipe output folder of your project. 
   2. Check project's search paths. Make sure that your project do not contain explicit search paths to other EurekaLog version.
      • Make sure that your IDE does not contain explicit search paths to other EurekaLog version.
   3. Be sure to clear your project from old .dcu, .obj and other generated files. 
   4. If the error message mentions a specific unit - search your hard drive for that unit with any file extension.
   5. Try to run a disk-wide file search for EurekaLog and your project files. See if there are any unexpected duplicates.
4. Clean up EurekaLog installation:
   1. Try to make a clean reinstallation by following guides in help (EurekaLog 7 guide, EurekaLog 6 guide).
   2. Activate the correct EurekaLog version for your IDE - via Start/Programs/EurekaLog 7/Manage menu item.
   3. Sometimes it's possible that IDE do not update changes in settings. Try to run Start/Programs/EurekaLog 7/Manage tool and click on "No EurekaLog" and then - on "EurekaLog 7 with IDE expert" (make sure you close IDE before doing that and make sure to run the Manage tool under administrator account).
   4. Try to install and configure EurekaLog manually by following this guide.

See also:

I get "File not found: XYZ" error when trying to compile my project with new version EurekaLog (I used the previous version of EurekaLog with fine result).

Reason:

It seems that there was some kind of installation issue, so now your project uses the mix of two different versions of EurekaLog. It also may be that EurekaLog is not registered in your IDE or registered inproperly.

There also may be a case when you have too many IDE components or extensions installed, so some kind of limit is reached and EurekaLog settings takes no effect.

Solution:

1. Check virtualization:
   1. If you are using old IDE version on modern OS - see if there is anything related to your IDE, your project, or EurekaLog in the C:\Users\username\AppData\Local\VirtualStore folder. 
   2. Try to run your IDE under administrator account (or visa versa).
2. Clean up the project:
   1. Wipe output folder of your project. 
   2. Check project's search paths. Make sure that your project do not contain explicit search paths to other EurekaLog version.
      • Make sure that your IDE does not contain explicit search paths to other EurekaLog version.
   3. Be sure to clear your project from old .dcu, .obj and other generated files. 
   4. If the error message mentions a specific unit - search your hard drive for that unit with any file extension.
   5. Try to run a disk-wide file search for EurekaLog and your project files. See if there are any unexpected duplicates.
3. Clean up EurekaLog installation:
   1. Try to make a clean reinstallation by following guides in help (EurekaLog 7 guide, EurekaLog 6 guide).
   2. Activate the correct EurekaLog version for your IDE - via Start/Programs/EurekaLog 7/Manage menu item.
   3. Sometimes it's possible that IDE do not update changes in settings. Try to run Start/Programs/EurekaLog 7/Manage tool and click on "No EurekaLog" and then - on "EurekaLog 7 with IDE expert" (make sure you close IDE before doing that and make sure to run the Manage tool under administrator account).
   4. Try to install and configure EurekaLog manually by following this guide. Try to specify EurekaLog search paths in IDE before other 3rd party libraries.
   5. Try to uninstall unused extensions and libraries. Try to clean search paths from unused folders.
   6. If this will not help - try to set search paths specifically for your project (not for IDE).

See also:

I get error message saying that installer/uninstaller has detected running EurekaLog instance and asks me to close it before continue with installation/uninstallation. However, I do not see any EurekaLog programs. 

Reason:

There may be hang EurekaLog application that is still running in the background.

Solution:

• Try to find and kill EurekaLog's processes manually.

or

• Restart your computer.

I downloaded and started installer. However, it hangs on start. Nothing happens.

Reason:

It is a known problem with Malwarebytes Anti-Malware tool. Its driver (mbamchameleon.sys) injects into CreateProcess call and cause infinite loop during check for digital signature of some signed executables.

Solution:

• Avoid mbamchameleon.sys:
  • Uninstall Malwarebytes (important: simple stop/exit will not help; even if services are off, the driver will continue to run)
  • OR
  • Use safe mode.
• Contact Malwarebytes support for help.

This is not EurekaLog issue, it is not specific to any EurekaLog version. An empty signed Delphi executable will exibit the same behaviour. The problem seems to be related to certain digital certificates.

I need to install old version of EurekaLog for one IDE and new version of EurekaLog for other IDE. In other words, I want to have two different versions of EurekaLog to be installed at the same time, on the same machine.

Solution:

EurekaLog 7.0-7.1 allows you to install EurekaLog 7 over EurekaLog 6 installation and switch between EurekaLog 6 and EurekaLog 7 by using "Manage" tool provided by EurekaLog 7.

Starting with EurekaLog 7.2, it is no longer possible to install EurekaLog 7 over EurekaLog 6. File layout was changed drammatically, and it is no longer compatitible with EurekaLog 6 file layout. Old version of "Manage" tool (v7.1.5, which is capable of working with EurekaLog 6) can be downloaded here: https://www.eurekalog.com/files/ManageProfilesV6.exe. See instructions below.

Starting with EurekaLog 7.5, additional tools is included into EurekaLog installer, so it is possible to automatically install EurekaLog 7 over EurekaLog 6. "Manage" tool for EurekaLog 6 will be installed automatically by EurekaLog 7.5+ installer.

Instructions for manual installation EurekaLog 7.2, 7.3, or 7.4 with EurekaLog 6

(not applicable to EurekaLog 7.0, 7.1, 7.5+)

You have to manually install both EurekaLog versions:

1. Uninstall any installed EurekaLog versions;
   • Perform a clean uninstallation (older versions) to be sure there are no leftovers from old installation;
2. Install older (previous) version of EurekaLog (v4, v5, or v6):
   • IMPORTANT: Install older version of EurekaLog FIRST;
   • Make sure that you checked only IDE which you want to work with this older EurekaLog version, and unchecked other IDEs. For example, you can install EurekaLog 6 for Delphi 7 only;
   • Complete installation as usual, make sure that older/previous version of EurekaLog works as expected in the installed IDE, make sure there are no EurekaLog visible in other IDEs;
   • IMPORTANT: Copy ecc32.exe/emake.exe files from \bin folder of the selected IDEs into corresponding sub-folder(s) of your EurekaLog installation. For example, C:\Program Files (x86)\Borland\Delphi7\Bin\ecc32.exe -> C:\Program Files (x86)\EurekaLab\EurekaLog 6\Delphi7\ecc32.exe;
3. Remove installation information about older/previous EurekaLog version:
   • Go to "Start" / "Run..." and type "regedit" to open registry editor;
   • Navigate to HKEY_CURRENT_USER\Software\EurekaLog;
   • Rename the "EurekaLog" key to something else. For example, "OldEurekaLog";
4. Install new (latest) version of EurekaLog (v7.2, v7.3, or v7.4):
   • IMPORTANT: Make sure that you are installing new version of EurekaLog into different folder; Do not install it in the same folder which was used at step 2;
   • IMPORTANT: You may install new/latest version of EurekaLog for the same IDEs as used in step 2. However, use caution when switching between EurekaLog versions in the same IDE - read remaks below for more info. It is recommended to install different EurekaLog versions into different IDEs;
   • Complete installation as usual, make sure that new version of EurekaLog works as expected in the selected IDEs;
5. Restore older/previous EurekaLog version:
   • Open registry editor;
   • Navigate to HKEY_CURRENT_USER\Software\OldEurekaLog;
   • Rename "OldEurekaLog" key to its original name ("EurekaLog");
   • Restore old EurekaLog IDE registration:
     
     • If selected IDE has EurekaLog 7 installed - remove EurekaLog 7 from the specified IDE (by using latest "Manage" tool);
     • Automatic (EurekaLog 6 only) - use old version of "Manage" tool to register EurekaLog 6 into IDE. IMPORTANT: Do not use old version of "Manage" tool to edit settings for IDEs with installed EurekaLog 7, do not use latest version of "Manage" tool to edit settings for IDEs with EurekaLog 6 - see remarks below;
     • Manual (EurekaLog 4, 5, and 6):
       • Copy previosly saved ecc32.exe/emake.exe file(s) into its proper location (\bin folder of IDE);
       • Use "Component" / "Install packages" IDE's menu command to register (C)ExceptionExpert.bpl file (for example: C:\Program Files (x86)\EurekaLab\EurekaLog 6\Delphi7\ExceptionExpert7.bpl);
       • Add directory containing the (C)ExceptionExpert.bpl file into Library Search Path setting of your IDE ("Tools" / "Environment Options" / "Library Path").
6. Done!

If you want to update/reinstall newer version of EurekaLog (v7.2, v7.3, v7.4) - perform such steps:

1. Remove installation information about older/previous EurekaLog version:
   • Go to "Start" / "Run..." and type "regedit" to open registry editor;
   • Navigate to HKEY_CURRENT_USER\Software\EurekaLog;
   • Rename the "EurekaLog" key to something else. For example, "OldEurekaLog";
2. Install new (latest) version of EurekaLog (v7.2, v7.3, v7.4):
   • Uninstall current v7 version;
   • IMPORTANT: Make sure that you are installing new version of EurekaLog into different folder; Do not install it in the same folder which was used at step 2;
   • Complete installation as usual, make sure that new version of EurekaLog works as expected in the selected IDEs;
3. Restore older/previous EurekaLog version:
   • Open registry editor;
   • Navigate to HKEY_CURRENT_USER\Software\OldEurekaLog;
   • Rename "OldEurekaLog" key to its original name ("EurekaLog");
   • Re-register EurekaLog 6 into desired IDEs as discussed above;
4. Done!

Important notes:

• Do not use latest "Manage" utility from EurekaLog 7.2-7.4 to change settings for IDEs with old EurekaLog versions (v6). You can use latest "Manage" utility to alter settings of IDEs with EurekaLog 7 only;
• Do not use old "Manage" utility from EurekaLog 7.1- to change settings for IDEs with EurekaLog 7.2+, use it only for IDEs with EurekaLog 6;
• Do not uninstall old/previous EurekaLog version (v4-v6), unless you have restored uninstallation information under "Uninstall" registry key;
• You may try to install EurekaLog 6 and EurekaLog 7 for the same IDE. However, use caution when switching between versions:
  • Use new "Manage" tool (7.2-7.4) to remove/install EurekaLog 7 from IDE;
  • Use old "Manage" tool (7.1-) to remove/install EurekaLog 6 from IDE;
  • Do not install EurekaLog 6 into IDE with installed EurekaLog 7: remove EurekaLog 7 (with new "Manage" tool) first, then install EurekaLog 6 (with old "Manage" tool);
  • Do not install EurekaLog 7 into IDE with installed EurekaLog 6: remove EurekaLog 6 (with old "Manage" tool) first, then install EurekaLog 7 (with new "Manage" tool).

After installing EurekaLog: if I double-click on the IDE project file (for example, .dproj) - a pop up dialog will be open, asking me to select application to open the file. I think it is a bug, EurekaLog should not change file associations.

Reason:

Our installer registers the new "Edit EurekaLog settings" action ("EditEL" verb) for all IDE project types (such as .dproj, .cbproj, etc.):

Please note that our installer does not change the file association. Your project files are still associated with IDE.

However, Windows 10 has the feature of showing you a dialog box where you can choose an application to open the file with - when you try to open a particular file, if you have multiple applications that can do so. This is actually helpful in a lot of scenarios, as it tells you to try the apps that you actually installed. 

Please note that the RAD Studio IDE (bdslauncher) is still a default choice in this dialog.

Solution:

1. Simply check the "Always use this app" checkbox and click on the OK button (the "Keep using this app" option should be highlighted by default).

2. If you do not like this feature of Windows 10 - you can disable it by enabling the "Do not show the 'new application installed' notification" group policy:

This policy removes the end-user notification for new application associations. These associations are based on file types (e.g. *.txt) or protocols (e.g. http:)

If this group policy is enabled, no notifications will be shown. If the group policy is not configured or disabled, notifications will be shown to the end user if a new application has been installed that can handle the file type or protocol association that was invoked.