Arno Garrels wrote:
> Claude and Kia Hunter wrote:
>> Mr. Garrels:
>>
>> Thanks for the information. I turned off Korean program support and
>> the packages complied with no problems. This is the first time I
>> have seen this issue. Do you think that it will be safe to turn
>> Korean support b
if (_LowerCase(FProtoStr) <> 'tcp') and (_Trim(FProtoStr) <> '6') then
begin
RaiseException('TCP is the only protocol supported thru socks
server'); { V5.26 }
Exit;
end;
a) looks quite weird, as it likely to throw exception in every case
(FProtoStr can't be equal to 'tcp'
But you could build your own packages without the terminal components.
It is probably a good idea to save the modified packages (design time and
run time packages) under new names to avoid clash when ICS is updated.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middlewa
Claude and Kia Hunter wrote:
> Mr. Garrels:
>
> Thanks for the information. I turned off Korean program support and
> the packages complied with no problems. This is the first time I
> have seen this issue. Do you think that it will be safe to turn
> Korean support back on and use the compiled
>When Unicode Delphi came out the goal was to port ICS with minimum
>changes, I guess the same was true when Delphi .Net came out.
No argues, but sometimes the things done in hurry should be polished, shouldn't
they?
About .Net: I see that it's in eraly development stage, so let it go as you
wis
Mr. Garrels:
Thanks for the information. I turned off Korean program support and the
packages complied with no problems. This is the first time I have seen this
issue. Do you think that it will be safe to turn Korean support back on and
use the compiled packages now?
Claude and Kia Hunter
011-
Sir:
Thanks for the response. My Windows is not a Korean localized version. I
use English Windows Vista with Korean keyboard support installed using the
Regional and Language Options in the Control Panel. I do have the system
set to use Korean for non-UNICODE programs since many Korean programs
