Corinna Vinschen cygwin.com> writes:
> You should nevertheless use /dev/com4 or /dev/ttyS3. I might be wrong
> but it still looks like you don't quite see what Brian was up to.
>
> Corinna
>
Hmm...I think I see what you're getting at. I'm (obviously) not really all that
knowledgeable of seri
Brian Dessent dessent.net> writes:
> What I was trying to emphasize is that passing "COM4" to open() in a
> Cygwin program sets you up for a world of hurt...
>
> Brian
It's even worse than you think. In this case...COM4 is not even a real serial
port...but a "virtual" serial port constructed b
Todd Rearick cox.net> writes:
> Thanks for all of your help. Unfortunately...now the problem isn't really
> directly under my control...hope I can find a solution.
>
HAHA!!! I'm such an idiot. I have firewall software running on the 2 PC's
that don'
Corinna Vinschen cygwin.com> writes:
>
> This I can't tell you since I don't know the server side of the
> connection. It's normal to get EOF (== 0) over and over again if EOF
> has been detected. This behaviour can be observed on, for instance,
> Linux, too.
Well..I thought it shouldn't if i
Brian Dessent dessent.net> writes:
>
> > #define OUTPUT_DEVICE "COM4"
>
> *cough*
>
>
Like I said. I'm not having a problem with output. The program fails even
when I run it with the options "-x -d"in this case, COM4 is never even
opened..and no attempts are made to write to it.
Corinna Vinschen cygwin.com> writes:
>
> On Oct 22 07:06, Todd Rearick wrote:
> > while(1)
> > {
> > char buf[80];
> > int len;
> >
> > len = recv(infd,buf,1,0);
> >
> > if (len < 1)
>
Brian Dessent dessent.net> writes:
>
> Your test case does not compile...
...good point...I was just trying to cut down on the length of the post...but
it really didn't save that much anyway...I'll attach the full code on the end
of this post in case anyone wants to try it.
>
> Is there any
7 matches
Mail list logo
