Windows still has 45-year-old quirks, and most are safe to leave alone

Windows has changed enormously over the past four decades, but some parts of it still feel familiar to anyone who used MS-DOS in the 1980s.You can run modern applications, use advanced file systems, and even run Linux inside Windows, yet the operating system still follows conventions that were established when floppy disks were standard equipment.Add How-To Geek on Google Add as Preferred Source Follow on Google Discover Some of these quirks look rather strange today, especially if you have spent time using Linux or macOS.

However, changing them now would create considerably more problems than leaving them alone.Why Windows still uses backslashes for file paths A decision from DOS 2.0 that became permanent If you have used Linux or macOS, you are probably familiar with file paths that look like /home/user/Documents.Windows, however, uses C:\Users\Name\Documents, with backslashes separating directories.

It is a small difference, but one that has confused people switching between systems for decades.The reason goes back to MS-DOS 2.0, released in 1983.Earlier versions of DOS already used the forward slash (/) to identify command-line switches, so when DOS 2.0 introduced hierarchical directories, Microsoft needed another character to separate directory names.

Unix already used the forward slash for this purpose, but adopting it would have conflicted with existing DOS command syntax.The backslash (\) became the standard separator instead.Interestingly, modern Windows is more flexible than you might think.

Many Windows APIs accept forward slashes in file paths and automatically convert them into backslashes.For example, C:/Users/Name/Documents works in many programming environments.However, Command Prompt and certain Windows utilities still interpret forward slashes as command switches, so you cannot assume that both forms will always work.

You might wonder why Microsoft has never standardized everything around forward slashes.The problem is that decades of applications, scripts, and utilities already depend on the existing convention.Changing it would offer very little practical benefit while potentially breaking a great deal of software.

Besides, at this point, the backslash is practically part of Windows’ identity.You still cannot name a folder CON or NUL Windows remembers devices that most people have forgotten Close Try creating a folder named CON in File Explorer.Windows will refuse, even though there is nothing particularly unusual about those three letters.

The same restriction applies to names such as PRN, AUX, NUL, COM1 through COM9, and LPT1 through LPT9.These names date back to DOS, when they identified hardware devices rather than ordinary files.CON represented the console, PRN referred to a printer, AUX was associated with an auxiliary device, and NUL was a special destination that discarded anything written to it.

The COM and LPT names identified serial and parallel ports.For example, a DOS program could send output to LPT1 to communicate with a printer.It did not need to know which physical file represented the printer because DOS handled the name as a device.

Windows inherited these conventions, and they remain recognized today.Interestingly, Windows 11 has relaxed this restriction somewhat.You can now create files with names such as CON.txt or NUL.txt, although some applications may still have trouble handling them.

The original reserved names without extensions remain restricted in ordinary Windows file operations.There are also ways around some of these restrictions using the extended path syntax, which begins with \\?\.This lets applications bypass certain normal Win32 path-processing rules, although the results depend on the specific name and API involved.

It is a specialized workaround rather than something you should use for ordinary files.These restrictions can occasionally cause problems when transferring files from Linux, where such names are generally allowed.However, most Windows users will never encounter them, and there is little reason to change the behavior.

Drive letters A and B are still associated with floppy disks Your PC has moved on, but the lettering convention remains Have you ever wondered why your main Windows installation is almost always on the C: drive? Why does Windows apparently skip the first two letters of the alphabet? The answer is floppy disks.On early IBM-compatible PCs, the A: drive typically represented the first floppy drive, while B: represented a second floppy drive.Hard drives were not standard equipment on the earliest machines, and when they became common, C: was the natural choice for the first hard disk.

Decades later, floppy drives have practically disappeared from everyday computing, but Windows still normally uses C: for its system drive.Additional storage devices are typically assigned D:, E:, and subsequent letters.However, there is an interesting detail here.

Windows does not permanently prohibit you from using A: or B:.You can manually assign those letters to other volumes, subject to the usual restrictions on available drive letters.Microsoft could have made A: the default system drives years ago, but what would that accomplish? Plenty of programs, configuration files, and scripts assume that Windows is installed on C:.

Although good software should not rely on that assumption, changing a convention this established would create unnecessary compatibility problems.The empty space at the beginning of the alphabet is a harmless reminder of an era when installing software meant inserting floppy disks one after another.Windows still treats uppercase and lowercase filenames as the same A small difference that can surprise Linux users On a typical Linux file system, Report.txt and report.txt can exist in the same directory as two completely separate files.

Windows usually treats them as the same filename.This behavior is called .Windows remembers the capitalization you used when naming a file, but it does not normally consider capitalization when looking for that file.

For example, you can create a file named Budget2026.xlsx and open it by referring to budget2026.xlsx.Windows will find the same file regardless of how you capitalize the name.Related 5 legendary open-source Windows apps that still don't work on Linux These legendary open-source Windows tools prove Linux still has a compatibility problem.

Posts 36 By  Jorge A.Aguilar This is convenient for everyday use, particularly when typing paths manually.However, it can cause unexpected problems when working on software projects across Windows and Linux.

Suppose a developer references Config.json in their code, but the actual file is named config.json.The application might work perfectly on Windows and then fail when deployed to a case-sensitive Linux environment.Interestingly, NTFS can support case-sensitive directories, and Windows allows you to enable this behavior for individual directories.

Microsoft introduced this capability partly to improve compatibility with the Windows Subsystem for Linux (WSL).Still, there is little reason for an ordinary Windows user to change the default.Case-insensitive filenames are an established part of the Windows experience, and most desktop applications are designed around that behavior.

Those strange PROGRA~1 filenames have a purpose Windows still supports the old 8.3 naming format If you have spent enough time exploring Windows through Command Prompt, you might have encountered a directory name such as PROGRA~1.It looks like something went wrong while displaying the filename, but it is actually another compatibility feature.Early DOS file systems used the 8.3 naming convention.

Filenames could contain up to eight characters before the extension and three characters after it.Names such as README.TXT fitted this format perfectly, but something like My Important Documents did not.When Windows introduced support for longer filenames, it needed a way for older applications to continue accessing them.

One solution was to generate short aliases using the old 8.3 format.For example, the Program Files directory might have a short alias such as PROGRA~1.Older applications could use the short name without needing to understand the longer one.

You can check whether a file or directory has a short name by opening Command Prompt and running: dir /x Windows will display short names alongside ordinary filenames where those aliases exist.However, modern Windows does not necessarily generate these aliases for every file.Whether 8.3 name creation is enabled depends on the volume and system configuration.

You can inspect the configuration using the fsutil 8dot3name command, and Windows also provides ways to disable short-name creation on individual volumes.Related If you've never opened Windows Terminal, you're missing the most powerful tool already on your PC Harness the power of the command line on Windows.Posts 1 By  David Delony There can be legitimate reasons to disable it, especially in environments with huge numbers of files where short-name generation adds unnecessary overhead.

However, existing software may still depend on those aliases, so disabling the feature without checking compatibility is generally a bad idea.For most users, these strange-looking names are simply another feature that Windows keeps around for applications that refuse to retire.Some old Windows habits are better left alone Windows is still shaped by decisions made for computers that had only a fraction of the capabilities of a modern PC.

The people designing DOS in the early 1980s probably never imagined that some of their conventions would still be around more than four decades later.Yet here we are, running Windows 11 on machines with terabytes of storage, while the operating system still remembers what LPT1 means.

Read More
Related Posts