HP3000-L Archives

March 1996, Week 3

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:
Eero Laurila <[log in to unmask]>
Reply To:
Eero Laurila <[log in to unmask]>
Date:
Thu, 14 Mar 1996 01:00:46 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Gilles Schipper ([log in to unmask]) wrote:
 
: Also, since you will be losing your DTC and network configurations, be
: prepared to go back and restore NMCONFIG.PUB.SYS and NSCONF.NET.SYS and run
                                                       ^^^^^^^^^^^^^^
                                                       This was MPE/V stuff
 
: NMMGRVER against them. I am presuming that NMMGRVER version 5.0 will be able
: to handle conversion of these version 2.2 files. If this presumption is
: incorrect, be prepared to reconfigure your DTC's and network from scratch.
: Hopefully, you have hard copies of these configurations.
 
- On MPE/iX the file NSCONF.NET.SYS is not needed.  NS on MPE/iX never used
  that file.  I wonder if you're talking about the network directory files
  NSDIR & NSDIRK in NET.SYS ?  Even if so, those arent of type NCONF and
  NMMGRVER will not be able to convert those (as far as I know).
 
  Another note:  I'm not sure if NMMGRVER would be able to convert 2.2
  NMCONFIG file to 5.0 format... there might be a limit in NMMGRVER on how
  old file it knows of to convert... I'm not sure since I don't support that
  code, however, it might be worth keeping in mind.
 
  In any case, I would also get a printout of all the data in the NMCONFIG
  before updating to be safe...
 
 
  Cheers,
  Eero Laurila - HP CSY Networking lab, NS services.

ATOM RSS1 RSS2