3 ms·
> Also old software sometimes tends to include 16bit components that do not work yet with ReactOS. Possibly some "new" software too? A few months ago on HN the
by smitherfield 9y ago
> Also old software sometimes tends to include 16bit components that do not work yet with ReactOS.
Possibly some "new" software too? A few months ago on HN there was a thread about the "age" of various software, someone had mentioned that Visual C++ traces its lineage back to 1983's Microsoft C (written in pre-ANSI C and 16-bit x86 assembly for DOS), and I said I imagine they must've thrown that code out when rewriting it in C++ for Win32, but then someone from the VC++ team corrected me: a lot of that code is still in there.
Of course, 64-bit Windows doesn't support 16-bit programs, so I'm not sure if those parts are only still present on builds for 32-bit Windows, or if they're recompiled as 32-bit, or if they're run in a VM or kernel module.
- badsectoracula 9y agoI'm going to guess that some stuff might be there, if for no other reason than to support the bootup process for computers that use the classic BIOS which starts at 16bit real mode. Although considering that 32bit Windows can still run 16bit code, i guess they also need to be able to compile the 16bit-to-32bit bridge code so this is probably another reason why the 16bit stuff exist.