Enabling OS/2 Namespace

[andyshriver]

We have a NetWare3.12 server accessed on a LAN by a number of W2K and XPSP2 boxes with very few issues UNTIL... I tried to upgrade a client-server app residing on this server. The upgrade crashed 3% into the file copy process on every attempt. The PURGE utility (followed by BINDFIX) was run, so disk space is not at issue. There is plenty of RAM, so that is not at issue. The manufacturer of the app advised that use with servers not supporting long filenames has been problematic. I have read that enabling OS/2 namespace is a good fix for this problem, but how do I perform this and what are the potential problems and pitfalls?

Many thanks in advance.

Andy

 

[itsp1965]

It's been awhile but if I recall,it is quite safe to load an additional namespace as long as your SYS: volume has adequate disk space (doesn't take much) and you have avail memory. It is also recommended that you have the latest version of the namespace files. With that said, if I recall correctly all you need to do is from the console prompt is to LOAD OS2.NAM (make sure that you also update STARTUP.NCF to include this line). Hope this helps

 

[andyshriver]

Thanks for your reply. I think this procedure and its outcome are far less significant than I have led myself to believe, but I want to make sure that I add the LOAD OS2.NAM to the STARTUP.NCF file in the proper sequence (unless, of course, it doesn't matter where I insert it). The syntax of my STARTUP.NCF file is below:

REM THE FOLLOWING LINES WERE ADDED BY THE 3.2 ENHANCEMENT PACK INSTALLATION
LOAD C:\SERVER.312\CPUCHECK
LOAD C:\SERVER.312\START\PM312
PMLOAD C:\SERVER.312\START
REM END MODIFICATIONS MADE BY THE 3.2 ENHANCEMENT PACK INSTALLATION
load ide port=1f0 int=e

Thank you again for your help!

Andy

 

[marvhuffaker]

You need to also add the namespace to the volume.. Just loading OS2.NAM won't do it.

ADD NAME SPACE OS2 TO VOLUME <VOLNAME>

Before you do this, you can verify whether it's already there or not (maybe you're chasing the wrong problem) by typing:

VOLUMES

This will show you the mounted volumes as well as the name spaces that are installed on them.




Marvin Huffaker, MCNE

http://www.redjuju.com

 

[itsp1965]

And that's why it's good to hear someone else chime in. Thanks for the reminder Marv (I totally forgot about that)

 

[andyshriver]

Thank you, Marv. I checked, and there is one Volume (SYS), and the only namespace is DOS. So I gather that the sequence is:

Add the namespace to the volume,
Load OS2.NAM.
Add the command Load OS2.NAM to both STARTUP.NCF & AUTOEXEC.NCF.

Does this sound right?

Thanks again and in advance.

 

[marvhuffaker]

No, load the OS2.nam, then add the name space. I don't beleive you can add it without the module loaded first.

Once it's added, the OS2 will be required to load before volume will mount.. Thats why you add that to the startup.ncf file.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[andyshriver]

Perfect -- thank you very much, Marv & ITSP!!