this post was submitted on 17 Mar 2026
51 points (96.4% liked)
Programmer Humor
30442 readers
2340 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Fun fact: all Windows exe files are also com files. They all have a dos running part, most of which simply prints "this program cannot be run in dos nice" and exits, but some programs do have fully functional dos program as well as the usual windows GUI part.
I actually first thought that was weird and wasteful. Then I remembered that, uh, Commodore 64 often uses a similar thing. Basically, a lot of assembly and compiled languages just put the machine code into the BASIC memory, preceded by a stub BASIC program that's basically just "10 SYS addr" with that address pointing just past the end of the stub program itself. BASIC's LOAD command handles it just fine because program files don't have any header information besides load address. BASIC handles the loaded program just normally because the program has the end token, so as long as you don't modify the BASIC program, it'll be fine.
Luckily the .exe's MZ header is pretty small. But in this case it was necessary: when DOS loads a .com binary, it can't know how much memory it will need, so DOS just gives it all free memory. But then the program can't launch another, because all memory is in use. So that's why I had to add the MZ header which allows specifying the memory needs.
Technically that segment is not a com file. They are MZ exe files. com files have no metadata or header
You could say any arrangement of words or letters about the inner workings of Windows, and I’d probably just take your word for it at this point.