RE: Console issues upgrading from V4R5 to V5R1 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Console issues upgrading from V4R5 to V5R1
From: vhamberg@xxxxxxxxx
Date: Thu, 26 Sep 2002 23:39:46 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Oops, never really looked - 9401-150, 2269 processor (no
interactive "feature"  ;-)   )

Still, can I set up a console with PCOMM this way?

Thanks

Vern
> Vern,
>
> 170 ??
> V3R7 ??
>
> The 170 was first announced in the V4R2 era, which should be the minimum
> OS allowed on that hardware.
>
> Regards,
> Andy Nolen-Parkhouse

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Console issues upgrading from V4R5 to V5R1 , Jim Essinger

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.