Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!lll-tis!ptsfa!ihnp4!alberta!sask!reid
From: reid@sask.UUCP (I am NOT your Sweet Baboo)
Newsgroups: comp.sys.dec
Subject: Re: Is anyone out there running Venix 1.0 on a Pro 350?
Message-ID: <731@sask.UUCP>
Date: Thu, 21-May-87 18:19:30 EDT
Article-I.D.: sask.731
Posted: Thu May 21 18:19:30 1987
Date-Received: Sat, 23-May-87 16:23:14 EDT
References: <725@sask.UUCP>
Reply-To: reid@sask.UUCP (Irving Reid)
Distribution: world
Organization: The Church of the Least Fixed Point
Lines: 19
Summary: Oops - the problem is in C-Kermit & code mapping, not the serial line driver.

In article <725@sask.UUCP> reid@sask.UUCP (that's me) writes:
>
>Unfortunately, the serial line driver in Venix 1.0 has a bug in it which
>makes the Pro crash stone cold dead when I try to receive at > 300 baud...

Well, I've checked around a little more, and now I'm trying to get some of
this egg off my face.

The Pro only crashes at >300 Baud when I'm running Kermit (even just as a
terminal emulator).  Cu, which I'm using now, runs just fine at 1200 baud.

As far as I can guess, it must be some interaction between Venix's
code-mapping (a tricky sort of pseudo-overlay system) and interrupts,
causing the CPU to become lost somewhere on the outskirts of /dev/null.

-- 
 - !Baboo -   (reid@sask.uucp or {alberta, ihnp4, utcsri}!sask!reid)

When I was a child I was an imaginary playmate.