Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!mnetor!seismo!lll-crg!topaz!ll-xn!mit-amt!mit-eddie!genrad!decvax!decwrl!ridder@warlok.dec.com
From: ridder@warlok.dec.com
Newsgroups: net.micro.amiga
Subject: Re: More errors from console.device
Message-ID: <4091@decwrl.DEC.COM>
Date: Thu, 10-Jul-86 14:14:56 EDT
Article-I.D.: decwrl.4091
Posted: Thu Jul 10 14:14:56 1986
Date-Received: Fri, 11-Jul-86 23:12:36 EDT
Sender: daemon@decwrl.DEC.COM
Organization: Digital Equipment Corporation
Lines: 48


   ========
           
Date: 10 Jul 1986 1149-MDT
From: Hans <RIDDER@WARLOK>
To: "net.micro.amiga"@DECWRL
Reply-to: Ridder@WARLOK
Subject: Re: More errors from console.device
Message-ID: <"MS11(5235)+GLXLIB5(0)" 12221610030.25.143.2634 at WARLOK>
 
 
(The gateway I use died right after I sent my message, so I missed
any replies.  I did however read one reply from Mic Kaczmariczik(?),
from an archive on trantor (wonder what happened to the others?).  I
would appreciate it if someone would forward the replies to me
(please send a short message first, incase someone else already sent
them to me!).)
 
 
Tom -
    In reference to your first question, I really don't think
devices should return ANYTHING but errors in io_Error.  However,
if CA wants to DOCUMENT that when a certain bit is set in io_Flags
after a write means that the error isn't, then I wouldn't mind.  I 
would rather they implement a device specific command for it
instead (like the serial.device).  Really, what do the number of
input characters available have to do with a WRITE request?
 
    As to your second question, Mic seems to think we are talking
about the serial.device.  But the answer is still yes for the
console.device.  CMD_READ for the console device will return AS
MANY characters as are avalable in the buffer (up to your io_Length),
all you need to do is check io_Actual after the read to see how
many characters you got.  Essentially all CMD_READs of the
console.device are non blocking, unless there are NO type-ahead
characters available, then you WILL block.  (Assuming DoIO()s of
course).  If you are using SendIO() or BeginIO(), then you can just
check io_Actual after you get the reply.  Although fast typists
are not usually a problem for most terminal programs, posting
a READ for multiple characters might lower the message traffic
caused by 1 character reads of the console....  There is also
the case of IOF_QUICK, but you can figure that out on your own :-}.
 
    But I still want to know what the error is!  Please won't
someone tell me?
 
-hans
   --------