Loader canot find public symbol
leoowls
message ' Loader cannot Find Public Symbol' for numerous variables.
Can any one assist
Regards
Leo
* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Barry Schnur
Are current patches in place?
Typically you get that message when server updates are not in place (with 3.12 that would
mean in particular, updates for LIB312D.EXE, 312PTD.EXE and the Lan driver set in
ODI33G.EXE).
Barry Schnur
Novell Support Connection Volunteer Sysop
http://support.novell.com/forums/
Please post replies ONLY via the Newsgroup
Shaun Pond
From TID 2948195
Symptom
When loading the Lan driver an error is reported saying "loader cannot
find public symbol..."
Troubleshooting
You need to know the Spec of your Lan driver. You can learn this from
documentation, trial and error, or a neat little utility called
drvspec.exe This can be found by going to http://support.novell.com
clicking on 'file finder' and doing a search for DRVSPC.EXE. Read the
txt file on using the ustility. The key is that it will give you a 2
line response and the last thing it will have is the specification, it
will say 3.2 for 32 Spec 3.3 for 33 Spec and 3.31 for the 331 Spec.
Cause
Lan Drivers are written to certain specifications, for simplicity sake
those specifications are called 32 Spec, 33 Spec, and the newest is 331
Spec. logic dictates that if you have a 33 Spec Lan card but are
loading the 32 Spec support modules that you will have failure. In fact
what Netware reports is the 'public symbol' error.
Another reason you will get the 'public symbol' error is if those
support modules are cross-spec'd What I mean by that is that 2 of your
support modules are 32 Spec and the 3rd one is a 33 Spec module or vice
versa.
There is one more cause of these 'public symbol' errors and that is if
all 3 support modules are from the same Spec but one of them is the
wrong version of that spec. Right now there are 2 download files
available from the web site that are specificly LAN support module
downloads. They are: LANDR9.EXE and ODI33F.EXE. If you have 2 support
modules from landr9 and one from odi33f you have a 'version mis-match.'
That will report the 'public symbol' errors as well.
Solution
Know your driver specification and use all three support modules from
the same source and the same Spec.
The support modules used for 32 Spec are:
Token-Ring 3.x: tokentsm.nlm, msm31x.nlm, and lslenh.nlm
Ethernet 3.x: ethertsm.nlm, msm31x.nlm, and lslenh.nlm
Token-Ring 4.x: tokentsm.nlm, msm.nlm, and lslenh.nlm
Ethernet 4.x: ethertsm.nlm, msm.nlm, and lslenh.nlm
The support modules used for 33 Spec are:
Token-Ring 3.x: tokentsm.nlm, msm31x.nlm, and nbi31x.nlm
Ethernet 3.x: ethertsm.nlm, msm31x.nlm, and nbi31x.nlm
Token-Ring 4.x: tokentsm.nlm, msm.nlm, and nbi.nlm
Ethernet 4.x: ethertsm.nlm, msm.nlm, and nbi.nlm
Note: When the msm31x.nlm and the nbi31x.nlm modules load you will get
a message that is just informational that says that the name of the
module is really msm.nlm and nbi.nlm respectively. The message can be
ignored. This is just telling you that when you type modules you will
not see a module called msm31x.nlm or nbi31x.nlm but they will display
msm.nlm and nbi.nlm. This name change is done to make it easy to
identify which OS the module is for.
Shaun Pond
Novell Support Connection SysOp