🚀 go-pugleaf

"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 

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
> 

"John M. Hobbie" <hobbiejm@earthlink.net> wrote in message 
news:47f7deb5@newsgroups.borland.com...

> 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.

They are one and the same version.  C++Buillder can compile and use Delphi 
components.

> 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.

Did you have the C++ personality loaded in the IDE at the time you install 
the packages?  If not, you need to do so.


Gambit 

Thanks for the fast response, Remy.


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:47f87478@newsgroups.borland.com...
>
> "John M. Hobbie" <hobbiejm@earthlink.net> wrote in message 
> news:47f7deb5@newsgroups.borland.com...
>
>> 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.
>
> They are one and the same version.  C++Buillder can compile and use Delphi 
> components.
>
>> 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.
>
> Did you have the C++ personality loaded in the IDE at the time you install 
> the packages?  If not, you need to do so.

Yes.  I did the whole thing again, just a bit ago.  I uninstalled, using 
windows
uninstaller, then I went everywhere I knew indy related files were and 
deleted them.
I also went into the component->install packages and deleted the two indy 
package
references.  I used an Indy10.zip downloaded last night and unzipped it into 
a directory,
and then ran the Fulld10.bat file.   (If you are talking to the Indy folks, 
this zip file
does not contain the file  dclIndyProtocols100.res   and I had to fake it by 
renaming
dclIndyProtocols90.res)

Anyway, all went well.  Started up the BDS2006 in C++ personallity only and 
installed
the two indy packages -- core and protocols--, and verified that they had 
the components
-- at least the icons.  I then loaded a BDS2006 project and the tool palette 
had no indy items on it.

To further test it, I loaded a BCB5 project that Indy5 components and there 
was no Indy
on the tool palette and there were no Indy icons on the form.  (Also, while 
loading the
project, BDS2006 complained about two SMTP1 properties -- older versions? -- 
and asked if I wanted to ignore them.  So, it at least seems to be 
processing Indy code during
initializing the project.)

When I get into a full personallity mode, and load an Indy demo (Delphi) 
everything works like it is
supposed to.

Sorry this is so long winded, but I hope it can give you a clue as to where 
I went astray.

Hobbie 

On or about Sat, 5 Apr 2008 23:53:04 -0700 did "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> dribble thusly:

>
>"John M. Hobbie" <hobbiejm@earthlink.net> wrote in message 
>news:47f7deb5@newsgroups.borland.com...
>
>> 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.
>
>Did you have the C++ personality loaded in the IDE at the time you install 
>the packages?  If not, you need to do so.

I don't think he did anything wrong.  I have BCB2007 (i.e. only C++), and the
tool palette is not created when the design libraries are installed.  

Everything compiles fine on the command line (using a modified Fullc6.bat),
but the design package installation is not creating the tool palette icons.

It does for BCB6, but not BCB2007.

"John M. Hobbie" <hobbiejm@earthlink.net> wrote in message 
news:47f91e7b@newsgroups.borland.com...

> Anyway, all went well.  Started up the BDS2006 in C++
> personallity only and installed the two indy packages

Did the confirmation popup that appeared actually list the individual 
components by name?  If not, then they were not registered properly.

> To further test it, I loaded a BCB5 project that Indy5
> components and there was no Indy on the tool palette
> and there were no Indy icons on the form.

Did the BCB5 project use Indy 9 or 10?  The fact that no icons appear on the 
Form itself also suggests the components did not get registered correctly.

> Also, while loading the project, BDS2006 complained about
> two SMTP1 properties -- older versions? -- and asked if I
> wanted to ignore them.  So, it at least seems to be processing
> Indy code during initializing the project.

It is loading an old DFM and comparing it to later RTTI.  Some properties 
were moved/renamed between Indy 9 and 10.


Gambit 

Sorry I've taken so long to get back. I am on the road at this time.


>
> Did the confirmation popup that appeared actually list the individual 
> components by name?  If not, then they were not registered properly.

  Yes

>
> Did the BCB5 project use Indy 9 or 10?  The fact that no icons appear on 
> the Form itself also suggests the components did not get registered 
> correctly.
>
   It used Indy5.

>
> Gambit

I decided to take another tack, figuring I had made hash of everything. I 
completely removed BDS2006 as well as removing all Indy references I could 
find. I then reinstalled BDS with all personalities and looked for indy 
related files. I had to use the Indy90 installation as per the BDS 
installation instructions for use with C++. I then looked for, and examined 
all the indy files I could find. I used "FileAlyzer" and looked for version 
references. Though some of the files were labeled dclIndyCore100.bpl, for 
example, they were really version 9 as was expected. There were some indy 
.dll files, but they seemed to be for .NET personalities. There were no 
files that the versions claimed to be for C++; only .NET or Delphi.
In the files created by unzipping the latest Indy snapshot and compiling, 
only one .dll file was generated, Mono.Security.dll.

I did notice - since I also still have installed BCB ver. 5 which uses 
Indy50 - that there were two files that were labeled Indy90.bpl and 
dclIndy90.bpl (with similar versions for indy50). In the latest snap shot, 
there are no Indy100.bpl only IndyCore100.bpl, etc. That is the word Indy100 
alone, as opposed to IndySomething100.bpl.

In the run-time part of the Component->Install Packages window, there is a 
reference only to "Indy".

Should there be an Indy100.bpl and a dclIndy100.bpl generated in the batch 
files of the latest snapshot, and is that the problem?

Should there be more .dll files generated by the snapshot, and is the lack 
of those files the problem?

"John M. Hobbie" <hobbiejm@earthlink.net> wrote in message 
news:48010624@newsgroups.borland.com...

>  Yes

Well, then the components are installed properly.  The Tool Palette simply 
does not want to display them correctly.  We don't kow why it does that.

>   It used Indy5.

There never has been an Indy 5.  Prior to Indy 8, Indy was known as WinShoes 
instead.  So I assume that you actually mean the "BCB/Delphi v5 flavor of 
Indy 9" instead.

> I did notice - since I also still have installed BCB ver. 5 which
> uses Indy50 - that there were two files that were labeled Indy90.bpl
> and dclIndy90.bpl (with similar versions for indy50). In the latest
> snap shot, there are no Indy100.bpl only IndyCore100.bpl, etc.

That is normal.  Indy 9 is only 1 runtime package + 1 designtime package, 
whereas Indy 10 is 3 runtime packages + 2 designtime packages.

That is the word Indy100
> alone, as opposed to IndySomething100.bpl.

"IndyXXX" is Indy 9.  "Indy...XXX" is Indy 10.


Gambit