>Hi all, I got into this problem.
>I need to send three bytes to a sort of trafficlight (ie : chr(160) + chr(5) + chr(1) ). The problem is that the receiver does not react as i expect. Looks like it does not buffer info so that i loose many packets. I tested wih a java program and in this case it worked fine.
>My question is, is there any settings I can make ? Maybe wnsock is sending something i don't know ? As you can see i'm not expert at all in those things :)
>
>thank you

Probably won't help much in your case, as what code I've got using winsock uses TCP and calls the API functions directly (rather than using the OCX control). Ran into peculiar problem where data seemed to get 'stuck" somewhere in some situations -- and addition of debugging code to step through the process, or running through a debugger would solve the problem. Then it dawned on me -- this looked just like the problem I'd run into when communicating over the serial port (again using API calls rather than OCX) -- in particular when a USB-to-serial "dongle", USB modem, or a "WinModem" (i.e. one that doesn't actually have a UART). Found that I periodically need to do a DOEVENTS (typically where an "idle loop") to make sure that these devices are being serviced -- essentially by calling DOEVENTS you're freeing up the current "timeslice" and allowing other programs to run.