当前位置: 首页 > news >正文

what is 8.3 file-naming convention?

 

The term “8.3 filenames” refers to the legacy file-naming convention used by MS-DOS and early versions of Windows (as well as FAT file systems) in which file names were limited to:

  • 8 characters for the base name, and

  • 3 characters for the file extension.

Hence the shorthand: “8.3 format.”


🧩 Structure Example

FILENAME.EXT
^^^^^^^^ ^^^
│        └── Extension (3 characters)
└─────────── Base name (up to 8 characters)

Examples:

  • COMMAND.COM

  • AUTOEXEC.BAT

  • README.TXT

  • GAMEINFO.NFO

If a filename exceeded this limit (for example, ThisIsALongFileName.txt), it would be truncated and altered for compatibility — e.g. THISIS~1.TXT.


⚙️ Historical Context

  • Introduced with MS-DOS 1.0 (1981) and persisted through the FAT12, FAT16, and FAT32 file systems.

  • Designed to simplify file handling in early operating systems with limited memory and directory indexing.

  • The 8.3 constraint was a result of FAT directory entries being 11 bytes long (8 for the base, 3 for the extension).

  • The file names were case-insensitive, stored in uppercase, and allowed only certain characters (A–Z, 0–9, and some symbols like _ and -).


🪶 Transition

With the advent of Windows 95, Microsoft introduced VFAT, which allowed long filenames (LFN) — up to 255 characters, mixed case, and Unicode support — while still retaining a hidden 8.3 alias for backward compatibility with older programs.

Example:

  • Long filename: MyLetterToTheEditor.txt

  • 8.3 alias: MYLETT~1.TXT


🧠 Why It Matters

The 8.3 convention shaped early computing culture, including:

  • Naming conventions in DOS, early Windows, and BIOS-level firmware.

  • The origins of short extensions like .NFO, .DOC, .EXE, .COM, .BAT.

  • Constraints that encouraged brevity and mnemonic creativity in early software distribution.


In short:
8.3 filenames were the strict DOS-era naming rule, born from hardware limits and filesystem simplicity, later serving as a fossilized compatibility layer even in modern Windows systems.

 

http://www.hskmm.com/?act=detail&tid=32235

相关文章:

  • 2025智慧水务平台
  • 机惨
  • auipc指令在NEMU中的执行过程 - Zeeh
  • 如何在AutoCAD中进行GIS空间查询?
  • initContainers实现整个数据目录的挂载
  • 2025年屋脊通风天窗厂家最新权威推荐榜:工业厂房自然通风解决方案优选品牌
  • 2025年10月电子散热器行业权威报告:十大品牌技术创新、性能表现与市场布局全景解析及选购指南
  • 迁移boot分区解决brtfs引起的Sparse File Not Allowed问题
  • 阿里面试:Redis挂了怎么办?集群主节点挂了怎么 恢复数据?可能有多长时间 数据丢失?【转自】
  • 2025年10月北京开锁公司最新服务商平台推荐排行榜,北京紧急开锁换锁上门服务推荐!
  • 学霸的期末 解题报告
  • 一种适用于正整数值域的无旋平衡树
  • 2025 年电子散热器厂家 TOP 企业品牌推荐排行榜,电子 / 型材 / 插片 / 电源 / 固态 / 变频器 / 铝合金 / 逆变器散热器 / 散热器铝型材公司推荐
  • 禁用sentinel
  • 静态网站宣言:用IPFS重建开放网络的乐趣
  • 收敛数列的性质
  • Eclipse Mosquitto MQTT 代理中持久性引擎(database.c 概念)的作用分析报告 - 指南
  • FFmpeg 实现视频批量剪辑
  • 2023盘古石 物联网取证部分
  • 2025 年自润滑轴承厂家联系方式推荐,宁波索力特复合材料有限公司专业产品与可靠服务指南
  • MATLAB PSO-PF 融合滤波
  • SaltStack 集群安装指南
  • nginx基本配置详解
  • NCS 3.1.1 蓝牙如何设置 public 地址
  • C# Avalonia 16- Animation- BlurringButtons
  • iOS 26 崩溃日志导出全流程,多工具实践 辅助分析策略
  • 小白也能学会的 rime + 万象拼音 输入法安装教程
  • 别再争了,“Prompt已死”是个伪命题
  • 2025.10.16——1绿
  • 2025年通风气楼厂家最新权威推荐榜:工业厂房自然通风与消防排烟系统专业解决方案精选