dosbox-staging VS wine-staging

I believe it is a bug in the the emulator's implementation of COMMAND.COM. Often, these DOS "emulators" re-implement the standard commands of DOS, including the shell[1]. This is in addition to emulating weird 16-bit environment stuff and the BIOS.

The bug lies in any C program using stdio that assumes it's fine to do `fread` followed immediately by `fwrite`. The spec forbids this.

To make matters more confusing, this behavior does _not_ seems to be in modern libc implementations. Or at least, it works on my machine.

The original COMMAND.COM from MS-DOS probably did not have this problem, since at least in some versions it was written in assembly[2].

[1] Here's DOSBox, for example: https://github.com/dosbox-staging/dosbox-staging/blob/main/s...

[2] MS-DOS 4.0: https://github.com/microsoft/MS-DOS/tree/main/v4.0/src/CMD/C...

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/

https://dosbox-staging.github.io/ Latest Staging version is 0.80.

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.

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!

Any crashes and freezes you experience -> please report them in the bug tracker: https://github.com/dosbox-staging/dosbox-staging/issues

In DOSBox Staging you can type imgmount /? and it will show you some usage examples, including the one with multiple floppies :).

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.

Now you can't just go from vanilla WINE to WINE Staging by installing stuff. You would have to patch the source code of WINE with all those patches: https://github.com/wine-staging/wine-staging/tree/master/patches and then compile it yourself.

Read this for more info: https://wiki.winehq.org/Wine-Staging

I've got the source from here and applied the patch as it says here

vkd3d-proton: - occasional upstream pending patches wine: - uses proton's bleeding edge wine base: https://github.com/ValveSoftware/wine/tree/experimental-wine-bleeding-edge-7.0-20190-20220716-pe79367-w7a9d8c-d5aa943-v5b7313 - adds wine-staging on top of it: https://github.com/wine-staging/wine-staging/tree/master/patches - adds FSR patches on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/48-proton-fshack\_amd\_fsr.patch - adds a handful of other game fixes on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/e01207aafe539d8d3ed49301665da717340e4c1d/patches/protonprep-valve-staging.sh#L295 - removes the proton-specific steamclient changes so that it works as a normal wine build: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/0001-De-steamify-proton-s-WINE-so-it-can-be-used-as-a-sta.patch ffmpeg: - we enable some codecs not available in steam's ffmpeg gstreamer: - we enable some codecs not available in steam's gstreamer protonfixes: - these are python scripts that automate installing various winetricks and/or other per-game tweaks. this achieves the same thing most lutris installers perform. -------------------------

USE "HOMEBREW" https://brew.sh/ Or "MACPORTS" https://www.macports.org/ As subsystem or wrapper to help wine to be stable. I trying homebrew for a week right now with many versions of wine ( stable & bev , etc The fastest WINE wrapper updated is WINE STAGING. 🍷 https://github.com/wine-staging/wine-staging

Install Wine Staging and winetricks. Then create a new 64 bit prefix. You can run winetricks for this.

It's possible there's blockers for it not being updated, but you can also get a general idea as to how long updates on Fedora's end takes by comparing the dates on that site to the releases on Staging's GitHub.

These patches are missing: https://github.com/wine-staging/wine-staging/tree/master/patches/winepulse-PulseAudio_Support

FFXI should run fine on Steam Deck as it's reported as Gold in ProtonDB but, as I'm used to play the game on Windows, it can be fully enhanced/HD remastered with a lot of graphical and QOL community mods (Ref. here) which are all based on Windower - This is probably a core issue for the SD trying to run this third party/"dll injector". After having a chat with Windower support on Discord, I found out that the main issue is this commit in Wine. Now it would be great to know if this commit will be included in the Proton build used by the SD - Keeping it short: Proton is basically Valve's implementation of Wine. I'm definitely going to try this as soon as I have my hands on the SD as FFXI is still such a great/unique MMORPG and I would also suggest to check it out to everyone having a few friends to bring in.