ntvdmx64
mustang
ntvdmx64 | mustang | |
---|---|---|
13 | 20 | |
758 | 790 | |
- | - | |
5.1 | 7.5 | |
11 days ago | 9 days ago | |
C | Rust | |
- | 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.
ntvdmx64
- Microsoft rewriting core Windows libraries in Rust
-
Revisiting Borland Turbo C/C++, A Great IDE back in the 90s – CodeProject
The link in the post to NTVDMx64 at Columbia seems to be broken, but the associated GitHub project appears to be at https://github.com/leecher1337/ntvdmx64
"What is it?
- Playing an old game with a 3060, this error made me laugh
-
Handling 16-bit Windows applications
ntvdmx64 might also be an option.
-
Alt-Enter Doesn't Window DOS Graphics in XP (Used to Work in NT and W2K) (2006)
People who absolutely need to run 16-bit DOS apps on x64 Windows can use NTVDMx64: https://github.com/leecher1337/ntvdmx64
-
First Casio wrist camera. Any chance this can connect to modern computers or devices?
If it's Windows, you can probably just use an external CD drive or look for an ISO copy online. For the most part, old Windows software still works with modern Windows (REALLY old software will be 16-bit and will need NTVDMx64 to work on 64-bit). Though I'm not sure about the driver itself. If it's a generic protocol, it might just be plug-and-play
-
Help getting NTVDMx64 installed
I've seen NTVDMx64 mentioned in the BBS community, as it's supposed to install a 16-bit NTVDM on 64-bit editions of Windows. I've been trying to get this installed on my main desktop PC at home (running Windows 11 64-bit), but I always run into some errors trying to install it, and it doesn't seem to install completely (I am unable to run 16-bit DOS programs).
-
I'm trying to set up my own bbs server
Looks like the NTVDMX64 link was taken down from the columbia.edu website and is now just at https://github.com/leecher1337/ntvdmx64
-
Not Tech Savvy- Seeking insight on why windows is a better operating system then Linux
Well... Windows is always the best option because of its backwards compatibility. Even with some small apps (like NTVDMx64, or similar) you can even make Win10/Win11 run software made to run in 16-bit (or, Windows 3.1 or Win95). I've had to do that for some edutainment software for my son.
-
An actual good thing about Windows 11 rollout: 64-bit only
If you really want DOS apps on 64-bit there's https://github.com/leecher1337/ntvdmx64 or use a flavour of DOSBox.
mustang
-
OpenBSD 7.5 Released
It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.
Found this as well: https://github.com/sunfishcode/mustang
Some discussion here: https://github.com/bytecodealliance/rustix/issues/76
- Mustang
-
Rust criticism from a Rustacean
On Linux there has been some attempts to get exactly this solutions, most notibly https://github.com/sunfishcode/mustang but the topic did not seem to fetch a prominent position on the supported feature list.
-
Microsoft rewriting core Windows libraries in Rust
For Linux, Mustang already exists because Linux has a stable syscall API
- Mustang: Rust target with std and no linking to a Libc
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
Why bother with a libc at all, when you can skip it entirely on Linux!
-
Why so few, if any, pure Rust apps?
Mustang is a project which is able to run some non-trivial programs written in Rust, such as ripgrep, without using any libc, on Linux.
-
Can rust be entirely written in rust and drop C usage in its code base ?
Mustang is one way to take care of the tiny amount of "C" that runs before main().
-
How do I use Zig as Rust's Standard C Library?
This is more a Rust question than a Zig question. In Rust, the choice of a specific libc (or to not use a libc) is part of the "target", for example many hardware platforms have gnu/musl/none targets. See also relibc or mustang for pure-rust alternatives. Each libc alternative require some work to integrate into Rust.
-
memmapix: A pure Rust library for cross-platform memory mapped IO, which replace libc with rustix.
There's a separate project for that, called Mustang. It's built on top of rustix and provides all those things. It's not super mature yet, but it is able to run ripgrep by itself: https://github.com/sunfishcode/mustang
What are some alternatives?
winevdm - 16-bit Windows (Windows 1.x, 2.x, 3.0, 3.1, etc.) on 64-bit Windows
ziglibc
OTVDM - Windows/DOS emulator -> https://github.com/otya128/winevdm
relibc - Mirror of https://gitlab.redox-os.org/redox-os/relibc
vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.
liblinux - Linux system calls.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
rustix - Safe Rust bindings to POSIX-ish APIs
winxpgames
jython3 - A sandboxed attempt at v3 (not maintained)
Windows UI Library - Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications
libc - Raw bindings to platform APIs for Rust