lfns造句

• The VFAT specification allows Long File Names ( LFNs ).
• It allowed mixed-case Unicode long filenames ( LFNs ), in addition to classic " 8.3 " names.
• NTFS, a file system used by the Windows NT family, supports LFNs natively, but 8.3 names are still available for legacy applications.
• On FAT12 and FAT16 volumes, testing for the values at 0x1C to be non-zero can be used to distinguish between VFAT LFNs and pending delete files under DELWATCH.
• For backward and forward compatibility LFNs were implemented as an optional extension on top of the existing FAT file system structures using a workaround in the way directory entries are laid out.
• Windows NT supported LFNs on NTFS file systems starting with the release of NT 3.1, and all of its utilities, including File Manager, were updated to support LFNs.
• Windows NT supported LFNs on NTFS file systems starting with the release of NT 3.1, and all of its utilities, including File Manager, were updated to support LFNs.
• OS / 2 stores LFNs for FAT filesystems in . LONGNAME extended attributes that are incompatible with Microsoft's implementation and only visible to tools supporting OS / 2's standard.
• FreeDOS can also be used with a driver called " DOSLFN ", which supports long file names, but most old programs before Win95 do not support LFNs even with driver loaded unless they have been recompiled.
• For backwards-compatibility with MS-DOS and older Windows software, which recognizes filenames of a maximum of 11 characters in length with 8.3 format ( i . e . : an eight-letter filename, a dot and a three-letter extension, such as autoexec . bat ), files with LFNs get stored on disk in 8.3 format ( longfilename . txt becoming longfi ~ 1 . txt ), with the long file name stored elsewhere on the disk.