V_OS2.NLM problem

Hello all

When i try to load V_OS2.NLM to be able to run VREPAIR on a 3.11 server with long filename support, i get 'loader cannot find public symbol' about 30 times...!? Anyone have any idea what could be missing? I use OS2.NAM and 3 other NLM's on the server (for long filename support on NW3.11), as described in Novell readme for Win95 client.

Any help appreciated!
hbnAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

unitymtgCommented:
You have to install the base 3.11 OS patches to load long name space.
If you have not had long name sapce loaded before you run VREPAIR, there is not reason to run it when you run vrepair.  If you don't have it running before, that means long namespace is not currently being supported and you can remove it using vrepair.
MAKE SURE YOU ARE RUNNING THE MOST RECENT VERSION OF VREPAIR
How to do this:
Dismount your volume.
Load VREPAIR
Select 2. Set VRepair Options
Select 1. Remove Name Space Support
Select 4. OS/2

This will remove long namespace support and you can run vrepair without loading the .nam's.
Even if you don't need long namespace support, I would recomend installing the base OS updates which is available under the minimum patch list.
Go to http://support.novell.com for the patches.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
hbnAuthor Commented:
I have used OS2.NAM on this server for about 6 months, and used VREPAIR 2-3 times without problem. If i don't load V_OS2.NLM before VREPAIR, it complaints (ofcourse). I haven't made any major changes in the system, but i will take your advice and load the minimum patches. There is always a risk that some NLM have been replaced accidentaly.

Thanks for your answer.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.