We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

OS2 Name Space and Windows 95 problem

lfffd
lfffd asked
on
Medium Priority
310 Views
Last Modified: 2012-05-04
I have 15 remote boot workstations with windows'95 and microsoft client for netware. Before instalation i edited MSBATCH.INF adding:
SupportLFN=2 (0 is for truncated filenames, 1 for long uppercase filenames ISO type, 2 for long ASCII filenames).
The installation is working fine, there's just one problem:
When I create files using portuguese characters in the name the system creates and writes to the file, but then, it no longer gets access to rename, delete, copy, move ou read the file. Neither i can do that with Explorer. The only workaround is using Novell's FILER.
I'm running Netware 3.11 with OS2 name space and OS2OPNFIX loaded.
Comment
Watch Question

Commented:

Hi, lfffd! I have found three TID's on Novell CD that seems to be related to your problem.

First TITLE: Windows 95 Long File Names under NetWare 3.11
DOCUMENT ID:      TID1203062
DOCUMENT REVISION:      3
DATE:      1FEB97

NOVELL PRODUCT and VERSION:
NetWare 3.11
Windows 95
NetWare Client32 for WIN95 2.1
GroupWise 4.1a for Windows

ISSUE
Windows 95 Long File Names are not officially supported on NetWare 3.11 with
Microsofts Client for NetWare Networks, but it is possible to use them.
The procedure is this:

1) If the OS2 name space is already applied it must be removed with VRepair.
This will lose any OS2 extended attributes on files that have been put there
by OS2 workstations.

2) Apply the current OS patch kit for NetWare 3.11. At the time of writing
it is 311pte.exe. This will apply the os2opnfx.nlm patch, as well as many others,
which is required to support Win95 LFN on NetWare 3.11. Note that this patch kit
may require an update to clib.nlm. The current version of clib.nlm is available
in libup9.exe.

3) Copy os2.nam into the directory on the C: partition that you run server from
(often server.311 or netware.311) if its not there already.

4) Add OS2 name space to the volume (LOAD OS2, ADD NAME SPACE OS2 volumename).

5) Add LOAD OS2 to the startup.ncf file. It should go between the patches being
loaded and the disk controller drivers.

6) Use Regedit to add "SupportLFN=2" to
Hkey_local_machine\System\CurrenControlSet\Services\Vxd\Nwredir

Choose the edit option and select a new string value and add the "SupportLFN=2"
as the new string value.

7) Add a new section "[nwredir]" to system.ini, and add a line "SupportLFN=2" to it.

Windows 95 should now recognize the volume as LFN-capable.

Second TITLE:      OS2 long file names Windows 95
DOCUMENT ID:      TID1005596
DOCUMENT REVISION:      1
DATE:      26SEP95

NOVELL PRODUCT and VERSION:
NetWare Client for DOS/MS Windows 1.2
Windows 95

SYMPTOM
Customer is running Windows 95 with Microsoft Client.  They have a NetWare 3.11
server with long filenames created on the file server and filenames were appearing
in 8.3 format.
Why are they appearing in the 8.3 format?  
Configuration:
load os2
add name space os2 to volume sys
os2opnfx.nlm  (patch ) is loaded.
Everything on file server was configured properly.

SOLUTION
If the NetWare patch (os2opnfx.nlm) has been applied to 3.11 server or if long
filenames support is applied to 4.x and 3.12 servers, you can ensure support for
long filenames with all NetWare servers by adding this line to your system.ini:

[Nwredir]
SupportLFN=2

OR
by setting SupportLFN=2 in the following Register key:
Hkey_local_machine\system\CurrentControlSet\Services\VxD\Nwredir

Third TITLE: Errors accessing files from a Windows 95 w/s
DOCUMENT ID:      TID1005198
DOCUMENT REVISION:      1
DATE:      5OCT95

NOVELL PRODUCT and VERSION:
NetWare Client for DOS/MS Windows 1.2
Windows 95

SYMPTOM
Attempting to access files on a 3.11 NetWare server from a Windows 95 w/s may
return one of the following errors:

"File not found" - when you know the file exists
"Sharing Violation" or "Lock violation"
"Unable to open file"
"File in use"

SOLUTION
The problem only occurs when attempting to access files with long names on a
NetWare 3.11 server.  The resolution is to download 311ptd.exe from Compuserve
and load the os2opnfx.nlm on the server.  The patch is built into NetWare 3.12
and 4.x.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.