Long filename
This article needs additional citations for verification. (February 2015) |
Long filename (LFN) support is
To maintain compatibility with older operating systems, Microsoft formulated a method of generating an 8.3 filename from the long filename (for example, Microsoft.txt
to MICROS~1.TXT
) and associating it with the file.
Compatibility issues
Microsoft implemented support for LFNs in the FAT filesystem by using hidden directory entries, of the volume label type, to store the longer names; this scheme is known as
When LFN support was first introduced into a DOS-based operating system in the form of Windows 95, it caused some problems for older programs. For example, a DOS program performing sector-level directory operations while Windows was in DOS mode could destroy long filename information so, by default, sector-level access to hard disks was disallowed in this mode.
Upon booting into plain DOS, the long filenames are not visible unless a VFAT LFN driver is installed. Microsoft did not add LFN support to many of its older programs, including
Limits
Because the FAT LFN implementation is layered atop an older, more limited naming system, there are inevitable complications, such as if an attempt is made to create too many files with the same first six letters.
The long filename system allows a maximum length of 255
\ / : * ? " < > |
). This is achieved by chaining up to 20 directory entries of 13 2-byte Unicode characters each.[4]While long filename support allows for longer file and directory names, under DOS-based systems, the absolute file path constructed from the associated short file and directory name equivalents is still represented in an internal data structure called the
VFAT LFN drivers
The following is a list of drivers that can be used to provide support for VFAT long file names as used in Windows 95. Although drivers such as DOSLFN can be loaded in almost any versions of DOS, it works best on DOS versions that have support for LFN themselves, such as
DIR
would show long file names as well.
OS | Driver name | Provider |
---|---|---|
any plain DOS | DOSLFN, LFNDOS | third-party |
DR-DOS | LONGNAME | included |
RxDOS
|
built-in | included |
OS/2 | VFAT-OS2.IFS | third-party |
Windows NT 4.0 | NTLFN | third-party |
Driver-less Real Mode Dos LFN commands
Some small real mode Dos programs have also been written over the years, although many have been lost over time. One notable collection of programs that still exists is LFN Tools, which is open source and comprises seven useful LFN commands written in C++ and assembly language, with documentation included in English and German, and is available at LFNTOOLS on Sourceforge.net.
Other implementations
Before LFN support was implemented into the FAT family of file systems, various file managers provided their own methods to attach and maintain longer file descriptions. Among the first to do so are the alternative command line processors
-based applications.In order to support
See also
- TRANS.TBL
- Rock Ridge
- Joliet (file system)
- Romeo (file system)
- 8.3 filename
- 6.3 filename
- Filename
- VFAT patentissues
- Design of the FAT file system
- File system
- Large file support(LFS)
References
- ^ "MSDOSFileSystem". CocoaDev. 2005-09-12. Archived from the original on 2006-10-18.
- ^ "Errors Creating Files or Folders in the Root Directory". Microsoft. 120138.
- Microsoft Corporation. 810456. Archived from the originalon 2008-04-23. Retrieved 2007-04-19.
- ^ a b Dobiash, Jack "vinDaci", ed. (1998-01-06) [1996-11-18]. "Long Filename Specification" (4 ed.). Grand Ronde, Oregon, USA. Archived from the original on 2015-10-25. Retrieved 2013-05-22.
- INTER61.
- ^ a b Paul, Matthias R. (1997-07-30) [1994-05-01]. NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. MPDOSTIP (in German) (3 ed.). Archived from the original on 2017-09-10. Retrieved 2014-08-06. (NB. NWDOSTIP.TXT is a comprehensive work on Novell DOS 7 and OpenDOS 7.01, including the description of many undocumented features and internals. It is part of the author's yet larger
MPDOSTIP.ZIP
collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of theNWDOSTIP.TXT
file.) [3] - ^ a b Paul, Matthias R. (1997-06-07) [April 1994]. "Chapter 1.3.xi: Überlange Pfade". NWDOS7UN.TXT — Zusammenfassung der dokumentierten und undokumentierten Fähigkeiten von Novell DOS 7. MPDOSTIP (in German). Archived from the original on 2016-11-07. Retrieved 2016-11-07.
- ^ 4DOS 8.00 online help.
- pseudo-environment variables,.)
0xED
being reserved for Digital Research/Novell/Caldera and0xFD
for FreeDOS - ^ Davis, Jeremy. "FreeCom and 4DOS DESCRIPT.ION files" (FreeDOS tech note). FreeDOS. Archived from the original on 2016-11-11. Retrieved 2016-11-11.
- ^ Paul, Matthias R. (1997-05-01) [1995-03-01]. "Hinweise zu JPSofts 4DOS 5.5b/c, 5.51, 5.52a und NDOS". MPDOSTIP (in German). Archived from the original on 2016-11-04. Retrieved 2015-05-08. (NB. The provided link points to a HTML-converted version of the
4DOS5TIP.TXT
file, which is part of theMPDOSTIP.ZIP
collection.) [4] - ^ Novell (1999-02-11). "TID1002030 Windows NT, Long File Names on NetWare". Archived from the original on 2011-06-06. Retrieved 2007-12-03.
- ^ 4690 OS Programming Guide Version 5.2 (PDF). IBM. 2007-12-06. IBM document SC30-4137-01. Archived from the original (PDF) on 2022-01-25. Retrieved 2018-09-03.