Can't find public symbol

[jeffkelly]

OK, here's my final issue with the new server...

I'm using a E100B ethernet card. When Ethertsm.nlm/MSM.nlm are loaded, I get 7 "loader cannot find public symbol" messages. I updated the server to the latest 3.12 ODI patch posted on Novell's website and still get the message. The server seems to work fine and I am not getting any communication errors as shown inside the monitor console. Are the errors benign or should I be worried of an impending crash down the road? Is the problem with the version of MSM or with the LAN driver? Also, does anyone know what the difference is between E100b.lan and E100b32.lan? They both seem to operate the same on my server?

Thanks to everyone who have responded to my recent flurry of postings!

Jeff

 

[marvhuffaker]

Generally, you need newer MSM.NLM and ETHERTSM.NLM files to avoid the public symbol errors. Usually those files come with the driver of the NIC. I'm surprised your nic even loads in the scenario you describe.


Also, I believe E100b32.lan is Novell's Client32 for dos/windows. At one point, if I recall correctly, they were interchangable between server and workstation client.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[JockMullin]

Hi, Jeff

You also need the latest lib updates. If memory serves it is lib312d. This contains the clib updates which should resolve the public symbols.

FYG I have seen servers running for a long time with those errors on lan drivers, but I recommend eliminating them if possible.

Jock

 

[jeffkelly]

Confused to say the least. Well, it's fixed, but I'm not sure if the solution is appropriate.

The autoexec.ncf has the following:
File server name....
ipx internal number...
register memory...
load streams
load remote...
load rspx
load after311
load nwsnut
load c:\server.312\ce100b frame=......
bind ipx to spx......
A few set statements afterward.

I noticed that when the nic driver loaded, it autoloaded msm.nlm and ethertsm.nlm. It was msm.nlm that was causing the public symbol errors. Msm.nlm would then unload and msm31x.nlm would autoload in its place. Since msm.nlm unloaded, the public errors were benign. That's why my server was working.

To fix the problem, I simply renamed msm.nlm to msm.old in my sys:system directory and in c:\server.312. In their place is a copy of MSM31x.nlm. Now the server boots without any errors.

This was done after verifying that the latest clib and intel drivers were installed.

Does this solution sound appropriate? Why doesn't MSM.nlm work w/ my 3.12 server? Maybe it is for NW4 and above???

Jeff

 

[JockMullin]

Hi, Jeff

Sounds good to me and that is likely exactly the problem.

It is getting harder and harder to support 3.12, unfortunately.

Jock