🚀 go-pugleaf

Remy or whoever answers --

I have not been able to try your suggestions, Remy, because of problems 
installing Indy.  I could only find a snapshop
of a delphi/pascal version of Indy, not a Builder C++ version.  It took a 
while to find out how to compile in Delphi;
I use C++ normally and the Delphi personality didn't normally come up.

I installed the output of Indy delphi compiles in the Borland\bin directory 
using  Component->Install Packages.

Now, however, I can not find any Indy items on the tools palette.  When I 
start in the Delphi mode and open a Delphi project --
an Indy demo -- the Indy components show up in the tool palette.  If I open 
a C++ project, one that had Indy components, the Indy
components are not there on the tool palette, though the component icons 
still show up on the form.  (I didn't try to compile/build the
project with the indy icons in case the Indy parts wouldn't compile and mess 
up a working executable.)

Any ideas on how to get this to work, or what I might have done wrong?

Thanks again for your help.

John Hobbie






"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:47f1183a$1@newsgroups.borland.com...
>
> "John M. Hobbie" <hobbiejm@earthlink.net> wrote in message 
> news:47f06047$1@newsgroups.borland.com...
>
>> I'm using BDS 2006 and its version of Indy.
>
> Then you are using a very old version of Indy and should consider 
> upgrading.
>
>> There are some work arounds in Delphi, but I can't
>> seem to get them to work in Builder C++.
>
> Why not?  Indy is the same in both environments.  What works in one should 
> work fine in the other.
>
>> Has anybody else had this problem and have some fixes/work arounds?
>
> Try setting the UseTLS property to utUseExplicitTLS, the AuthType property 
> to atSASL (satSASL in the latest snapshot version), and then fill in the 
> SASLMechanism collection with one or more TIdSASL... components 
> (TIdSASLLogin, TIdSASLCRAMMD5, TIdSASLNTLM, etc) for each protocol you 
> want to support.
>
>
> Gambit
>