LISTSERV - HP3000-L Archives

HP3000-L Archives

April 2002, Week 3

HP3000-L@RAVEN.UTC.EDU

	LISTSERV Archives
	HP3000-L Home
	HP3000-L April 2002, Week 3

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

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 >>]

Subject:	Re: Software ID and Model string
From:	"Wayne R. Boyer" <[log in to unmask]>
Reply To:	[log in to unmask][log in to unmask], 18 Apr 2002 09:20:09 -0400532_iso-8859-1 Hello Folks @ 3000-l, Re: Advanced Telnet Returns - SR 4701-422436 TELNET SUPPRESS LOCAL ECHO OPTION & XON/XOFF FLOW CONTROL This functionality is primarily used in the QCTERM product from AICS Research, Inc. For further details see: http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind9806D&L=hp3000-l&P=R54119 The patch which returns this functionality to Telnet is now available for 6.0 (and is expected to be available for 6.5 and 7.0 in the next few weeks): [...]45_18Apr200209:20:[log in to unmask]
Date:	Tue, 16 Apr 2002 13:48:07 EDT
Content-Type:	text/plain
Parts/Attachments:	text/plain (41 lines)

In a message dated 4/16/02 10:19:34 AM Pacific Daylight Time, [log in to unmask]
writes:

> Besides, the HP9000 has the same hardware. Releasing SSCONFIG might allow
> people to change the strings on HP9000's as well.
>
>

Paul: If I understand you correctly, you are supposing that SSCONFIG could be
used by non-HP-3000 users (ie: HP-9000) to change around HP-9000
configuration settings.  That could be a giant problem for HP.  So how is HP
going to solve this? Does HP care about their customers or not?  Any HP-3000
system that was a CPU failure after end of support for that model is faced
with one of these four choices:

a) Replacing the CPU board with a used board from another similar HP-3000 -
if so then the HPSUSAN should at least be changed in order to allow some
software to run.

b) Replacing the CPU board with a used board from a similar HP-9000 - if so
then many firmware settings must be established in order for the system to
even boot up.

c) Utilizing a used replacement CPU board and dealing with whatever it has
stored in it's firmware AS-IS. Ie: change your third-party software, etc. to
accomodate it.

d) Scrapping the unusable hardware.

If everyone who intends to keep their HP-3000 running for at least a little
while after the end of support would look at the above choices... which one
do you want to do if you have a CPU board failure????  Remember: choices "a"
and "b" require SSCONFIG whch is unavailable!

Wayne Boyer
Cal-Logic

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2

RAVEN.UTC.EDU