🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.masscomp
Article #72

Re: HPSM problems - The Project Leader Speaks

#72
From: masscomp-request
Date: Thu, 01 Oct 1987 20:35
48 lines
3063 bytes
In article <3226@soma.bcm.tmc.edu> carlton@apollo.UUCP (Carlton B. Hommel) writes:
>I believe that all of the posted problems with the High Performance
>Serial Boards (HPSMs) have been fixed in the RT-HPSM V4.0 release.
>I was just the project leader and release engineer, not the technical
>bug-killer, so please don't send me technical questions about DTR,
>DSR, RTS, or PDQ.  Lets face it, the original HPSM releases were dogs.

While the current release (4.0) is better, we still require frequent
reboots because of hung lines.  We're working with Masscomp on it
locally, but still no joy.  Since we talk to the Masscomp through an
Equinox data PBX, the RS-232 signals get more exercise than they do
at most installations.  Still, it's extremely annoying to have a
system that must be rebooted four or five times a week.  Do I sound
annoyed?  I'm annoyed.

>Under intense pressure from several OEMs who threatened to walk away and
>buy Suns or (dare I say it?) Apollos, an emergency one-month project was
>put together to make the HPSM work.  *ALL* of the outstanding SQR's were
>closed.  Most were found to be due to errors in driver code, and fixed.
>The others were not reproducible with the new RTU software.  (At one point,
>we had a 5700 with 8 hpsm boards feeding 64 tty lines, feeding into four
>5400s with 2 hpsms each, running all week.  Its amazing how much respect
>your testing group gets when OEMs wave dollar signs about.)

If the lines were modems that drop carrier rather than just wired TTY
lines, I seriously doubt that you would have passed the test.

>Everyone was happy.  

We aren't.

>Now, if you *have* installed RT-HPSM V4.0, and have these wierd hangs,
>undropped lines, etc. let MASSCOMP know.  Insist that the person you talk
>to on the phone actually lets a manager in Engineering know, so they can
>consider getting the fix into their next release.

Can you tell me who to talk to?  No one in San Jose has had any luck
or seems to know how to attack the problem.

>If you haven't installed V4.0, get it!  Its only one floppy, and 5-15
>minutes downtime.  (5300's take 15 minutes, 5700s take 5 or less.)

It's certainly better than what you had before.

-- 
- Joe Buck  {uunet,ucbvax,sun,decwrl,<smart-site>}!epimass.epi.com!jbuck
	    Old internet mailers: jbuck%epimass.epi.com@uunet.uu.net
Technical Details
Message-ID: <3229@soma.bcm.tmc.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!ukma!uunet!soma!masscomp-request
References: <3226@soma.bcm.tmc.edu>

Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!ukma!uunet!soma!masscomp-request
From: masscomp-request@soma.UUCP
Newsgroups: comp.sys.masscomp
Subject: Re: HPSM problems - The Project Leader Speaks
Message-ID: <3229@soma.bcm.tmc.edu>
Date: Thu, 1-Oct-87 16:35:03 EDT
Article-I.D.: soma.3229
Posted: Thu Oct  1 16:35:03 1987
Date-Received: Sat, 3-Oct-87 08:40:24 EDT
References: <3226@soma.bcm.tmc.edu>
Sender: masscomp@soma.bcm.tmc.edu
Reply-To: jbuck@epimass.EPI.COM (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 48
Approved: masscomp@soma.bcm.tmc.edu
Summary: Sorry, it's not right yet