> This is the same line I have. The problem is that same code is all
> over the place in the source. Is there another version of the source
> without those debug statements or with conditional compilation
> directives?

There isn't but you can easily replace OutputDebugString by 
//OutputDebugString to disable most of those lines. You'll have to add 
comment to the next lines for multilines outputdebugstring.

Or you can globaly disable range checking in your project settings which is 
even fatser !

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be


----- Original Message ----- 
From: "Johnnie Norsworthy" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Wednesday, August 02, 2006 6:32 PM
Subject: Re: [twsocket] UDP Socket Range Error


> On 8/2/06, Francois PIETTE <[EMAIL PROTECTED]> wrote:
>> > 008d7c34 +064 REMINDER.EXE OverbyteIcsWndControl  525  +1
>> > TIcsWndControl.Dispose
>>
>> Can you point the exact source code ? It is likely that your line numbers
>> doesn't match my line numbers. Show the offending line and a few before 
>> and
>> after so that we can locate exactly which istruction trigger the range
>> error.
>>
>> In my source code, line 525 is:
>>    OutputDebugString(PChar('Dispose ' + ClassName + ' ThreadID=' +
>> IntToStr(GetCurrentThreadId)));
>>
>> It is possible that GetCurrentThreadId return an unsigned integer which
>> could not fit into an integer required for IntToStr (an integer in the 
>> range
>> 2G to 4G). You may simply remove that line since it is for debugging
>> purpose, or fix it like this:
>
> Thanks for responding..
>
> This is the same line I have. The problem is that same code is all
> over the place in the source. Is there another version of the source
> without those debug statements or with conditional compilation
> directives?
>
> I need the code for the UDP packet sending as bullet-proof as
> possible. Would you recommend programming it in something less
> powerful than ICS - possibly the standard Delphi sockets? I can't use
> Indy as it also cause some obscure error and I don't care to
> inconvenience the Indy people anymore.  I am running the server here
> on on eo fmy machines with ICS code with no problems.
>
> The machine the error is happening on is a Windows 98SE machine and so
> far, it is just that one computer.
>
> -Johnnie
> -- 
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to