anyone tried opening the magic file "con" from MS DOS Edit?

I was hoping for an editor but it turns out instead it happily opens it but then hangs forever

weird punnet square of results:

EDIT hangs if you open "CON", but errors if you try "C:\CON\CON"
Win95 errors if you try to open "CON", but crashes if you try "C:\CON\CON"

@foone

Wasn't there also once a bug in Win7 or 8 that caused it to hang in kernelspace and bluescreen with these once?

@agowa338 Win95 had that bug, yeah

@foone No, I mean something way more recent. Cause that together with early days Minecrafrt modding (where you had to unzip the jar file and then at some version there was a file named "AUX" in it)

where when I learned about these special filenames for the first time. And I didn't play minecraft on anything less recent than win7, so...

@agowa338 oh that's not a bug, that's an intentional design decision. windows reserves a bunch of filenames and it's a pain

the bug where this crashed the machine hasn't been there since windows 95, that's a separate issue

@foone @agowa338 CON means /dev/ttyS0
There is also NUL and LPT.

@f4grx @agowa338 yeah!

I made a list of the reserved names, as a git repo, so that windows users can not check it out

https://github.com/foone/forbidden-files

GitHub - foone/forbidden-files: Files that cannot be created on windows

Files that cannot be created on windows. Contribute to foone/forbidden-files development by creating an account on GitHub.

GitHub
@foone @agowa338 hahaha evil

@f4grx @foone

You're missing the ones with the superscript number btw.

@agowa338 @f4grx mm? I'm not seeing that, which ones?

@foone @f4grx

COM¹, COM², COM³, LPT¹, LPT², and LPT³

See the note on the microsoft naming a file docs page I linked to in my other post.

It's another funny windows quirk.

@foone @f4grx

> Windows recognizes the 8-bit ISO/IEC 8859-1 superscript digits ¹, ², and ³ as digits and treats them as valid parts of COM# and LPT# device names, making them reserved in every directory. For example, echo test > COM¹ fails to create a file.

Source: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file

Naming Files, Paths, and Namespaces - Win32 apps

The file systems supported by Windows use the concept of files and directories to access data stored on a disk or device.