V4R5 ---> V5R1 -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: V4R5 ---> V5R1
From: "Graves, Chuck" <cgraves@xxxxxxxxxxxxxx>
Date: Tue, 11 Dec 2001 15:40:15 -0800
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>
Thread-Index: AcGCnS9latbhfoKdRLyKIZ0JwgWTIQ==
Thread-Topic: V4R5 ---> V5R1

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I'm planning to upgrade two machines from V4R5 to V5R1 (a 620 and a 170)
on new years day...Are there any gotcha's that anyone has encountered?
I've never had any problems with upgrades in the past.  I've heard a
rumor that I needed to upgrade ALL of my PC's to the V5R1 Client Express
or else they wouldn't connect.  (currently running express client v4r5)

Follow-Ups:

Re: V4R5 ---> V5R1 , Alan Novick

This mailing list archive is Copyright 1997-2026 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.