Long Filename Support on NetWare 3.x, 4.x, 5.x
(Last modified: 25Oct2002)
This document (10019083) is provided subject to the disclaimer at the end of this document.
goal
Long Filename Support on NetWare 3.x, 4.x, 5.x
How do I enable Long File Name Support for the workstation on a servers volume?
fact
Formerly TID 2929574
fix
NW 3.11
1. Apply the current OS patch set (currently 311ptg.exe)
2. On the Server, Load os2.nam
3. On the Server, at the console prompt, type: ADD NAME SPACE OS2 TO VOLUME <VOLNAME>
4. Reboot workstation and test.
5. Place "Load OS2" in the STARTUP.NCF file.
NW 3.12 or NW 3.2
1. On the Server, Load os2.nam
2. On the Server, at the console prompt, type: ADD NAME SPACE OS2 TO VOLUME <VOLNAME>
3. Reboot workstation and test.
4. Place "Load OS2" in the STARTUP.NCF file.
NW 4.0x and NW 4.10
1. On the Server, Load os2.nam
2. On the Server, at the console prompt, type: ADD NAME SPACE OS2 TO VOLUME <VOLNAME>
3. Reboot workstation and test.
4. Place "Load OS2" in the STARTUP.NCF file.
NW 4.11 and NW 4.20
1. On the Server, Load LONG.NAM
2. On the Server, at the console prompt, type: ADD NAME SPACE LONG TO VOLUME <VOLNAME>
3. Reboot workstation and test.
4. Place "Load Long" in the STARTUP.NCF file.
NW 4.11 SFTIII
1. On the Server, at the MS (Mirrored Server) console prompt, Load LONG.NAM
2. On the Server, at the MS (Mirrored Server) console prompt, type: ADD NAME SPACE LONG TO VOLUME <VOLNAME>
3. Reboot workstation and test.
4. Place "Load Long" in the STARTUP.NCF file.
NW 5.0
Long name space is supported by default with NetWare 5, you do not have to
Notes:
- Long.nam should not be loaded on NW 4.10 and below, you should load os2.nam instead of LONG.NAM for long file name support.
- If you have Mac name space on your volume currently, you should consider the issue discussed in Technical Information
Document 1007579.
- The Add Name Space command is a process. You only need to run that process once, it does not have to be in your startup or AUTOEXEC.NCF files.
- You need to reboot Win95 and WinNT workstation prior to being able to save long named files to the server after adding long name space support.
- Your clients should be running the current Novell Client on them. If they are not, then you may not have long name space support on network drives on that machine. Link to the current Novell Clients: http://www.novell.com/download/
- If you have the need to remove a name space from a volume, this is done through vrepair. CAUTION: Removing a Name Space may corrupt files originating in that name space. (Example, if the mac namespace is removed, mac files lose their resource fork which may corrupt the file depending upon the application the file was written with) The procedures to remove a name space are Load Vrepair, Set Vrepair Options, Remove Name Space Support from the volume, Select the name space you want to remove, Run Vrepair on the volume.
document
| Document Title: | Long Filename Support on NetWare 3.x, 4.x, 5.x |
| Document ID: | 10019083 |
| Solution ID: | 1.0.34704474.2360662 |
| Creation Date: | 13Oct1999 |
| Modified Date: | 25Oct2002 |
| Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.