Newsgroups: comp.sys.apollo
Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system
From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson))
Subject: Re: vt100 bugs for OS 10.2
Message-ID: <1991Jan24.162751.2379@alchemy.chem.utoronto.ca>
Organization: University of Toronto Chemistry Department
References: <1991Jan23.162913.132@Stardent.COM>
Date: Thu, 24 Jan 1991 16:27:51 GMT

In article <1991Jan23.162913.132@Stardent.COM> donaldg@Stardent.COM (Donald Gale) writes:
>We've got 2 vt100 bugs for OS 10.2. These occur on 3000's and 3500's.
>
>1. vt100 will come back with "cannot create vt100 window" as a message.
>This message is the same as if you tried to execute vt100 from a 
>window in which you have crp'd onto a node. When the node in question
>was rebooted, vt100 proceeded to work normally for a day - then the 
>same problem reappeared.
>
>2. vt100 will appear to work, but the cursor appears over the $ prompt.
>Nothing can be typed into the vt100 window - dm claims that it is read-only.
>
>Has anyone else had similar problems ? Does anyone have a work-around solution ?

1. We have had that problem ever since SR10.2/SR10.2.p and it is still
broken in SR10.3.p. In our case you get 1 shot at vi/more/whatever that
uses vt100/vtserver, then all future commands just hang.

2. Haven't seen this.

The workaround is to rebuild the pty's with mkdev, but this must be done
by root. The way we avoid this problem is to run X Windows, but that
leaves 2 DN580's sitting useless (since last April) since X is sooooooo
slow on those nodes (takes 5 minutes to login).

This should be added to the FAQ, since it looks like it isn't fixed at
SR10.3 either!
-- 
Mike Peterson, System Administrator, U/Toronto Department of Chemistry
E-mail: system@alchemy.chem.utoronto.ca
Tel: (416) 978-7094                  Fax: (416) 978-8775
