doshea wrote on 2023-07-09, 06:07:
As for DOS, a comment on https://hackaday.com/2020/02/09/c-the-languag … s-3-11-and-dos/ suggested that the .NET code wasn't really being translated to native DOS code but rather something which required https://github.com/Baron-von-Riedesel/Dos64-stub ('small stub that allows to run "bare" 64-bit PE binaries in DOS', I guess it's like HX DOS Extender).
A stub? I see parallels to OS/2 and "Family Mode" programs using "Family API".
These essentially were OS/2 programs with a built-in OS/2 runtime.
They could natively under OS/2, but also more or less under plain DOS.
https://www.landley.net/history/mirror/os2/hi … s213/index.html
That reminds me a bit of Windows 3.1/DOS hybrid EXEs (Windows Setup) or Carbon applications on Power PC Macs, too.
Edit: If you enjoy doing a bit of Windows 3.x development, please have a look at MS Quick C for Windows 1.0. .
It's a cute little compiler that runs completely on Windows 3.x and doesn't require DOS environment variables to be set up etc.
If you have tinkered with DOS-based 16-Bit Windows SDK before, you may remember how messy this can be at times.
Quick C also can create similar pseudo-textmode applications like Turbo Pascal for Windows can.
They helped at making DOS-based source code run on Windows without much alteration.
To do so, they simulated MS-DOS prompt (inverse colour).
The resulting programs are essentially MS-DOS look-alikes running on Windows 3.x.
Edit: It just comes to mind because the C programming handbook my father has in his book shelve mentioed MS Quick C for Windows.
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//