Could you explain to me the following change...
Articles and Tips: qna
01 Oct 2002
Q.
Could you explain to me the following change in the behavior I've observed in NetWare 6, as opposed to previous versions of NetWare? It is related to loading NLMs.
In versions of NetWare prior to version 6, if I create an NLM with name FILENAME.NLM but put in the appropriate field in the NLM header as a name, say HEADER.NLM, the following happens: When I enter the command LOAD FILENAME, the OS loads the NLM and displays this warning on the console screen:
Module name is HEADER.NLM not FILENAME.NLM
After that, if you look at the loaded NLMs using MODULES command, it appears as HEADER.NLM. Also, if I want to unload the module, I need to enter "UNLOAD HEADER.NLM". So it seems that the name from the NLM header has priority if they are different.
In NetWare 6, if I load the same NLM, the OS doesn't issue any warnings. If I check the NLM with the MODULES command, it appears as FILENAME.NLM. I unload it by entering UNLOAD FILENAME.NLM. So it seems to me that in NetWare 6, the name from the NLM header is ignored completely.
What has been changed in NetWare 6 and was it intentionally or just by accident?
A.
I reproduced this issue, although in my case the OS issues this warning:
SERVER-5.60-1956: Module name is VERY_LON.NLM not VERY_LONG_NAME.NLM
Any attempts to unload VERY_LON.NLM fail. To unload it, I must unload it by the long name, UNLOAD VERY_LONG_NAME.NLM. How does this apply to your question? I recommend you try to unload the NLM using the short name. If that fails, use the long name.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.