MS-DOS
dosbox-staging
MS-DOS | dosbox-staging | |
---|---|---|
59 | 105 | |
15,623 | 1,174 | |
- | 1.6% | |
0.0 | 9.9 | |
over 4 years ago | 4 days ago | |
Assembly | C++ | |
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
dosbox-staging
-
Sony FW900 Widescreen CRT Trinitron
DOSBox Staging has the best CRT emulation I've seen. It really feels like going back to a VGA monitor.
See the screenshots on https://dosbox-staging.github.io/
-
How to map joystick with more than 2 axis?
https://dosbox-staging.github.io/ Latest Staging version is 0.80.
-
What is the best solution to play mid to late '90s games on modern hardware and Windows 11?
Anyhow whioch dosbox? Well there were non release version somewhere on t he stage but it got fairly bad and https://dosbox-staging.github.io/ is probbaly a better choice.
- Where is Lemmings? Was incredibly surprised not to find it on GOG recently
-
How in the world do I change the keys on the DOSBOX Duke Nukem?? And also the screen size.
You may also want to consider alternatives, such as DOSBox Staging, DOSBox Enhanced Community Edition, or DOSBox-X.. or if you're looking for a more user friendly experience, you can also try the eDuke32, Raze, or JFDuke3D community ports instead of messing around with DOS settings. Hope this helps!
-
Dosbox X slower/less responsive then Dosbox 0.74 at basically same settings
Any crashes and freezes you experience -> please report them in the bug tracker: https://github.com/dosbox-staging/dosbox-staging/issues
-
When installing a game and it prompts you to insert disk 2, what do I do?
In DOSBox Staging you can type imgmount /? and it will show you some usage examples, including the one with multiple floppies :).
-
Do yall have recommendations for games on gog?
The version of DOSbox the above games come with is very old, so you may want to look into something like https://dosbox-staging.github.io/, which will run those games much better on newer hardware.
- DOSBox Staging is going to drop pixel-perfect scaling as a feature
-
Ayuda
Lo puedes jugar emulando DOS en DOSBox (recomiendo el "fork" DOSBox Staging) o a través de un source port llamado Commander Genius, que es más fácil de usar y tiene algunas facilidades para la modernidad.
What are some alternatives?
86Box - Emulator of x86-based machines based on PCem.
dosbox-x - DOSBox-X fork of the DOSBox project
dosbox-pure - DOSBox Pure is a new fork of DOSBox built for RetroArch/Libretro aiming for simplicity and ease of use.
Chicago95 - A rendition of everyone's favorite 1995 Microsoft operating system for Linux.
daggerfall-unity - Open source recreation of Daggerfall in the Unity engine
qubes-issues - The Qubes OS Project issue tracker
em-dosbox - An Emscripten port of DOSBox
emu2 - Simple x86 and DOS emulator for the Linux terminal.
boxtron - Steam Play compatibility tool to run DOS games using native Linux DOSBox
open-watcom-v2 - Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
wine-staging - Staging repository for Wine; mirror of https://gitlab.winehq.org/wine/wine-staging - Bugtracker and Patches: https://bugs.winehq.org/