its
MS-DOS
its | MS-DOS | |
---|---|---|
35 | 59 | |
812 | 15,623 | |
1.2% | - | |
8.7 | 0.0 | |
6 days ago | over 4 years 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.
its
-
Integral Calculator
Compile ITS and just run :macsyma at the DDT prompt (shell/debugger) from ITS:
https://github.com/pdp-10/its
The syntax it's the same, I even made a plot and 'printed' into the host from an ARDS output from the plot command, by converting the file into PPM->PNG or PPM->PDF.
- The Magic Switch – Modern Update
-
Research Unix Sixth Edition (WASM)
ITS didn't really have password control, one was technically added but IIRC it was a fig leaf on some requirement from outside MIT. The user accounts were there mostly to inform others who was logged on and who owned what process.
You could login either using terminal through ARPAnet dial-in support, or later over network, and over time there was added a more concrete "tourist" policy.
DonHopkins seems to have an interesting writeup https://donhopkins.medium.com/mit-ai-lab-tourist-policy-f73b...
and of course there's PDP-10 org and its gather docs on github: https://github.com/PDP-10/its
-
PDP-10 Incompatible Timesharing System emulator
Terry and SHRDLU at 8:23 here: https://archive.org/details/what-about-tomorrow-on-the-side-...
See this for some more information: https://github.com/PDP-10/its/issues/425#issuecomment-145588...
-
So that's where failed print jobs go!
The Magic Switch (in reference to the More Magic, above)
-
Original PDP-10 Zork now rebuilt with MDL compiler
Oops, URL should be https://github.com/PDP-10/its/pull/2150
-
Zork compiled from MDL source code
For more info, see https://github.com/PDP-10/its/pull/2150
- 1981 mainframe Zork built from MDL source code
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
What are some alternatives?
vmtouch - Portable file system cache diagnostics and control
86Box - Emulator of x86-based machines based on PCem.
sims - Burroughs B5500, ICL1900, SEL32, IBM 360/370, IBM 7000 and DEC PDP10 KA10/KI10/KL10/KS10, PDP6 simulators for SimH
dosbox-x - DOSBox-X fork of the DOSBox project
a2d - Disassembly of the Apple II Desktop - ProDOS GUI
Chicago95 - A rendition of everyone's favorite 1995 Microsoft operating system for Linux.
tenex - BBN's PDP-10 operating system
qubes-issues - The Qubes OS Project issue tracker
tashtalk - An interface for Apple's LocalTalk networking protocol.
emu2 - Simple x86 and DOS emulator for the Linux terminal.
PC-LISP - Franz Lisp dialect Lisp system
open-watcom-v2 - Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.