MS-DOS
virtualagc
MS-DOS | virtualagc | |
---|---|---|
59 | 13 | |
15,623 | 2,490 | |
- | 1.0% | |
0.0 | 8.9 | |
over 4 years ago | 2 days ago | |
Assembly | Assembly | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MS-DOS
- MS-DOS v1.25, v2.0, v4.0 Source Code
-
Open Sourcing DOS 4
This 4.0 code contains references to 4.00, though: https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/BOOT/...
- DOS 4.0 Source Code Released Under MIT License
- Why Does Windows Use Backslash as Path Separator?
-
ST-DOS
I recently stumbled across the MS-DOS 1.25 and 2.0 source code [1].
[1] https://github.com/microsoft/MS-DOS
-
The History of Xenix
“Despite this reduction in scope for MS-DOS 2.0, it did carry many bits of XENIX. The system adopted I/O redirection via less-than and greater-than symbols, piping, a hierarchical directory tree, file handles […]”
The source code for MSDOS 2 is available and the file descriptor stuff appears to be in https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/... and XENIX2.ASM. It stands in contrast to the File Control Block API which MSDOS 1 (née 86-DOS) modeled after CP/M’s API.
- MS-DOS v1.25 and v2.0 is now open-source (2014)
- MS-DOS v1.25 and v2.0 is now open-source
-
MS-DOS is now open-sourced
Asynchronous I/O figures in prominently in Windows NT. I was really surprised to see[0]:
Each driver in the chain defines two entry points; the strategy routine and the interrupt routine. The 2.0 DOS does not really make use of two entry points (it simply calls strategy, then immediately calls interrupt). This dual entry point scheme is designed to facilitate future multi-tasking versions of MS-DOS. In multi-tasking environments I/O must be asynchronous, to accomplish this the strategy routine will be called to queue (internally) a request and return quickly. It is then the responsibility of the interrupt routine to perform the actual I/O at interrupt time by picking requests off the internal queue (set up by the strategy routine), and process them. When a request is complete, it is flagged as "done" by the interrupt routine. The DOS periodically scans the list of requests looking for ones flagged as done, and "wakes up" the process waiting for the completion of the request.
I didn't realize that kind of forwarding-looking perspective was going into the design of MS-DOS.
[0] https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/...
-
Exploring the Internals of Linux v0.01
>Any others I'm missing?
I would suggest MS-DOS: https://github.com/microsoft/MS-DOS
virtualagc
-
Mistral CEO confirms 'leak' of new open source AI model nearing GPT4 performance
I don't think that's a great example.
For instance, I can step through and even modify that code using tooling like AGC emulators like this one http://www.ibiblio.org/apollo/#gsc.tab=0
What makes it open source is access to the same level of source access that the original developers worked in.
That's what's missing here. Mistral's engineers do not simply open this binary in their editor to do their job.
- Exploring the Internals of Linux v0.01
-
Apollo 14 LMAE specs/exit velocity calculation
Glad you're enjoying the videos! I'm Mike from them. :) The Apollo 14 code I linked above was reconstructed in the same way as Luminary 69/2, but the process was far, far too involved for a video. Like I said above, I probably won't be much help with math, but I'd be more than happy to assist with finding documentation or navigating AGC code whenever you want!
-
Apollo 11 was FAKE. What is the best evidence to support this?
The fact that all the information about the computer and software is public and you can verify it yourself like thousands of people have. https://www.ibiblio.org/apollo/
-
TIL NASA landed on the moon using a computer with just 4KB of RAM
If you’re curious about the the technical specs of the AGC check out Ron Burkey’s website, it’s even got the source code for you to see for yourself: https://www.ibiblio.org/apollo/
- Ask HN: What weird technical scene are you fond/part of?
- The Apollo On-Board Computers
-
What is the evidence for the moon landing being fake?
Of course you should be able to tell us because all the hardware architecture and software can be found here. So you must have fully reviewed it and located the issues. Right? Than please point out where the error is.
- How did a Space Rocket take off again from the surface of Moon?
-
Exploring the software that flies SpaceX rockets and starships
It had manually encoded ROM in the form of "core rope memory", which is pretty wacky, but it was a digital computer. In fact, it was the first IC computer.
You can learn way too much about it and even operate (a simulation of) one here: http://www.ibiblio.org/apollo/
What are some alternatives?
86Box - Emulator of x86-based machines based on PCem.
ArduinoCore-avr - The Official Arduino AVR core
dosbox-x - DOSBox-X fork of the DOSBox project
rvc - A 32-bit RISC-V emulator in a shader (and C)
Chicago95 - A rendition of everyone's favorite 1995 Microsoft operating system for Linux.
new-wave - Stack Computer Bytecode Interpreters: The New Wave
qubes-issues - The Qubes OS Project issue tracker
CAM6 - Cellular Automata Machine (CAM6) Simulator
emu2 - Simple x86 and DOS emulator for the Linux terminal.
CygnusX1 - A thrust-vectoring model rocket flight computer. Comes with all you need to keep your rocket pointing up.
open-watcom-v2 - Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
SVM-Face-and-Object-Detection-Shader - SVM using HOG descriptors implemented in fragment shaders