Now I get this exception:
function TIcsWndHandler.AllocateMsgHandler(Obj: TIcsWndControl): UINT;
var
I : UINT;
begin
if FMsgLow < WM_USER then
raise EIcsException.Create('MsgLow not defined');
if FMsgCnt >= WH_MAX_MSG then
raise EIcsException.Create('No more free messag
I don't see why your first version could not work. I have programs which
basically does the same thing (calling several Send in a row). And I can't
imagine why an AMD processor whould fail doing that !
btw: Your second versin is much faster (well 50 iterations probably doesn't
do any difference
Hello Marcelo,
Your problem has nothing to do with AMD processors. It was by coincidence
that the machine that produced the problem had an AMD processor. You should try
an Intel one also. As far as I know, socket implementations doesn't depend on
or differ by processor type. They should not.
> AFAIK winsock API function WSAAsyncSelect() is a common, blocking
> function. In this case it's called to disable winsock notifications.
> Because the window is detached/destroyed in subsequent lines.
> BTW: Same is done in V5.
> So for a short while the detached socket is windowless, that's
> wh
Something wrong in TIcsWndHandlerPool.GetWndHandler ?
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Saturday, June 10, 2006 9:20 AM
Subject: Re: [twsocket] ICSv6 Thread Attach/Detach pro
I built a small test to verify TIcsWndHandlerPool.GetWndHandler and it works
perfectly. So the problem is elsewhere.
Are you deriving a component from an ICS component ?
If you do, be sure to respect the rules with AllocateMsgHandlers,
FreeMsgHandlers and MsgHandlersCount. If you don't, you may
All is well now. Sorry for the trouble. I was calling GetHandle which was
calling allocatehwnd internally after the threaddetach... That was the
problem.
THANKS!
SZ
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Saturday, June 10, 200
Hi,
I've finally been able to restart a project from last October. Something
has gone missing and code that used to work doesn't anymore. So I have to
sort of start over. I've followed the example code, looked at my postings
from back then in the archives but I'm having problems with the follow
> I think I'm missing something critical but can't quite figure it out.
Your are missing the fact that you use UDP and not TCP. UDP is
connectionless and sessionless. So don't use TWSocketServer. Use TWSocket,
make it listen and the just handle OnDataAvailable event to call Receive to
get the i
Ah. I see. Thank you. Before I posted my question I read as much
information on all this as I could including my old postings from last year
and the wsocket.hlp file. As I understand it then, the Wsocket.hlp file is
wrong or even worse, vague giving the impression that something is possible
wh
10 matches
Mail list logo