Back when this mistake was made, There was only one Phone Company, because they hadn't been broken up yet. Ted Bundy was still on the loose. Babe Ruth's home run record was about to fall.
It is 2018 and this error message is a mistake from 1974.
This limitation, which is still found in the very latest Windows 10, dates back to BEFORE STAR WARS. This bug is as old as Watergate.
Back when this mistake was made, There was only one Phone Company, because they hadn't been broken up yet. Ted Bundy was still on the loose. Babe Ruth's home run record was about to fall.
You could do neat things with it like copy data off the serial port into a text file, or print a textfile right from the command line!
You can get infinite zeros from /dev/zero, random bytes from /dev/random, etc!
So directories? you don't need 'em. Instead of directories, you just use different disks.
So they're just "everywhere", effectively.
So if you have FOO.TXT and need to print it, you can do "PIP LST:=FOO.TXT" which copies foo.txt to the "file" LST, which is the printer.
but what about extensions? Here's the problem: programs like to name their files with the right extension.
but the program might try to put .TXT on the end of your filename! LST.TXT isn't the printer, right?
Eh. It's a hack, but it works, and this is just on some little microcomputers with 4k of ram, who cares?
But it was big, so naturally IBM wanted it for some "PC" project they were doing in early 1980
MS purchased Tim Paterson's project and developed it into PC-DOS (which later became MS-DOS, if you're not aware)
It was definitely inspired by CP/M, in a lot of ways.
So QDOS and PC-DOS 1.0 have AUX, PRN, CON, LPT, etc, too!
You need them to keep your massive 10mb hard drive organized, obviously!
with directories, Microsoft could now make a C:\DEV folder... but they didn't.
Special files are in EVERY DIRECTORY with EVERY EXTENSION.
So your "DIR > LPT" trick to print the directory listing doesn't break because you're in C:\DOS instead of A:\
And when Windows 95 was released, it was built on top of DOS. So it naturally inherited this behavior. (Windows 1/2/3 similarly did, but Win95 was much more an OS than they were)
But Windows NT wanted compatibility with DOS/Windows programs. And XP merged the two lines.
So these special files still work, FORTY FOUR FUCKING YEARS LATER
aux.txt
prn.txt
it'll tell you NOPE
CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9
https://t.co/1eYQVBKO65
These special-device names are implemented at the OS level, rather than the filesystem level. So they're perfectly valid NTFS filenames, and I was using an NTFS drive in linux.
A couple follow ups:
1. The CP/M inventor's name is "Gary Kildall", not "Gary Kiddal".
Sorry, I posted this at 5am after being in the hospital for like... 8 hours?
It actually required them to be followed by a colon, as if they were a drive name.
So PRN: is the printer, PRN is not.
I didn't mean to imply CP/M did, just DOS, but I don't think I made this clear
PC DOS 1 did support copying to/from special files though, so my general point was correct, even if my example was confusing
It's like you're living on a space station and get trampled by a horse.
More from foone
More from Tech
Ok. Let's talk about why Xbox decided to announce that it would double the price of Xbox Live Gold (12m period) and then reversed that decision less than 24 hours later after strong backlash from fans.
Quick thread on the topic from me below:
If you've followed me in the past you know that I've talked a lot about Xbox is moving beyond the console and has a goal to offer multiple entry points into its ecosystem, with Game Pass being the main entry point into its software and services
This strategy makes a lot of sense on paper, but is proving difficult for Microsoft to execute in the short term.
The aim is to scale Game Pass as a service to reach the entire gaming audience via multiple console offerings, but also beyond console via PC & Mobile (Cloud) etc.
It's also why Xbox has plans to extend Game Pass + xCloud to iOS, Windows and other devices (Smart TV's) in the future.
Its investment in studios and IP aims to increase the value prop of Game Pass, with multiple AAA titles available on the service day 1.
All for $15pm.
Game Pass has already grown to 15 million subscribers, but it's worth noting that the majority of these subs are also Xbox console players.
The goal of reaching the broader gaming audience beyond console will take some time to fully execute for a number of reasons:
Quick thread on the topic from me below:
If you've followed me in the past you know that I've talked a lot about Xbox is moving beyond the console and has a goal to offer multiple entry points into its ecosystem, with Game Pass being the main entry point into its software and services
Xbox has two goals:
— Daniel Ahmad (@ZhugeEX) July 23, 2020
1. Remove barriers to entry in the hardware space
2. Remove barriers to entry in the software and services space.
With the overall goal to grow the number of players in the Xbox ecosystem through multiple entry points and a range of connected services.
This strategy makes a lot of sense on paper, but is proving difficult for Microsoft to execute in the short term.
The aim is to scale Game Pass as a service to reach the entire gaming audience via multiple console offerings, but also beyond console via PC & Mobile (Cloud) etc.
It's also why Xbox has plans to extend Game Pass + xCloud to iOS, Windows and other devices (Smart TV's) in the future.
Its investment in studios and IP aims to increase the value prop of Game Pass, with multiple AAA titles available on the service day 1.
All for $15pm.
Game Pass has already grown to 15 million subscribers, but it's worth noting that the majority of these subs are also Xbox console players.
The goal of reaching the broader gaming audience beyond console will take some time to fully execute for a number of reasons:
You May Also Like
Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇
It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details): https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha
I've read it so you needn't!
Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.
The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.
Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details): https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha
I've read it so you needn't!
Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.
The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.
Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
