Support

Installing InterBase 2017 and XE7 64 bit on Windows 10 Creators U...

Written by Steve A416 on . Posted in Installation / Registration

Customers have reported that it is not possible to install the 64 bit version of InterBase on the Windows 10 Creators Update (build 1703). When you get to the screen that allows you to choose between 32 bit and 64 bit, it is greyed out

 

A workaround is to perform a silent install, which is described in the documentation at http://docwiki.embarcadero.com/InterBase/2017/en/Installation,_Registration,_and_Licensing_Information#Using_the_Wise_Installer_to_Embed_InterBase. A values file for a default installation of InterBase would contain:

COMPONENTS=ACD

MAINDIR=C:\Program Files\Embarcadero\InterBase\

INSTANCE=gds_db

TCP_PORT=3050

ARCH=64

If you have an existing successful installation of InterBase, you will find a values.txt in the program directory.

You would then launch the installer via the following command line:

 

When the installation has completed, you should find that a 64 bit instance has been installed.


Manual uninstall of RAD Studio/Delphi/C++Builder 10.2

Written by Christopher M424 on . Posted in Installation / Registration

 

Launch the License Manager from the bin folder (by default "C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\LicenseManager.exe") and delete any trial or beta (Test Field) license that you can find. Check it under “License Details” in the center column.

Under your Control Panel's Program and Features Add/Remove Program uninstall the following entries:

  • RAD Studio 10.2 version 19.0

Please follow these instructions to remove any leftover files:

  1. If Windows 32-bit, remove the C:\Program Files\Embarcadero\Studio\19.0 directory (or the custom folder you had used).
  2. If Windows 64-bit, remove the C:\Program Files (x86)\Embarcadero\Studio\19.0 directory (or the custom folder you had used).
  3. Remove the C:\Users\Public\Documents\Embarcadero\Studio\19.0 directory
  4. Remove the C:\ProgramData\Embarcadero\Studio\19.0 directory.
  5. Remove the %APPDATA%\Embarcadero\BDS\19.0 directory.
  6. Remove the HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\19.0 registry key
  7. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\19.0 registry key
  8. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Embarcadero\BDS\19.0
  9. If Windows 32-bit, remove the following files from C:\Windows\System32\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL
  10. If Windows 64-bit, remove the following files from C:\Windows\SysWOW64\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL

Field testers should also do the following (and others may want to as well):

  1. Delete the Godzilla license from License manager before uninstalling it or during the installation of RAD Studio 10.2

If you had problems in the second step (uninstalling from Windows Control Panel), try this Microsoft tool to solve uninstallation problems:

http://go.microsoft.com/?linkid=9779673

 


Issues with winapifamily.h and other header files after installin...

Written by David Millington on . Posted in RAD Studio

There is a known issue where occasionally, after the C++Builder and RAD Studio 10.1 Berlin Update 2 installer has run, eight header files may be missing from C++Builder’s include\windows\sdk folder.

The bug manifests as trying to build a Windows C++ application, and getting a compiler error at the top of windows.h stating that winapifamily.h was not found.


Upgrading from Delphi or C++Builder Berlin Starter edition to hig...

Written by Sarina D on . Posted in Installation / Registration

This post was updated on November 16th, 2016.

The Feature Installer (also known as the GetIt Installer) for Berlin Update 2 Anniversary Edition includes license detection support for detecting existing Berlin licenses. If an existing license of the same version of the product is found on your system, you will see a version of this screen during the install process. You can proceed with the installation using an existing license or enter a new license. Please note that this screen is only shown when an existing Berlin license is found on your system.

The Update 2 installer should automatically trigger the uninstall process prior to installing Update 2 system. The steps outlined below are only necessary should you run into issues during the uninstall/reinstall process.

Note: It is recommended that you use the same installer (offline installer or web installer) to re-install or install an update since the registry settings will not be compatible.

 


 

This post outlines the steps for upgrading from Starter to higher editions of the same version on the same machine. Please note that Delphi Starter and C++Builder Starter cannot be installed on the same machine. Installing higher editions of the same version alongside Starter on the same machine is not supported and will not work. Trials of the same version also cannot co-exist with Starter on the same machine.

 

Related links:

 

Upgrading from Starter to Pro/Enterprise/Architect

The following covers the steps required to install Delphi, C++Builder or RAD Studio Pro/Enterprise/Architect if you currently have Delphi or C++Builder Starter installed. The steps below assume that you are intending to install the higher edition on the same machine.

 

Step 1: Launch LicenseManager.exe

The License Manager can be found in C:\Program Files\Embarcadero\Studio\18.0\bin

 

Step 2: Add and register your higher edition license

Select Register to launch the registration wizard. Next, enter and register your new license. After successfully registering your higher edition license, it is recommended to remove the Starter license (although it’s not required).

 

Step 3: Uninstall Starter

Double-click on the Update 1 executable to launch the installer. This will uninstall the Starter edition. Alternatively, you can kick off the uninstall process by going to your Windows Control Panel and selecting Apps & Features.

 

Step 4: Install Update 1

After the uninstall is complete, the install will proceed. The Update 1 installer will now automatically pick the higher edition license you previously registered in Step 2.

 


 

Note: If you have already uninstalled Starter, and are looking to install a higher edition of the same version on the same machine, there are two options:

 

  1. Reinstall the Starter edition, then follow the steps outlined above

  2. Manually remove the Starter license key. To remove the individual license, you can delete/rename the C:\ProgramData\Embarcadero directory.  This is the local license storage and removing it will remove license information for *all* recent versions on your machine (please use with care). After removing the Starter key and uninstalling Starter, the Update installer will prompt you to enter your new license.

 


InterBase and Windows 10 Anniversary Update

Written by Steve A416 on . Posted in Support

We are getting reports from customers who are unable to connect to InterBase after applying the Windows 10 Anniversary Update. The error could be:

"Cannot attach to password database"

or

I/O error for file "C:\ProgramData\Application Data\Embarcadero\InterBase\gds_db\admin.ib"
Error while trying to open file
The system cannot find the file specified."

Since the release of InterBase XE3, the location of the password database, admin.ib has been determined by the IBCONFIG setting, APPDATA_DIRECTORY. The default value for this is

APPDATA_DIRECTORY         "C:\ProgramData\Application Data\Embarcadero\InterBase\<instance name>"

It turns out that Application Data is not a real directory but is what is known as a junction point that just points back to c:\programdata. When the Windows 10 update is run, this junction point is deleted. The way around the problem is to do the following:

  1. Run Notepad or your favourite text editor as Administrator.
  2. Open IBCONFIG. This is located in the InterBase installation directory
  3. Locate the APPDATA_DIRECTORY setting.
  4. Change this to APPDATA_DIRECTORY         "C:\ProgramData\Embarcadero\InterBase\<instance name>"
  5. Save the file and restart InterBase.

 


Get the new Powered By, Built With and Built For Logos

Written by Jim McKeeth on . Posted in RAD Studio

Embarcadero Cool App ContestThe Embarcadero Cool App contest is showing a lot of very cool apps that are built with Delphi, C++Builder, RAD Studio, InterBase and FireMonkey. So we've created some new graphics you can use to proudly show off your favorite development tool.

You can use the Built With or Powered By logos to highlight apps that use one of our products. Then the Built For ones are for those amazing tools, apps or libraries that are designed to work with our products. 

Let me know if there are other variations of these images that you need and enter your cool apps in the contest so you can win $2000 credit towards your next purchase. A new winner is announced every month!

DataSnap

  

RAD Server

  

VCL

  

C++Builder

  

Delphi

  

FireMonkey

  

InterBase

  

RAD Studio

  

 


“This version of the product does not support command line comp...

Written by Borja on . Posted in Installation / Registration

Some customers have reported that the Delphi compiler (dcc32.exe) that they have in their installation having a correct Professional, Enterprise or Architect edition of the product is not the correct one. This compiler is used if you perform builds outside of the IDE (for instance during the installation of several 3rd party components).

The first step of the installation of the IDE using the new feature installer installs a basic IDE with very limited functionality. This mini-IDE has the “trial” Delphi compiler that cannot be used to compile any program (trial licenses don’t include the final command line compilers). Afterwards, once you install the 32-bit Windows platform, the real “dcc32.exe” has to be copied to the “bin” folder of the product. Under some circumstances (an antivirus accessing the “trial” dcc32.exe file, for instance) the compiler is not correctly overwritten and you could still have the “trial” version on your “bin” folder.

If you have this problem please copy the correct dcc32 compiler from:

C:\Users\Public\Documents\Embarcadero\Studio\18.0\CatalogRepository\Core_Common_Files_Enterprise-18.0.Build.22858.6822\TARGETDIR\bin

Or

C:\Users\Public\Documents\Embarcadero\Studio\18.0\CatalogRepository\Core_Common_Files_Professional-18.0.Build.22858.6822\TARGETDIR\bin

To the “bin” folder of your installation (by default C:\Program Files (x86)\Embarcadero\Studio\18.0\bin) and the issue will disappear.


Manual uninstall of Rad Studio/Delphi/C++Builder 10.1 Berlin

Written by Borja on . Posted in Installation / Registration

Launch the License Manager from the bin folder (by default "C:\Program Files (x86)\Embarcadero\Studio\18.0\bin\LicenseManager.exe") and delete any trial or beta (Test Field) license that you can find. Check it under “License Details” in the center column.

 

Under your Control Panel's Program and Features Add/Remove Program uninstall the following entries:

 

  • RAD Studio 10.1 Berlin 18.0

 

Please follow these instructions to remove any leftover files:  

 

  1. If Windows 32-bit, remove the C:\Program Files\Embarcadero\Studio\18.0 directory (or the custom folder you had used).
  2. If Windows 64-bit, remove the C:\Program Files (x86)\Embarcadero\Studio\18.0 directory (or the custom folder you had used).
  3. Remove the C:\Users\Public\Documents\Embarcadero\Studio\18.0 directory
  4. Remove the C:\ProgramData\Embarcadero\Studio\18.0 directory.
  5. Remove the %APPDATA%\Embarcadero\BDS\18.0 directory.
  6. Remove the following hidden folders with a GUID name in C:\ProgramData\
    1. {FE8BEBBE-9A66-4252-9271-3B862ED0CA94}temp (Win 10 SDK files to copy to the product)
  7. Remove the HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\18.0 registry key
  8. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\18.0 registry key
  9. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F4A93EC9-7AD8-4874-853D-02C09A51B141}_is1 or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90E8837E-3E59-444F-B83F-39BAB9B5336D} registry keys if they exist.
  10. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10.1 Berlin registry key if it exists.
  11. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Embarcadero\BDS\18.0
  12. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F4A93EC9-7AD8-4874-853D-02C09A51B141}_is1 or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90E8837E-3E59-444F-B83F-39BAB9B5336D} registry keys if they exist.
  13. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10.1 Berlin registry key if it exists.
  14. If Windows 32-bit, remove the following files from C:\Windows\System32\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL
  15. If Windows 64-bit, remove the following files from C:\Windows\SysWOW64\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL

 

Field testers should also do the following (and others may want to as well):

 

  1. Delete the BigBen license from License manager before uninstalling it or during the installation of RAD Studio 10.1 Berlin

 

If you had problems in the second step (uninstalling from Windows Control Panel), try this Microsoft tool to solve uninstallation problems:

 

http://go.microsoft.com/?linkid=9779673


How to report a C++ Compiler or Linker problem and workarounds

Written by Juan Antonio Ruzafa on . Posted in RAD Studio

This is a guide with some hints on how to report Rad Studio C++ Compiler and Linker issues to Embarcadero's Quality Portal. If you follow these advices, R&D team will have more chances to reproduce and fix the issue you've found. Besides, you'll find some workarounds for common problems.

 

How to report a C++ Compiler problem

 

Enable "Diagnostic" Verbosity 

  • Go to Tools | Options | Environment OptionsCompiling
  • Change the "Verbosity" drop down to "Diagnostic":

 diagnostic

  • Do a build of the project
  • Save the messages from the "Output" tab of the Messages Pane to a text file:

output

  • Attach the text file to your bug report

 

Include Preprocessed files

When reporting a compiler crash, the report should contain a narrowed down testcase that illustrates the crash. If that is not possible, then include a Preprocessed copy of the source file that causes the crash. To create a 'Preprocessed' file, right click on the source file that crashes in the Project Manager and select "Preprocess". The IDE will create a .i file. Save that file and include it with the report.


preprocesed

 

 

You must add the compiler command line to your report, as shown in the Output tab of the Message View:


copy_output

Command Line: Build vs Output Tab

It is easier to copy the Command Line from the "Build" tab but it's preferable to copy the Command Line included with your report from from the"Output" tab because the "Build" tab wraps long command lines.

 

 

How to report a Linker problem

With the case of the linker crashes, R&D team usually needs the whole linkset to reproduce the issue. IMPORTANT: We do not need source: just objs and libraries, so if you can't provide us the source code is generally fine for linker issues.

Get Linker Team to Lookup XXX#### Code

If it's a "Fatal: Error detected (XXX####)", the linker team can look up the error (the 3 letter represent a linker source file and the numbers the line number) and maybe provide some guidelines about what might be happening. In some cases these point to the compiler having generated a bad object file.

 

 

Posible workarounds for Linker problems

Turn Off Incremental Linking

Turn off Incremental linking; Clean the Project and Rebuild. This can help with ilink32 but does not help with ilink64 as "-Gn" is hardcoded in the IDE for WIN64.

Bump Heap Sizes (For 'Out of memory')

For ilink64, if the error is "Fatal: Out of memory", the -GH switch can help. First you need to make ilink64 LARGE ADDRESS AWARE. To do that use the "editbin" utility provided with Visual Studio:

editbin.exe /LARGEADDRESSAWARE $BDS/bin/ilink64.exe

Then you use the -GH switch to increase the heap that was overflowed. For example, a typical failure might report:


Turbo Incremental Link64 6.72 Copyright (c) 1997-2015 Embarcadero Technologies,
Inc.
Overrun on linker heap: dwarf_info
...
dwarf_info 0x06039000 0x06000000
...
Fatal: Out of memory

 

The "dwarf_info" heap overflowed. To remedy we ask the linker to allocate a bigger size via: "-GHdwarf_info=0x0E000000".
You might find that after increasing one heap, another one overflows. So the final command line might read:

-GHinfo=0x24000000 -GHdwarf_info=0x0E000000 -GHbss=0x0E000000 -GHdwarf_str=0x0A000000 -GHdwarf_line=0x06000000 -GHcode=0x0E000000

Out of Memory and Unknown Heap error

Sometimes ilink32 raises an OOM and then "Unknown Heap" error (normally that unknown heap is "tds"). This workaround may help:

In the IDE:

  1. Go Project | Options | C++ Linker | Advanced | Additional options
  2. Add "-GHtds=0x0A000000" without the quotes.
  3. Try to link again.

 


Manual uninstall of Rad Studio/Delphi/C++Builder 10 Seattle

Written by Borja on . Posted in Installation / Registration

 Launch the License Manager from the bin folder (by default "C:\Program Files (x86)\Embarcadero\Studio\17.0\bin\LicenseManager.exe") and delete the licenses that activate your RAD Studio 10 Seattle product (XE8 or 10 Seattle licenses). Check it under “License Details” in the center column.

Under your Control Panel's Program and Features Add/Remove Program uninstall the following entries:

  • Embarcadero RAD Studio 10 Seattle

Please follow these instructions to remove any leftover files:  

  1. Remove the %USERPROFILE%\Documents\Rad_Studio_10_Seattle_Downloads folder
  2. If Windows 32-bit, remove the C:\Program Files\Embarcadero\Studio\17.0 directory.
  3. If Windows 64-bit, remove the C:\Program Files (x86)\Embarcadero\Studio\17.0 directory.
  4. Remove the C:\Users\Public\Documents\Embarcadero\Studio\17.0 directory
  5. Remove the C:\ProgramData\Embarcadero\Studio\17.0 directory.
  6. Remove the %APPDATA%\Embarcadero\BDS\17.0 directory.
  7. Remove the following hidden folders with a GUID name in C:\ProgramData\
    1. {09FECC13-2950-4AE6-BB23-05C206979F18} or {5D50B637-4756-435A-816E-68ABFE86FC69} (main installer)
  8. Remove the HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\17.0 registry key
  9. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\17.0 registry key
  10. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{25059B3C-FFC7-41B6-80A9-80E4A2ED5564} registry key.
  11. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10 Seattle registry key.
  12. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Embarcadero\BDS\17.0
  13. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{25059B3C-FFC7-41B6-80A9-80E4A2ED5564} registry key.
  14. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10 Seattle registry key.
  15. If Windows 32-bit, remove the following files from C:\Windows\System32\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL
  16. If Windows 64-bit, remove the following files from C:\Windows\SysWOW64\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL

Field testers should also do the following (and others may want to as well):

  1. Delete sample files from %PUBLIC%\Public Documents\Embarcadero\Studio\17.0
  2. Delete DBExpress connection files from %PUBLIC%\Public Documents\Embarcadero\Studio\dbExpress\17.0
  3. Delete the Aitana license from License manager before uninstalling it or during the installation of RAD Studio 10

If you had problems in the second step (uninstalling from Windows Control Panel), try this Microsoft tool to solve uninstallation problems:

http://go.microsoft.com/?linkid=9779673

 

 


Check out more tips and tricks in this development video: