This is nice, then you can make your own "upgrade/better version" or what ever with it?
Although MS indeed opened the source, their license is very far from being an open source license. For example their license prohibits redistribution of the source or derivative works based on it.
WARNING: Do not download or read the Microsoft DOS source if you are working or planning to work on other projects (be that open source projects, or something you do for profit, or at work) that might potentially use any knowledge about DOS internals (for example developing a device driver, or a FAT filesytem driver). Potentially having access to the DOS code can cause IP contamination issues with all kind of legal consequences.
Hasn't enough been published already about DOS internals--even by Microsoft itself? It's not rocket science. And the source for 6.0 has been kicking around on the web for several years, as well as bits of 2K.
Besides, there's always FreeDOS if you want some source to look at...
It would have been more interesting to publish the code for Word for DOS 1.00 from 1983, but then they would have to explain this:
Or other dirty things they may have done at the time.
Right, not a rocket science. Published documentation/books is one thing, published source is another. Usually there is no problem with re-using examples from books/documentation in your code, but reusing somebody else's code in yours is a potential legal trouble.
Also Microsoft somehow managed to get various companies to pay royalties for using FAT. And we also had SCO vs. IBM case regarding Linux contamination...
That message appears if it thinks it detects a debugger. Which meant some systems with special or development software would always get that message, even from a genuine original disk. However, it doesn't actually erase anything. This anti-debugging feature was also in some of their other products at the time.Interesting - is that a self destruct? Never knew about that one. Although presumably this only occurred on a copy or hacked disk so its not like it is a big deal as the original disk would be unaffected.
That message appears if it thinks it detects a debugger. Which meant some systems with special or development software would always get that message, even from a genuine original disk. However, it doesn't actually erase anything. This anti-debugging feature was also in some of their other products at the time.
But if they had the audacity to put something like that in there, then who knows what else is underneath the hood?