Problem
I have a Netware 4.x fileserver that I want to access using the
SCO Gateway for Netware. The documentation states that in order
to provide full UNIX filename semantics to UNIX users accessing
mounted Netware volumes, I should add NFS namespace to the Netware
volume and load the NUC.NLM on the Netware server. When I dismount
the Netware volume and attempt to load the NFS.NAM at the Netware
server console, this message is displayed:Loading module NFS.NAM NetWare 386 NFS Name Space Support V1.2 Rev(B) (920515) Version 1.02 May 15, 1992 (C) Copyright 1992, Novell, Inc. All rights reserved. SERVER-4.00-1586: Loader cannot find public symbol SERVER-4.00-30: This module is using 4 outdated API calls You should upgrade to a newer module when it becomes available. SERVER-4.00-1135: Load file referenced undefined public variable. The module was NOT loaded.
Or, if the module loads successfully and I am able to add the namespace, the server abends during loading of the NUC.NLM.
Cause
In the first instance, the NFS.NAM cannot find modules it needs,
and therefore fails to load. In the second case, the NUC.NLM has
made illegal calls to the Netware operating system, causing the
server to hang. Solution
Do not load the NLMs shipped with SCO OpenServer Release 5 on a
Netware 4.x server. The Release Notes and online documentation
state:...an NLM is provided that adds UNIX filesystem semantics to
Netware 3.11, 3.12, 4.01, or 4.02 file servers. If you have
such a server you should install this NLM on your file server.This is incorrect. The NLM should ONLY be loaded on Netware 3.x
servers. If you have UnixWare from Novell, use the NFS.NAM and
NUC.NLM from that software package on your Netware 4.x server.SCO Engineering is aware of this limitation. These modules for
Netware 4.x are scheduled to be provided in a future release.