Root > Quick start tutorials > Installation > Installation for AppWave or without IDE installed

Installation for AppWave or without IDE installed

Previous pageReturn to chapter overviewNext page   

General concepts

Application virtualization is software technology that encapsulates application software from the underlying operating system on which it is executed. A fully virtualized application is not installed in the traditional sense, although it is still executed as if it were. The application behaves at runtime like it is directly interfacing with the original operating system and all the resources managed by it, but can be isolated or sandboxed to varying degrees. In this context, the term "virtualization" refers to the artifact being encapsulated (application), which is quite different to its meaning in hardware virtualization, where it refers to the artifact being abstracted (physical hardware).


Examples of application virtualization technologies are: AppWave, Windows XP Mode, Wine, BoxedApp, Citrix XenApp, Novell ZENworks Application Virtualization, Endeavors Technologies Application Jukebox, Microsoft Application Virtualization, VMware ThinApp, etc.



Embarcadero AppWave

AppWave Store is an app store for Windows which uses application virtualization to avoid the hassles and risks of the usual Windows install process. The idea is that purchasing apps for Windows will be as simple as installing an app on a mobile using the Apple app store or Android Market. The underlying technology was developed to simplify deployment of Embarcadero’s tools. The All-Access subscription includes a tool box application that lets you run tools using “InstantOn”, which means no installation, just click and run.


In addition to the standard installation executables for AppWave applications, Embarcadero provides AppWave Apps versions of each product. Through the Embarcadero AppWave Store you also have access to many free apps from other parties. Apps simplify deployment and enable side-by-side versioning. When AppWave Browser is not running in Turbo mode, such as in a locked-down desktop environment, Apps are ideal because they do not affect system files or system registry settings.


AppWave Apps run within their own space without sharing DLLs or system-wide settings that could conflict with other applications. Application data, including configuration and license information, is stored locally on the hard disk, separate from the executable itself. AppWave Apps run on the local machine and are launched from the network using AppWave Browser. Apps launched from AppWave Browser benefit from application streaming because the application will begin to open before the product has been fully downloaded. However, if you need frequent access to an application, you should download and run the file locally, which is typically faster than running it from AppWave.



Technical issues

EurekaLog installer may be unable to gain access to settings and configuration of virtualized Delphi or C++ Builder IDE (such as IDEs with All-Access licenses, AppWave versions of classic IDEs). This depends on exact solution which you're using to virtualize applications. For example, AppWave version of Delphi is isolated from host machine/OS, so EurekaLog installer will not be able to "see" it during the installation.


Normally, you should try to run EurekaLog installer within virtualized environment, so EurekaLog installer may get access to IDE's settings. Otherwise EurekaLog installer would act as if there is no IDE installed (since it can not detect virtualized IDE).



Installation guide

There are two possible methods available:


Option A: Please, refer to documentation on your virtualization software to know about running two applications (i.e. Delphi/C++ Builder IDE and EurekaLog installer) within the same virtualized environment (sandbox). EurekaLog installer will be able to detect installed IDE and install and register EurekaLog properly when it is running in the same environment as IDE itself. Installation process should not be different from normal installation (with respect to specifics of used application virtualization solution).


Option B:

(You can also use this option to install EurekaLog on machine without any IDE installed, or when IDE installation is corrupted)

You can instruct EurekaLog installer to install necessary files even there is no IDE installed. Of course, EurekaLog installer will not be able to properly register EurekaLog into (non-existent/invisible) IDE - you still have to perform manual installation. To force-install files for a specific IDE - please, run EurekaLog installer with the following command-line switches:





M is either 'D' or 'C' - to indicate Delphi or C++ Builder IDE
V is integer version of IDE. You can determine integer version of your IDE by using this table.


For example, to install EurekaLog files for AppWave version of Delphi XE4:


EurekaLog7-Enterprise.exe /Force_D18


To install files for RAD Studio XE4 (i.e. both Delphi XE4 and C++ Builder XE4):


EurekaLog7-Enterprise.exe /Force_D18 /Force_C18


To install files for Delphi 7 with corrupted installation/registration:


EurekaLog7-Enterprise.exe /Force_D7


EurekaLog installer will act as if IDE was detected - i.e. installer will show you normal checkboxes for IDE's files during such installation. You should see a typical set of all necessary files (i.e. .dcu/.obj, .bpl, etc.) after installation - assuming that you did not cleared checkboxes.


Please note that EurekaLog's "Manage EurekaLog in IDEs" tool will not work - because it will not see installed IDE(s). You have to register EurekaLog manually. That is (simplified instructions):

1. (Optional) Copy necessary files to location where your IDE (or your build tool) can see it. We recommend to copy at least EurekaLogCore.bpl package to 32-bit System folder (like C:\Windows\SysWOW64\)
2. Specify paths to EurekaLog files:
a. Add %EUREKALOG%\Lib\%PLATFORM%\Release\%IDENAME%\, %EUREKALOG%\Lib\Common and %EUREKALOG%\Source\Extras\ folders to "Library Paths"/"Search Paths" option.
b. Add %EUREKALOG%\Source\ folder to "Browsing Paths" option.
c. Add %EUREKALOG%\Lib\Win32\Debug\%IDENAME%\ folder to "Debug DCU paths" option.
d. Add %EUREKALOG%\Lib\Common\ folder to "Include paths" option.
3. (Optional) Register EurekaLog IDE expert by installing (registering) EurekaLogExpert.bpl package.
4. (Optional) Register EurekaLog Events component by installing (registering) EurekaLogComponent.bpl package.


Please, see manual installation guide for more detailed information.



See also:

Send feedback... Build date: 2023-09-11
Last edited: 2023-07-18
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: