Hello all

I was again having a cow of a time trying to install the latest version of EDB to XE8 on a Windows 10 Pro machine. I had been running 2.23, and I wanted to go to the latest version. After installation, I got the message ‘Cannot load ‘edbrun226rsdelphiwin32xe8’. It contains unit ‘edbmigratemodule;, which is also contained in package ‘edbrun223rsdelphiwin32xe8’.

I un-installed 2.26, and went back to 2.23, and everything worked. I appear to be the only person having these issues, but I found an old thread of mine on this NG, and took note of the suggestions. I went through the registry and removed everything EDB that I could find. I removed all EDB paths from the Delphi Library. I reinstalled EDB on C;\Prog.., and the 23 bit app couldn't find the components - the paths were not in the Library. The installer had once again not put the paths in the library. I manually inserted ...
C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win32);
C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win64);
...and the 32 bit version was built, and the app ran.

The 64 bit version of the same app wouldn't compile, as it could not find edbcomps. I added
C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win64)\code
... to the Library path, and it compiled and ran.

All appears well at this end, but I have lots of apps to build\compile with the new components, so I am not entirely out of the woods.

I compressed this narrative a fair bit - I have done 6 installations today, and spent hours on something that should be easy. I have said that the problem appears to be at my end, but I am at a loss to understand why it should be so.

Any ideas?

Peter

Peter


I'm still on antiquated D2006 & W7 so can't even start to look at anything and, unfortunately, if you're the only sufferer it makes it hard for Tim to resolve.

My guesses, in no particular order:

1. some funky permissions thing with the registry - if it affects you it should affect others but with W10 who knows

2. illegal characters in the path string - probably my favourite

3. length of the path string - this would require Tim's installer to have the problem

4. the installer / W10 getting confused between real and redirected (I've forgotten the proper word) registry entries

5. little green men - gotta cover all bases

One serious suggestion is stop using the Windows recommended directories. I went rogue about 3 ice ages ago and it killed a lot of problems. Delphi itself lives in C:\BDS2006, all my 3rd party stuff in c:\3rdParty\whatever


Roy Lambert

Hi Peter

No problems here but I was just upgrading from Build 2 to Build 3.

I see that Version 2.24, which you have skipped over, had a breaking
change over the location of the runtime packages.  Perhaps that had
something to do with your troubles?

Malcolm

Peter,

<< I was again having a cow of a time trying to install the latest version of EDB to XE8 on a Windows 10 Pro machine. I had been running 2.23, and I wanted to go to the latest version. After installation, I got the message ‘Cannot load ‘edbrun226rsdelphiwin32xe8’. It contains unit ‘edbmigratemodule;, which is also contained in package ‘edbrun223rsdelphiwin32xe8’. >>

This indicates that 2.23 was *not* uninstalled properly prior to 2.26 getting installed. Given that all installations automatically uninstall any *other* versions installed, this indicates that the installer is having issues both uninstalling the prior version as well as installing the new version.  Given that all of your issues revolve around the registry settings, my guess is that there's something amiss with your registry permissions, etc. that are causing the registry portion of install/uninstall process to fail.

I can do a remote desktop with you to find out what the issue is, but you have to promise to come here and tell everyone that there's nothing wrong with our installers.  Just email me if you're interested.

<< C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win32);
C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win64);
...and the 32 bit version was built, and the app ran. >>

You don't want to put 64-bit directories in your 32-bit path settings, and those directories should have a \code portion on the end.

Tim Young
Elevate Software
www.elevatesoft.com

Malcolm,

<< I see that Version 2.24, which you have skipped over, had a breaking change over the location of the runtime packages.  Perhaps that had something to do with your troubles? >>

Good suggestion, but the uninstaller should have removed any older runtime packages from their *original* installation location, and the new installer would put them where they are *now* located.

It seems like there's something that is preventing the installer from doing even the most basic registry updates during the installation.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Malcolm,
>
> << I see that Version 2.24, which you have skipped over, had a
> breaking change over the location of the runtime packages.  Perhaps
> that had something to do with your troubles? >>
>
> Good suggestion, but the uninstaller should have removed any older
> runtime packages from their original installation location, and the
> new installer would put them where they are now located.
>
> It seems like there's something that is preventing the installer from
> doing even the most basic registry updates during the installation.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com

I am sure you will be right.  
My comment was just in case any registry settings were 'preserved' and
the jump over 24 and 25 skipped the intervening 'correction'.