Steema Central

I'm trying to get Tee Pro7 CLX components installed onto BCB6. I have the Indy 9.00.14 package installed.

If I try to install the package DclTee7C6CLX.bpl I get an error:

"The procedure entry point @Idwinsock@initialization$qqrv could not be located in the dynamic link library indy60.bpl"

Clicking ok immediately results in another error:

"Can't load package C:\Program Files\Steema Software\TeeChart Pro V7 Full Source Code\Sources\Compiled\BuilderC6CLX\Bin\DclTee7C6CLX.bpl.
The Specified procedure could not be found"

I can install the Tee7/VCL packages with no problems, so what's up with the CLX packages? I'm not quite sure what the link is between Tee7 and Indy.

If I remove the Indy package, I can install Tee7/CLX. If I then try to install the Indy package, that then comes up with similar errors.

I need both Tee7/CLX and Indy for my project, so I'm a bit stuck at the moment - any help would be gratefully received.

Keith

Hi Keith

do you use the source-code version of TeeChart and the source-code version of indy. I also use indy 9.0.14 together with TeeChart 7C6Clx.

In my compiled obj-files of indy 9.0.14 I find only "Idwinsock2@initialization$qqrv" (note the 2 after Idwinsock). Maybee you compiled TeeChart with the old (with BCB6 shipped version) of indy - and then the Idwinsock (not 2) reference is linked into DclTee7C6CLX.bpl.

I do not know anymore how I installed indy - but I didn't find any *indy* file under the BCB6 programs-directory (typical C:\Program Files\Borland\CBuilder6). Try to remove all files of the pattern "*indy*" (or move them to a backup-directory - eventual by keeping the directories structor for later restore) and then recompile indy V 9.0.14 and TeeChart 7 in this order.

regards
Martin

Hi Martin

Yes, I use the source code versions of both Indy and TeeChart. I had already successfully installed Indy 9.0.14 before trying to install TeeChart, and had previously moved any old (V8 ) Indy files to a backup directory.

Maybe I missed one somewhere??

At the moment, I've bodged my way round the problem by unchecking the Indy packages under the 'packages' tab, putting the old V8 indy60.bpl file back into CBuilder6\bin and installing TeeChart (it likes the V8 indy60.bpl file - it has idwinsock without the 2). I instantiate my Indy objects at run-time, so don't need the drag & drop components.

As long as I point my project to the V9.0.14 C6 directory, Indy works fine even with the old V8 file present.

However, this is not a permanent solution - if someone else in the future wants to modify my project, they would find it very difficult to reproduce what I've done.

As you have successfully installed both packages without problems, it seems I must have got something wrong somewhere, so I'll do as you suggest and start again from the beginning.

I'll let you know how I get on...

Thanks
Keith

Ok, I finally got Tee7 to install with Indy 9.0.14!

I found a lot of id*.dcu files in the CBuilder6\lib\obj directory, so deleted them and replaced them with those in the Indy C6 directory. I also found an Indy.bpi file in there as well.

Having deleted the Indy.bpi file, Tee7 wouldn't compile as it was looking for this file and couldn't find it - fair enough. However, the Indy C6 directory didn't contain a file of this name, but it did have one called Indy60.bpi, so I copied this file to the ..\obj directory and renamed it to Indy.bpi.

Incidentally, this was the file that contained references to idwinsock (without the 2) so good call Martin, this is where the wrong idwinsock was being linked in.

Tee7 then compiled without errors. I could then install Tee7/CLX with Indy already installed.

So, partly my fault, partly Steema's I think.

One thing I don't quite understand though - why does Tee7/VCL not require Indy to be installed, but Tee7/CLX does? Perhaps someone from Steema could enlighten me?

Thanks Martin
Keith

Hi Keith,

One thing I don't quite understand though - why does Tee7/VCL not require Indy to be installed, but Tee7/CLX does? Perhaps someone from Steema could enlighten me?

Hope you are not sad when I answer

Indy is used in TeeUrl.pas (search for "IdHttp")

Windows comes with the "Microsoft Windows Internet Extensions" in the unit wininet. This unit contains internet relevant functions such as InternetOpenUrl() and is used in the VCL parts of TeeUrl.

Since the CLX version should be prepared for Linux and Linux not comes with this unit they need the indy package.

The question is, why they do not use consequently the indy package in both (VCL and CLX) versions. Maybee the indy version coming with Borland is not useful for their usage...

regards
Martin

Hi Martin

Never sad when you answer

Thanks for the explanation, all is now clear.

Maybe if they used Indy for VCL as well, they'd be inundated with queries like mine, only they wouldn't be able to ignore them... or am I just being cynical.

Regards
Keith