Both files were not found during the compile process on one dedicated system with Delphi 10.4 and Windows 11.
The complete project has been compiled w/o problems on others systems using Delphi 11 and Delphi 10.3 and Delphi 10.4.
Following the solution from here (https://www.youtube.com/watch?v=l3_UVhBbP1s), adding the lib path (e.g. C:\Program Files (x86)\Embarcadero\Studio\21.0\lib\win64\release) to the project will not work for us, as we use different Delphi compiler versions inside our team.
Any more general solution for this problem?
Remark : using different compiler's worked before. This error appeared just a few days ago, we don't know what is really changed
I'm trying to install a new version of Indy 10 in Delphi XE3.
I'm using the Fullc_XE3.bat to compile the component, it works and finish OK, however, when I try to install dclIndyCore170.bpl I get the next popup error:
Procedure entry point not found #Idstack#TIdStackLocalAddressList#GetAddress$qqri in the dynamic link library D:\Entorno XE3\COMPONENTES\Indy-master\C17\Win32\Release\dclIndyCore170.bpl
I don't know what I'm doing wrong, I cleaned Delphi's Indy installation, deleting all indy files: dcp, dcu, pas, bpl.
Could you help me please?
First off, if you are doing a DELPHI installation, you should NOT be using the Fullc_XE3.bat script at all. That script is meant only for a C++BUILDER installation instead (the c in the filename stands for C++). For Delphi, simply open Indy's 5 .dpk packages (or the Indy170.groupproj project group) directly in the IDE and use the Project Manager's Compile and Install options.
Second, Delphi XE3 was released in September 2012, but TIdStackLocalAddressList was introduced in April 2013 for Indy 10.6.0 in XE4. So, you have clearly NOT cleared out the old Indy version that shipped with XE3 before installing the new Indy version. Your IDE is encountering an old binary that was left behind.
We have a huge app that uses ChartFX 4.0 a lot and we're migrating from Delphi6 to XE4. The programmer mainly responsible so far has basically created a new package for the ChartFX components and has successfully installed it on his machine, and has tested a lot of the code that uses these components. Every thing looked great at this point. Then he tried rebuilding/installing/testing on a couple of other machines - XE4 throws a designtime license not found error when he opens a new project and tries to place a chart object on the form. All machines have a licensed copy of chartFX 4.0 installed.
Any ideas?
You need to locate and transfer the CFX*.lic file (it's the development license for the .OCX file). In Delphi 7, it's CFX32.lic, and it's located in the %WINDIR%\System32 folder.
When we select Help / CodeGear Help from the Delphi 2007 for Win32 (Enterprise) menu, we get the error 'Access violation at address 02E85FC7 in module 'htmlhelp2100.bpl'. Read of address FB300182.'.
Then when we exit Delphi we get the Windows dialog 'CodeGear RAD Studio for Windows has stopped working'.
Selecting a keyword in the editor and pressing F1 displays a busy cursor for a couple of seconds then nothing. No help, no error.
Is anyone out there able to use the Delphi 2007 help system when installed under Windows 7?
Editing, compiling, linking all seem to work just fine.
We have loaded the IDE both with normal privileges and 'Run as administrator'. Same result.
Even though there is a prerequisite check for the .NET framework 2.0 SDK during installation and the check passes, to get the Delphi 2007 for Win32 help system to work under Windows 7 Ultimate 32 bit you must download and install the .NET Framework 2.0 SDK (including the documentation).
If you download and install the .NET framework 2.0 SDK after you have already installed Delphi, then execute install_and_view.cmd from the Delphi Help/Doc directory, the help system will then work.
Is there any conflict?
All new versions of Delphi can always be installed safely /next/ to older version.
Each new version should be installed in its own directory.
If you are going to install multiple versions, always install the oldest version first, and then work your way to the newest.
We work very hard to make sure that all versions of Delphi coexist together. But again, never install one version directly on top of another.
I am running 2007 and 2009 on the same machine (this machine) just fine. The only problem you might have is if you are compiling components to the same directory - you will just need to rebuild all your DCU's and packages each time, or make version specific packages and directories.
Install them in their own directories, and make sure you keep package binaries separate, you should be fine. I've got 2009, 2007, 2006, 7 and 5 all on this machine with no issues.
I have at least 4 Delphi versions on one machine. They do not bite each other.
I always install older versions first because i had once problems if i did this the other way round.
Yes - as Rob said (Robsoft) I have both working here. Delphi has always been very good at co-existing with other versions.
Obviously you can only have one version as the default for opening Delphi files.
Should not conflict.
I did D2007 on the same machine as D2006 with absolutely no problems (I was shocked, actually).
I haven't tried D2009 yet, but it should be ok.
This guy had problems though. Hopefully his issues were due to the custom setup he describes in that article.
A colleague of mine (think he has an account on here as dcraggs now) has got them both running on the same machine just fine, I believe.
Certainly would be a huge own-goal from Embarcadero if installing D2009 broke an already-installed D2007, given the way that the components and DCUs are not compatible - I suspect a fair number of people will need to have both around for a while (some of us still need D5 and D7 too!)
CodeGear stated (don't have a link handy, sorry) that there should be no conflict. I haven't yet installed D2009 on my workhorse PC so I don't know if that is correct.
The settings in registry have different path and packages have different names so there really should be no problems.
I have Delphi 2007 and I have installed 2009 yesterday with no visible problems so far. Both seem to work fine.
Appears to be no problem. Installed D2009 with TurboDelphi and 2007 and 2, 5 and 7 all on the same Vista machine
Both 2007 and 2009 have Jedi JVC and JVCL installed on them. All appear to work fine. Hope that helps.
.. and if you compile existing packages make sure you give them a new name (e.g. suffix with D12) as each version's BPL directories are in the path.
Installed D2009 Enterprise on VMWare instance running Vista Business with an existing D2007 Enterprise installation. Perhaps I did something incorrectly, but I began to experience errors in the D2007 IDE, as well as a very strange error, unknown fieldtype, in exe files compiled with D2007. I uninstalled D2009, and the errors have gone away.
You should always install the older version first. I tried to install 2009 first and then 2007 but the setup of 2007 failed.
Uninstalling 2009, and starting with 2007 first fixed the install problems.
In theory, it's possible, but if you use many third-party (or your own) libraries, it can get hairy pretty fast. I tend toward developing on Virtual machines, for this and other reasons. But, YMMV.
Should be fine. I have Delphi 7, 2006, 2007, 2009 with 3rd party libs Dev Express and Rem Objects for all (except Dev Express for 2009 - is it out yet?) and all work flawlessly. As others pointed out the versions were installed oldest to newest.
The installations won't interfere with each other, although the Delphi 2009 and Delphi 2007 projects are not compatible, and can't be shared.
Moving along with the order of release is a must. Install older first. Uninstalling may get tricky though.
How to fix Delphi 2009 data explorer?