Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Serial Question
Message-ID: <7646@hoptoad.uucp>
Date: 15 Jun 89 05:40:48 GMT
References: <558@nikhefk.UUCP> <3441@ncar.ucar.edu> <559@nikhefk.UUCP>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 26

In article <558@nikhefk.UUCP> paulm@nikhefk.UUCP (Paul Molenaar) writes:
>Does anyone know a plausible reason for charachters $91 and $93 not being
>transmitted when doing a text-transmission over the serial port?

In article <3441@ncar.ucar.edu> cruff@handies.UCAR.EDU (Craig Ruff) writes:
>Probably because they are CONTROL-Q ($11) and CONTROL-S ($13) with the
>high bit set.

In article <559@nikhefk.UUCP> paulm@nikhefk.UUCP (Paul Molenaar) writes:
>Thanx! You're probably right on the dot! Now how 
>do I produce a work-around for this hick-up? Should I have the
>serial driver ignore software-flow control?

Depends on what side the problem is on.  If you're going to be sending
and receiving these characters, then you ought to call SerHShake with
the fXOn and fInX fields set to zero regardless.  However, the problem
may be on the host computer you are talking to over the serial port, in
which case you will also have to set some flags known to the OS on that
system.  On UNIX, you do this with a "stty(1)" command.  ("man stty"
for information on how to use.)  On VMS, you use a "SET TERM" command.
("HELP SET TERM" for information.)
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com
Postal: 424 Tehama, SF CA 94103; Phone: (415) 495-2934

"Jesus died for somebody's sins, but not mine." -- Patti Smith