🚀 go-pugleaf

Thank you.  I did do the change and I am getting different problems now 
which I am trying to fix but if SendText doesn't send the entire amount and 
I fill the socket buffer wouldn't it call the ServerSocket OnError event? 
My network is a 10/100 hub which is sitting right on top of the computer and 
another computer sitting next to it (they are the only two items on the hub) 
so I don't think speed is an issue.  Did XP shrink it default packet size 
versus what they had on NT?  Thanks again.

Eric


"Bob Gonder" <notbg@notmindspring.invalid> wrote in message 
news:4mkf429644ao82ak653gcltqtf4v2g698j@4ax.com...
> Eric Patterson wrote:
>
>>That is all fine but why?  I would love to fix my issue but I am not a
>>person to shoot shotguns in the dark and hope to hit the target.  If what
>>you have gave me before will fix it then someone here should be able to 
>>tell
>>me why that will fix it.  What causes the invalid pointer exception?  Why
>>did this work in NT and now it doesn't in XP?  Please tell me the reason 
>>why
>>I have this problem instead of telling me your way will fix it.  Thanks.
>
> Remy explained the "why" in the same message where he explained the
> "correct" way to do it.
> In short:
> If SendText() fails to send the entire amount (due to a slow
> network perhaps, or a smaller packet size on the XP machine), then you
> are resending the entire string again, and again, and again...
>
>>> while(Server->ServerSocket1->Socket->Connections[ii]->SendText(AnsiString(AM
>>> sg+"\n"))==-1)
>
> In addition to that, you are creating and destroying a temporary
> AnsiString each time, which may or may not be a further problem (but,
> if you follow Remy's solution, this particular "problem" would also go
> away.)
>
>
>