If you're trying to write a utility using Open Watcom C/C++ that works both on DOS and on the Linux machine you normally cross-compile from, and you're getting mysterious misbehaviours on one platform, check your INCLUDE path.
Having INCLUDE=$WATCOM/lh when cross-building for DOS or having INCLUDE=$WATCOM/h when building natively for Linux can result in successfull builds with confusing runtime misbehaviours.
Sorry I went silent. I've been too busy to even check Mastodon, let alone post on it.
Today, however, I self-nerd-sniped and implemented a one-click aspect ratio correction userscript for 320x200 screenshots of DOS games on MobyGames:
(See https://www.gamasutra.com/blogs/FelipePepe/20150423/241730/No_MSDOS_games_werent_widescreen_Tips_on_correcting_aspect_ratio.php for an explanation of why it's necessary.)
I wanted to start off my #dos tweets recap with the link I found for IBM's CUA keybindings reference, but, sadly, it's now dead.
If anyone wants to try to track it down, this was the URL for the relevant section in one of the versions of IBM's reference:
Failing that, I've since picked up a used copy of http://www.worldcat.org/oclc/931408154 so maybe I'll try to find time to transcribe the reference tables listed as Figures 171 and 172 (Keyboard Functions, p. 315-322), (Keys to Functions, p. 319-322), Figures 175-185 (Mnemonic Assignments for ..., p. 345-349), and Figure 200 (Shortcut Key Assignments, p. 451-452).
(That said, if you can find a copy of the book, pick it up. While it's primarily intended for OS/2, it's got a *lot* of nifty stuff useful for DOS TUIs, including "Appendix E. Translated Terms"... charts translating various English menu/button labels like "Redo" into 16 different languages.)
Linux user, open-source enthusiast, science buff, and retro-hobbyist who occasionally reviews fanfiction.
QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.
No hate, No censorship. Be kind, be respectful
We federate with all servers: we don't block any servers.