Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!lll-winken!uunet!mcrware!kim
From: kim@mcrware.UUCP (Kim Kempf)
Newsgroups: comp.os.os9
Subject: Re: Undocumented SetStat codes
Message-ID: <1149@mcrware.UUCP>
Date: 4 May 89 14:20:48 GMT
References: <257@fbihh.UUCP>
Reply-To: kim@mcrware.UUCP (Kim Kempf)
Organization: Microware Systems Corp., Des Moines, Iowa
Lines: 34

In article <257@fbihh.UUCP> peters@fbihh.UUCP (Heino Peters) writes:
>Hi everybody,
>
>There seem to be lots of Setstat codes in OS9/68k whichs aren't
>documented in the technical manual.  I found names like SS_Break
>in /dd/defs/funcs.a but they aren't mentioned in any manual i own.

Many [gs]etstat codes (such as these) are codes that are not necessarily
useful from the user level.  Others are very specific to certain
drivers, filemanagers, functions or even systems.  One can define any
codes they wish the driver to interpret.  The best documentation for
such codes is always the drivers and utilities that use them. 

>I'd like to implement at least SS_Break, SS_RdBlk, SS_WrBlk in my
>drivers. Could somebody please tell me were i can get the Documentation?
>
SS_Break is intended to cause (SCF) the "break" function (asserted tx line)
on a tty port or (PIPE) the breaking of a pipe.  No arguments or return
values.  The implementation of the SS_Break function appears in the Portpak
drivers.

SS_RdBlk/SS_WrBlk - unknown.  Likely experimental or application-
specific functions for disk block read/write.  Roll your own...

>I'd also like to know if any software by Microware is using these codes.
>
Microware uses all the codes :-)

----------------
Kim Kempf, Microware Systems Corporation	{sun,uunet}!mcrware!kim
					opinions(mine) != opinions(microware)
-- 
----------------
Kim Kempf, Microware Systems Corporation	{sun,uunet}!mcrware!kim