🚀 go-pugleaf

Hmm, seems weird replying to my own message, but here goes!

Problem solved! Yes, I'm happy to say that nearly two weeks of frustration 
and headbanging finally led me to the solution. It seems that some sort of 
remnants of an old installation was the culprit, causing Indy to become most 
confused.

1. Remove Indy from the Packages list in Project Options.

2. Delete the many files related to Indy. You'll find these files installed 
'scattergun-style' all over your hard drive.

3. Reinstall a fresh version of Indy.

4. Add the path to Indy\C6 (or wherever yours is) to the Include and Library 
paths on the Directories list in Project Options, and make sure these 
entries are moved to the top of the list.

...and that's it. Easy.

Can I just say that installing components must be one of the most 
frustrating tasks in C++ Builder. It is for me, anyway.

I hope this information helps someone, somewhere!

Cheers,

- James


The very handsome "James" <jb9@btinternet.com> wrote in message 
news:415f4a4d$1@newsgroups.borland.com...
> Thanks for the reply!
>
> There are no exceptions raised at all. The Active property just remains 
> false! On searching Google, I noticed another C++ Builder user had 
> experienced this problem, but no-one had really offered an answer.
>
> I've tried loads of things, but I just can't get TCPServer->Active to 
> true. I wondered if there was some sort of initialisation taking place 
> when the TIdTCPServer was created by dropping it on the form, and 
> obviously I'm missing something when creating it dynamically.
>
> The TCPServer isn't even opening the socket. I know this because I'm 
> running ZoneAlarm, which always pops a box up when a TCPServer is started.
>
> Any advice?
>
> Thanks,
>
> - James
>
>
> "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
> news:415eea42$1@newsgroups.borland.com...
>>
>> "James" <jb9@btinternet.com> wrote in message
>> news:415eb5c8$1@newsgroups.borland.com...
>>
>>> I'm having real problems setting the TCP Server to Active.
>>> After running the code below, the TIdTCPServer's Active
>>> property is still false.
>>
>> Are you getting any exceptions at all?  If there is a failire in opening 
>> the
>> socket, you should be getting some kind of error.
>>
>>
>> Gambit
>>
>>
>
>