I love that they specify that they're not accepting pull requests.
Even funnier when it's their own platform and it has been missing the feature to disable them for so long afaik
The MS-DOS v1.25 and v2.0 files were originally shared at the Computer History Museum on March 25th, 2014 and are being (re)published in this repo to make them easier to find[.]
In 2014, MS-DOS 1.25 and 2.0 were released under a Microsoft shared-source license (Microsoft Research License) which forbids redistribution
In 2018, both versions were published to GitHub and relicensed as MIT, making them properly open-source
Today, MS-DOS 4.00 was added to that repo, also under MIT.
Ignore them. Send a pull request with the full source of Arch Linux.
Nah, just a giant compiled binary blob. That's what all the cool hackers do these days.
LOL, some of the comments in the source are gold.
https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/ABORT.ASM
Note: We do need to explicitly close FCBs. Reasons are as follows: If we
; are running in the no-sharing no-network environment, we are simulating the
; 2.0 world and thus if the user doesn't close the file, that is his problem
; BUT... the cache remains in a state with garbage that may be reused by the
; next process. We scan the set and blast the ref counts of the FCBs we own.
;
; If sharing is loaded, then the following call to close process will
; correctly close all FCBs. We will then need to walk the list AFTER here.
;
; Finally, the following call to NET_Abort will cause an EOP to be sent to all
; known network resources. These resources are then responsible for cleaning
; up after this process.
;
; Sleazy, eh?~
i remember writing .bat files and pretending they were really fancy update scripts when i was like ten they did nothing but it was still fun :)
Like half of my job is writing .bat files to automate stuff locally and not tell my boss that all I do anymore is double click the right things in the right order...
You can put in a timeout command at the end, and then call the next .bat file.
For example "TIMEOUT /T 60" waits for 60 seconds before resuming, or you can override it by pressing any key.
So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.
This guy is a master bat-er
Next step, bind them to unused keys on your keyboard and press them in the right order
I guess we now have a timeframe in which to expect the release of Windows.
FreeDos is better anyways
I wonder if this is of any use to them or if they're already too far ahead.
To my knowledge, FreeDOS has been a fairly complete implementation of DOS for a very long time, so this is probably not useful to them.
MS-DOS, Source public available on March 25 2014 with MS Research License, released with as Free Software MIT license in 2018, this yer released as Open Source MS-DOS 4.0. Anyway, the Source code was available since 2014, only different licenses since then.
So cool, thanks. As a kid I spent so much time in DEBUG, stepping through DOS's executables, and especially the Interrupt handlers. It's so neat to see the actual source code-- way easier to read and follow. I didn't know it was all written in assembly, from within Debug it sometimes seemed so messy and convoluted that I just assumed more was written in C.
Look at them, embracing open source like this, how wonderful.
I'm sure the only reason why they waited this long is that they needed to make sure it's old enough that the companies they stole code from can't sue.
Can't wait for the OSS community to fork it and build some cool shit on top of this /s
Where is the ctrl+alt+del function defined? I just want to see what made that sequence work. I'd also be interested in where ctrl+break is defined.
Ctrl+alt+delete was a separate interrupt line direct from the keyboard. That is, when you pressed the three keys, the interrupt signal was asserted, causing the CPU to jump to the interrupt service routine, which should be in the source code package.
Woah MIT license. That’s a lot more permissive than I expected.
!remind 10 years when they will release the source code of Windows 3.0 for non-commercial use
(3.11 will take another 10 years)
Would this have Bill’s code in it ? Or was he off the shop floor by then ??
https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/CTRLC.ASM
; The user has returned to us.
So ominous.
; Well... time to abort the user.
Goodbye
6.22 or foff
How much you wanna bet that a select few turbo-nerds are racing to debug it or something.
Is this useful for hobbyists besides poking around and seeking the design philosophy at work back then?
Like would there be any advantage or reason to implement this in a home project? For example maybe that it's lightweight and has some rare compatibility or anything like that?
I think its interesting from a historical perspective.
I imagine people will examine the code, find easter eggs, bugs, unknown features, amusing comments etc.
I look forward to seeing what is found.
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Community icon from opensource.org, but we are not affiliated with them.