Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ukma!uunet!soma!masscomp-request
From: masscomp-request@soma.UUCP
Newsgroups: comp.sys.masscomp
Subject: Re: HPSM problems
Message-ID: <3214@soma.bcm.tmc.edu>
Date: Wed, 16-Sep-87 18:36:53 EDT
Article-I.D.: soma.3214
Posted: Wed Sep 16 18:36:53 1987
Date-Received: Sat, 19-Sep-87 09:07:47 EDT
References: <3202@soma.bcm.tmc.edu>
Sender: masscomp@soma.bcm.tmc.edu
Lines: 32
Approved: masscomp@soma.bcm.tmc.edu

In article <3202@soma.bcm.tmc.edu>, gonzalez@vax.bbn.com (Jim Gonzalez) writes:
> I have started working with an HPSM that we had installed several weeks ago.
> ............
and Stan suggests: 
> [Did you reload the HPSM software into the HPSM? What version of the HPSM
> software are you runnings? I think the latest is 3.0. -- sob]

I just (last week ?) got HPSM software release 4.0, but have not installed 
it yet.  I am hoping that it will fix some of the problems we have been having.

The RELEASE NOTES claim to fix:
	-A flow control problem ... (which) would hang a tty port.
	-confusion resulting from NULLs in the data stream.
	and a collection of other errors in the previous releases 

We have had a number of problems with HPSM lines. The basic symptom is that
when you kill one (however that happens) the only way to recover that line
is to reboot. It may be possible to reload the HPSM, but you would probably
have to do it in single user or at least assure that no one else is using it.

The most common type of HPSM failure occurs when we transfer very long files
through it. We run a large format digitizer with a Mac+, then move the resulting
files from the Mac to a Masscomp with Kermit. I don't think that Kermit is at
fault. It appears that the HPSM loses an interupt, and then can not recover.

I probably should have spent this time installing the new release.....

			Dale Chayes 
			Lamont-Doherty Geological Observatory
			Palisades, N.Y. 10964
			(914) 359-2900
			....!philabs!lamont!dale