Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!brutus.cs.uiuc.edu!apple!fox!portal!cup.portal.com!R_Tim_Coslet
From: R_Tim_Coslet@cup.portal.com
Newsgroups: comp.sys.atari.st
Subject: Re: UniTerm V2.0c and TOS 1.4
Message-ID: <25108@cup.portal.com>
Date: 16 Dec 89 20:17:40 GMT
References: <8912112347.AA10073@NARNIA.SAIC.COM> <25010@cup.portal.com>
  <8554@cs.yale.edu> <31623@iuvax.cs.indiana.edu>
Organization: The Portal System (TM)
Lines: 34

In article <8554@cs.yale.edu> fischer-michael@CS.YALE.EDU (Michael Fischer) wri
tes:
>In article <25010@cup.portal.com> R_Tim_Coslet@cup.portal.com writes:
>>Other than this (BOMBS on exit) UniTerm seems to work fine under TOS 1.4.
>>Has anyone else encountered problems like this with UniTerm (any version)
>>under TOS 1.4?
>
>I've noticed this problem with UniTerm V2.0e, and I don't think it is
>specific to TOS 1.4.  UniTerm works fine when started from the
>desktop, but when started from the Mark Williams shell, it will give
>bombs on exiting, and sometimes the computer will subsequently crash.

I was finally able to play with it and located the cause of the problem I
was having with UniTerm V2.0c.

It bombed both from NeoDesk and the standard DeskTop (2 bombs from the
DeskTop though instead of the 3 it gets under NeoDesk).

By enabling and disabling accessories I got UniTerm to run with no bombs
on exit. The accessory having problems with UniTerm was NeoQueue V2.03.

I understand Gribnif has a newer release of NeoDesk... I think I will report
this bug to them, and see if they can tell if the new release also has this
problem... maybe it is time to upgrade... again.   :-)

By the way, I think the real source of the problem is inside UniTerm (probably
in the OSS Libraries, as you said)... sometimes after UniTerm bombs AES acts
very strangely, and a reboot (either warm or cold) completely corrects this
strange behavior.

                                        R. Tim Coslet

Usenet: R_Tim_Coslet@cup.portal.com
BIX:    r.tim_coslet