Technical article 100013

What filenames are supported with SCO AFPS and LAN Manager on OpenServer 5?

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

What forms of filenames are supported by the Advanced File and Print Server and LAN Manager products and their associated clients? Sometimes I can't see certain files on my servers.

Cause

Both the SCO Advanced File and Printer Server and LAN Manager
products are networking technology that has been transferred
from the Microsoft MS-DOS, Windows and NT operating systems
to the UNIX operating system.  The clients of these products
are, for the most part, Microsoft operating system based.  As
such, these various operating systems will internally store,
and externally represent, each other's files differently.
Filenames can vary in the length of characters used, and in the
choice of those characters, depending with which operating system
and application they are created.  For example, the UNIX operating
system will support filenames of up to 255 characters in length,
and use both upper and lowercase characters.  MS-DOS and Windows
3.11 and their applications only support filenames of 12-character
length in the format 8.3, in uppercase only.  Windows 95 supports
filenames of a greater length than this MS-DOS 8.3 limitation.

Once created, files may be stored or placed in a shared filesystem that is under the control of another operating system. The file can then be "viewed" from several other operating system environments. An example of this would be if a file of greater length than the usual MS-DOS 8.3 format is created under Microsoft Windows 95, placed in an Advanced File and Print Server shared filesystem and then viewed using the File Manager of Windows for Workgroups.

Solution

SCO AFPS or LAN Manager running over the SCO OpenServer 5.0 or SCO
UNIX Version 4.2 operating systems supports filenames up to 255
characters in length, both lower and mixed case. Files as above
can be placed in the UNIX filesystems or in shares. The files can
originate from other UNIX systems, MS-DOS, WFWG 3.11, Windows 95,
MS NT 3.5, and so on.  How will these files be seen on the AFPS/LAN
Manager share by clients?
UNIX

Files of any origin stored on the shares or UNIX filesystem can be seen by the UNIX operating system.

MS-DOS

Using software such as LAN Manager Client 2.2 for MS-DOS, it will only see files in an MS-DOS 8.3 format. If a file is created by another utility in uppercase 8.3 format on the share, it will not be seen by the MS-DOS client.

As UNIX differentiates between files in uppercase and lowercase, MS-DOS files stored on a share will be converted to lowercase format.

MS Windows 3.1
As above.
MS Windows for Workgroups 3.11
Still creates files of 8.3 format. However it can
see files longer that the 8.3 format if the flag
"longfilename=1" is set in the file "c:\windows\winfile
.ini".
MS Windows 95

Can create long filenames (>8.3) of mixed case. It can then store and see files of length greater than 8.3 on the share. If a file of mixed case is created and stored on a share, it will be converted to all lowercase automatically by the server. If that file is stored on a Microsoft NT server, the mixed case is preserved.

MS NT 3.5
NT supports both NT and MS-DOS filesystems resident in
the operating system.  It also contains both native NT
and MS-DOS/Windows applications.  NT can create files
of name length greater than 8.3 using NT applications
and store them on a share. It can also create files
using the resident MS-DOS utilities and store these
on the same share.  However, if an NT application file
is opened by a native MS-DOS utility and subsequently
saved to the share, its filename will be truncated to
8.3 format.  NT File Manager is able to see its own
long filenames on the share. NT MS-DOS native
applications such as QBASIC, for example, will only be
able to see 8.3 format files on the share and not the
long files created by its own native NT applications.

If two mixed case files are created on an NT file- system, for example, called "Fred" and "freD", the second created will fail as the two names collide. Under UNIX, they can coexist.

Lan Manager Client (LMC)

LMC as part of SCO OpenServer 5.0 or SCO UNIX Version 4.2, as per MS-DOS, will only see files of 8.3 format.

The Support Level Supplement (SLS) APP433a for SCO AFPS 3.5.1f and the same functionality included in SCO AFPS release version 3.5.2n now provide facilities for handling "long" (>8.3) filenames mixed case filenames, and names that include 8-bit characters (upper part of ISO- 8859-1 character set). Filenames of this format can be created via UNIX or from a Microsoft Client and manipulated on the SCO AFPS server.

Microsoft operating systems such as WFWG 3.11, Windows 95, NT 3.51, NT 4.0, will be able to address files on the AFPS server in 8-bit, mixed case, and long filename format. MS-DOS and LMC clients however, still only understand 8.3 format and will not see such files.

Please refer to the SCO documentation for a detailed discussion of the facility.

NOTE: This facility is not available for SCO LAN Manager for UNIX.

See also

IT lmu/69, "DOS clients cannot see files with uppercase or long filenames."

"UNIX to Windows filename mapping", SCO Advanced File and Print Server Release Notes, P22/23.

"Filename Mapping", SCO Advanced File and Print Server 3.5.2n Release Notes, P6.

"Filename Mapping", SCO Advanced File and Print Server Administrator's Handbook, Appendix A.

From the Xinuos technical article database, record 100013. Reproduced with permission. The original is at www.sco.com/ta/100013, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.