Windows 10 Still Won’t Let You Use These File Names Reserved in 1974

Must read

Reddit chief: I was late to spot GameStop stock mania

Steve Huffman says he supported the aims of a Reddit group taking on the hedge funds. Source link

How to disable and delete Samsung Pay from your Galaxy phone

When it comes to paying conveniently, Samsung Pay makes using your phone as a bank card an easy process; however, there may come...

How to Hack the Hidden Google Chrome Dinosaur Game

Most of us have seen the dreaded “No Internet” error message on Google Chrome. You can actually turn this screen into a fun,...

The PS5 and Xbox restock at Walmart was a crushing marathon – when to look next

Update: The largest Walmart restock of PS5 and Xbox Series X in 20211 is over, and the US retailer is now sold out....
Bhawani Singh
I am a blogger who believes in delivering latest tech news from around the world to my viewers.

Windows “reserves” certain file names and doesn’t let you use them anywhere. Forget calling a file “con.txt” or “aux.mp3”. This is all because of a choice made in 1974 and Microsoft’s thirst for eternal backward compatibility.

File Names You Can’t Use

Microsoft provides an official list of reserved file names, and here they are:


Note that you can’t use these file names with any file extension. So you can’t name a file “con.txt”, “con.jpg”, “or “con.doc”. And Windows isn’t case sensitive, so it doesn’t matter whether it’s CON, con, or CoN—Windows won’t let you use that name.

You can try it yourself. Try saving a file as “con.txt” or “lpt6.txt” in Notepad. Or try renaming any file to one of these names in File Explorer. Windows just won’t let you do it.

Of course, Windows also restricts file names in other ways. You can’t use various special characters like the following in names, either. Consult Microsoft’s official documentation for more information.

What Happened in 1974, and Why Should We Care?

As @Foone recently explained on Twitter, this issue dates back to 1974. In UNIX, “everything is a file.” (The same is true in UNIX-like operating systems like Linux today.) Hardware devices were represented at special paths like /dev/lp0 for the first printer and /dev/tty for the console.

In 1974, this same concept was added to the CP/M operating system. Unfortunately, CP/M was designed for computers with very little memory and no hard drives. It used multiple disks and no directories, so those special files representing devices effectively appeared everywhere, on every disk.

So, when you were saving a text file, you could tell your text editor to “save” it to the printer device, which would print it. But text editors and other programs like adding file extensions like “.txt”, so CP/M just ignored the file extension for these device files. In other words, if a text editor tries saving a file to the name of the printer device followed by “.txt”, CP/M just assumed it was referring to the printer device and ignored the file extension. Now the feature worked properly in every application—great!

Sure, it’s a dirty hack, but who cares? Well, CP/M caught on. Eventually, PC-DOS came along, and it kept that useful CP/M feature. PC-DOS 2.0 added directories back in 1983, but Microsoft chose to have these device files appear in all directories for compatibility with existing DOS software rather than place them in a special device folder.

Eventually, Windows 95 came along, and it was built on top of DOS. Windows NT wasn’t based on top of DOS, but it did want to be backward compatible with Windows 95 applications. Windows 10 is still based on Windows NT, and it works the same way. The same applies on Windows 7, of course.

Now, it’s over forty years later and we still can’t name files “con.txt” or “aux.mp3” because Windows wants to stay compatible with ancient programs that might be using this feature. It’s a good example of how intensely Microsoft is committed to backwards compatibility.

Update: We’ve been told that CP/M originally required a trailing colon—in other words, rather than “CON”, you had to type “CON:”. Apparently, the problem may have really started in 1981 with the release of MS-DOS and PC-DOS, which removed the colon requirement. In DOS, you could use “CON” instead of “CON:”. So perhaps DOS is more to blame for this than CP/M is.

Source link

More articles

Leave a Reply

Subscribe to our newsletter

To be updated with all the latest news, offers and special announcements.

- Advertisement -

Latest article

iPad, MacBook Models May Sport OLED Display in 2022: Report

Apple is reportedly planning to adopt OLED display technology for some of its upcoming iPad and MacBook models in 2022. The Cupertino company...

Want car insurance that’s easy and costs less? Check out Clearcover

When it comes to car accidents, it isn’t a matter of if, but when. The costs associated with vehicle collisions can be quite high, with...

After ‘Saina’ Poster Goes Viral For Error, Director Amol Gupte Defends The “High Concept Poster”

The first poster of Saina Nehwal's biopic arrived just a few days ago followed by a short teaser. Simply titled Saina,...

NASA Hubble Shares Sparkling Image Of A Spiral Galaxy M96 That’s 35 Million Light Years Away!

The National Aeronautics and Space Administration (NASA) recently shared a bright and sparkling image of a spiral galaxy M96. The image...

YouTube to Lift Ban on Former US Prez Donald Trump’s Channel Only When Risk of Violence Decreases

Alphabet’s YouTube will lift its suspension on former US President Donald Trump’s channel when it determines the risk of real-world violence has decreased,...
- Advertisement -