An error that persisted in Windows since 1974

It is now the year 201? and this message is a mistake that has persisted since 1974. The restriction, which is found even in the latest Windows 1? has appeared before "STAR WARS". The bug is as old as Watergate.
 
 
An error that persisted in Windows since 1974  
 
In those days, barcodes were only invented, only one telephone company worked in America, Ted Bundy was still running free, and Babe Ruth's home-run record was in his last days.
 
provides a complete list of Prohibited names: CON, PRN, AUX, NUL, COM? COM? COM? COM? ​​COM? COM? COM? COM? COM? LPT? LPT? LPT? LPT? LPT? LPT? LPT? LPT? LPT9.
 
 
For even more buzz, an attempt to access C: concon (or C: auxaux) on win95 will instantly show a blue screen. It was fun even in 199? because the bug is 21 years old! Imagine that some kind of error persists for so long?
 
 
3r3142.
 
 
3r3147.
 
 
Bonus: here is a photo of Tim Paterson on VCF: W in August of this year, he tells about the history of DOS.
 
 
 
 
If you're wondering how I got a “forbidden” file that cannot be copied, then I will say. These special device names are implemented at the OS level, and not at the file system level. Thus, these are perfectly valid NTFS file names, and I used an NTFS disk under Linux.
 
 
It seems that OS /2 also did not implement these special names, because one of the disks from IBM has AUX.H files in the OpenGL bundle.
 
 
 
 
So today I tried to make a backup copy of this NTFS disk on the main PC and OP-PA, IT IS IMPOSSIBLE TO COPY ALL FILES BECAUSE OF BAGA OLDER THAN THE MOST READERS OF THIS ARTICLE.
 
 
A few notes:
 
 
1. CP /M did not actually use these special names as easily as I described. It seems that I either did not know, or forgot about this fact. In fact, they should be followed by a colon, like disk names, that is, PRN: - this is a printer, PRN - no.
 
 
2. CP /M did not implement them at the OS level, as in DOS! They were simply included in the PIP, file copy command. Therefore, the DOS saving trick to the PRN.TXT file with automatic printing did not work there. I did not mean that CP /M did that, but only DOS, but apparently it was not clearly expressed.
 
 
3. In PC DOS 1.? there really were no redirects or a pipeline, so you cannot make such a redirect as I suggested. I forgot about it. They were added to PC DOS 2.0 in 1983. Although PC DOS 1.0 supported copying to /from special files, therefore the general thesis is correct, even if the example is unsuccessful.
 
 
In any case, thanks for the feedback on this article! I didn’t expect it to explode like that, I just sprinkled a couple of paragraphs when I came home very tired and saw an error message because of a 44-year-old bug.
 
 
And if that, I was not going to shout "Windows SUCKS". Backward compatibility is generally a good thing. In fact, I would like more backward compatibility, not less.
 
 
But I was just struck by this bug from antiquity, which popped up while copying from USB 3.0 SSD to another SSD in Windows 10.
 
 
It's as if you live on a space station - and then a horse appears.
 
tl; dr:
 
 
Your browser does not support HTML5 video.
+ 0 -

Add comment