Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Keywords: sRecvBinary CTRL-C
It's a bit more of a mess, but I think you are qualified to attack it. Mostly get the example figured out, then you ought to be home free.
I allocated memory for the binary buffer, I used IntControl(42,binbuf,0,0,0) to get a binary address pointer for the buffer, and then I wait for input with stuff=sRecvBinary(socket, binaddr, 1).
I assume this sRecvBinary will "wait" until 1 character enters into the Buffer at which point the function will close and proceed onto the next line.
My script is just sitting at this point and not passing on or even timing out. I have to do a Ctrl-Break to stop the program. I even tried setting the EOD with the BinaryEodSet function to 1 with no avail.
I know that the unix host is sending me data - I can see that with my LAN sniffer and with the unix logs. I know I can send to the unix box with the sSendString (socket, string) function because when I use this function I see it reach the unix box.
I know I cannot use the sRecvLine (socket, maxsize) function because that function is waiting to see a CRLF at the end of the message and my unix box does not send one, it sends a ctrl-c instead.
Hmmmmm.... Is there someway to implement a time-out part to the sRecvBinary (socket, blob, size) that after a certain amount of time it will timeout and just keep the data it was sent and close the socket? Or even if there is a way to implement a way to change what sRecvLine is waiting for to see as the end of the message. Hmmmmm.... Any ideas?
Article ID: W12609
Filename: How to Receive a Line with a Ctrl-C in it.txt
File Created: 2017:07:28:12:58:52
Last Updated: 1999:04:15:15:48:24