Re: PM2e ISDN bug in ComOS 3.3.2 (fwd)

MegaZone (megazone@livingston.com)
Wed, 4 Sep 1996 20:55:58 -0700 (PDT)

Once upon a time Jon Lewis shaped the electrons to say...
>Next question. If I upgrade using either
>./Linux/pm_install Version 3.3.1

Use this the correct way, via the 'pminstall' script, not a direct call.
Or use 'pmconsole.

>./Linux/pm_open OpenWindows Version 3.3.1

Don't use this, this is a routine called by other programs and should not
be run independantly.

>will I totally hose the configuration of the PM2e, or will everything stay
>as is? The upgrade notes say that configuration will no be affected...but

It should be ok. Note however that some units have been corrupted going
from 3.3.1 to 3.3.2 - I don't believe it is an issue going to 3.3.2c1. AND
an image saved from 3.3.1 is NOT valid for a unit running 3.3.2 and up -
so a pmreadconf from 3.3.1 is no good after the upgrade. If FLASH is
corrupted it must me relfashed and reconfigured by hand (or with a script
and pmcommand). This is due to a number of changes in the FLASH layout
made to accomodate the newer PM-2i and PM-2ei hardware which have a C0 port
and base ISDN ports.

>you can backup the config with pmreadconf, but how do you write the
>resulting data back to a portmaster?

pminstall - just like a new ComOS.

-MZ

--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 6920 Koll Center Parkway  #220, Pleasanton, CA 94566