Honestly had better luck with DOSBOX-X.
For one, it explicitly calls itself a “subset”; a subset is not the whole set.
If we don’t want to go just off the pedantics of language though, then here’s the thing: it was forked a very long time ago, and both have diverged significantly, I think. It’s a bit like saying Blink (the rendering engine of Chromium) is WebKit; sure, Blink is a fork of WebKit, but the two are very different now.
Technically not the Linux kernel.
Just because they existed during the Linux era doesn’t mean they ran Linux; Torvalds was writing for the 386 from the beginning, and Linux has never been written for anything below 32-bit.
Now, it certainly has RAN on that hardware through emulation, such as on a 4 bit Intel 4004, but only for the heck of it.
It is Super Mario BROTHERS 3, petaQ! For this, you shall experience much bIj in ghe’tor!
Excuse me, but you mean 24th century weed.
I’m pretty sure 23rd century weed was responsible for the TOS episode “The Alternative Factor” and that one CGI sequence in the one with the whales.
"Oh no! It's another Enterprise!"
All aboard the obscure Beta canon Weyoun variant train:
Rubbing alcohol and a microfiber cloth.
Also, I feel like I’ve had good luck with k3b, though mainly for CDs.
As for drives, as others have said, USB ones tend to be janky; go for an internal. I like my LG WH16NS40 Blu-Ray drive.
If it’s a desktop, it should be easy to hook up with SATA, though if you have a newer case, you might need to dangle a cable out the side like I do.
If you have a laptop, though, you’ll probably need a USB adapter, though there might be a hack using an M.2 slot to hook up an SATA PCI-E card.
If you don’t like bog standard Debian, you might really like Debian Testing.
It allows you to get decently new packages; I’d say typical lag is one week to a couple months depending on the popularity and/or complexity of the project.
I’ve been using it on my desktop for over three years just fine. It’s been quite stable while still getting new software versions in a mostly timely fashion.
Do note though that Testing means Testing; it’s not really concerned with being a rolling release distro, but with preparing for the next release, so there’s a few quirks:
- Sometimes, a package you’re using gets removed while its dependencies undergo a transition, forcing you to use the Flatpak.
- When a new stable release starts to get close (usually 6 months), they’ll start what’s called freezes, where they let in progressively less changes until release, after which things start speeding up again.
- As a general annoyance of anything rolling release-esque, software behavior may change over time, meaning a previously good config can suddenly break, and you have to fix it.
Personally, I’ve grown tired of Debian Testing and rolling release in general; while I still using Testing on my desktop, I’ve thrown Debian Stable on most things I’ve owned since then, and if I really need a newer version of software, I’ll just install the Flatpak or use a container.
To clarify, what I mean is WebKit continued while Blink became its own thing. Factually, Blink is not WebKit anymore.
Replace “WebKit” with Linux and Blink with ELKS.