Path: utzoo!attcan!uunet!ncrlnk!ncrstp!npdiss1!mercer
From: mercer@npdiss1.StPaul.NCR.COMDan Mercer)
Newsgroups: comp.lang.c
Subject: Re: unix c help
Keywords: unix c communications kbhit
Message-ID: <133@npdiss1.StPaul.NCR.COM>
Date: 9 Jul 90 18:28:31 GMT
References: <1950@novavax.UUCP>
Reply-To: mercer@npdiss1.StPaul.NCR.COM (Dan Mercer)
Organization: StPaul
Lines: 38

In article <1950@novavax.UUCP> raab@novavax.UUCPMoshe Raab) writes:
:i have been coding in c for a number of years. all of this
:time i have been programming using MSC, using the MS extensions.
:recently,  i installed  Mark Williams Coherent (unix like)
:operating system. i started writing  my own simple communications
:program but have hit some unexpected snags. for example, how does
:one monitor the keyboard and the com port at the same time.
:in MSC i use, kbhit(). i could theoretically write my own
:kbhit in assemlby using the bios call to interrup 0x16 but
:that would make it unportable. if any one has any suggestions,
:please let me know.
: 
:also, could someone send or refer me to the source code
:for a communications program?
: 
:i would appreciate all help.
: 
:thanks
: 
:moshe raab
:(raab@novavax)

If this truly is UNIX,  then you don't monitor the keyboard and line
in the same process - you utilize two processes - one that monitors
the keyboard and sends data to the line,  the other monitors the line and
sends data to the screen.

Or,  you could just get PCOMM from comp.sources.unix - or kermit from
same.

One of the beauties of UNIX is not having to wrestle with low level
stuff like task dispatching.

-- 

Dan Mercer
Reply-To: mercer@npdiss1.StPaul.NCR.COM (Dan Mercer)
"MAN - the only one word oxymoron in the English Language"