🚀 go-pugleaf

mikel@networx.com (Mike Lempriere) writes:

>Tom Green (tomg@code3) wrote:
>: We are trying to get hardware flow control going on an AOS/VS II system and
>: are having some trouble.  We set the HIFC and HOFC characteristics on the
>: con we are using, but it doesn't seem to be using regular rtc/cts signalling.
>: We are trying to talk to a SCO unix box.  Anyone have any suggestions which
>: pins are really being used, or if we are off base totally in the first place?
>: 
>: Thanks.

>My experience is 6 years out of date, but as I recall the IACs really badly
>wanted ALL the hardware protocols implented.  If your cables are not using
>pins 1 through 8 and 20, you'll probably have trouble.

>Are you running custom programs setting the values at run-time?  If not,
>are you setting the DEFAULT characteristics from the console?  I don't
>remember the details, just that there is a difference between setting the
[...]

Well it need not be the console...
Having the System Manager priv, you can set default CHARs from any
Terminal. ( Dont forget do dis/enable the console you set the characteris-
tics of... )
Turning on the SysMgr attribute :
:CLI32    PRIV SYS ON
:CLI16    JPI something
          ( Ignore the error message. the "something" should be written
            as <something>, which is anything except a valid JP-id.
            Feel free to put four letter words there... )
  Jens

v
>char's for the current session, vs. as default...