Bruce Toback <[log in to unmask]> wrote:

> Several things: first, make sure you've run jconfjob.net.sys. Second, did
> you purge USL.SYS and UXL.SYS before starting the installation? If not,
> you may have installed old versions of NL or XL modules (even for
> products you don't have).

In addition to old products left around in UXL.SYS and USL.SYS, old
networking components can be left hanging around in NET.SYS. If you
previously had support for say X.25, or full blown NS/3000, and now you only
have the bundled in network capabilities (formerly Lanlink and Arpa
Services) then you can run into this situation. The supporting files for the
previously installed products will be left in NET.SYS.

When JCONFJOB runs it "compiles" DADCONF.NET.SYS based on the files that
exist in NET.SYS, whether or not those modules are current. The result is a
VERSION MISMATCH error when you use the NSCONTROL START command.

Use Bruce's idea of NMMAINT and look for version mismatches in the output.
Then you must identify the offending module's corresponding MAST file in
NET.SYS (i.e. VTMAST.NET.SYS) and rename it. Then restream JCONFJOB to
rebuild the DADCONF file excluding the bad modules.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

The opinions expressed do not  necessarily represent the views or
opinions of Beechglen Development. They might but not necessarily.
They represent solely the opinions of the author.