A second, long file name API was created for Windows 95 / MSDOS 7.1. The LFN drivers were designed to duplicate this feature under regular DOS, FreeDos has the DOSLFN driver but few true DOS programs support long file names. 4DOS the Command.Com replacement has LFN support, but it is a special feature,. Often it was from programs once run under Windows 9X VFAT16 or VFAT32 is FAT with long filenames. FAT32 is the large disk support, without the patented LFN stuff. LFN programming requires digging into some low level coding, not really well supported by most programming languages. The programmer must handle many things which are done by the traditional Short File Name support in their chosen language.
![Why does DOS use 8.3 Filenames? [Byte Size] | Nostalgia Nerd](http://i.ytimg.com/vi/eGIyCD2_qA8/mqdefault.jpg)
![Why does DOS use 8.3 Filenames? [Byte Size] | Nostalgia Nerd](/img/tr.png)
Tip: if you double click on the window menu box it will close it automatically
A second, long file name API was created for Windows 95 / MSDOS 7.1. The LFN drivers were designed to duplicate this feature under regular DOS, FreeDos has the DOSLFN driver but few true DOS programs support long file names. 4DOS the Command.Com replacement has LFN support, but it is a special feature,. Often it was from programs once run under Windows 9X VFAT16 or VFAT32 is FAT with long filenames. FAT32 is the large disk support, without the patented LFN stuff. LFN programming requires digging into some low level coding, not really well supported by most programming languages. The programmer must handle many things which are done by the traditional Short File Name support in their chosen language.