HP3000-L Archives

February 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Larry Boyd <[log in to unmask]>
Reply To:
Larry Boyd <[log in to unmask]>
Date:
Mon, 2 Feb 1998 15:35:57 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
Chad wrote after Jim wrote:
>Therm-O-Link wrote:
>>
>> Okay, here I am again with another HPRC horror story:
>>
><snip Jim's Horror story>
>
>The whole thing could have been averted if the NS/3000 and other things
>in NET.SYS were actually on the SLT. This is something I have been
>asking for forever. Isn't this all part of FOS now and if so, shouldn't
>it be part of the SLT with no 'extra' action taken by system managers to
>get it there.

Actually, no, not all of NS/300 is part of FOS.  However, we are looking
into several different options for solving problems such as these.  I can't
really address specifics at this time, but hopefully a solution will be
available soon.

As far as Jim's horror story goes, I think I can safely say, "No, the
run-around you got is not what we would consider or hope would be
'normal'." :)  Whether it is normal is somewhat irrelevant for Jim, since
he experienced it.  Unfortunately, one reason (but not the only one) we are
looking at options is because this happens too often for CSY's and HP's
liking.

LB

ATOM RSS1 RSS2