Wine runs 16-bit Windows programs on 64-bit Windows by the use of 16-bit
protected mode segments through modifying the Local Descriptor Table. The
64-bit Windows port of WineVDM (OTVDM) has to use a CPU emulator because
processes can only modify their LDT on 32-bit Windows (where you can just
use native WOW.)

There is not technological limitation that Windows is enforcement

I'm not entirely how current WineVDM traps "DOS" calls made by 16-bit
Windows programs or handles their expectations of Windows being extended
DOS (e.g. int 21h and a PSP, for starters) but for the most part, most apps
designed for Windows 3.0 or later expect to be ran in protected mode in a
16-bit protected mode segments to begin with. This contrasts with the
previous implementation of WineVDM that used vm86 (and could even directly
run some DOS programs, mainly non-interactive utilities.)

On Tue, Dec 17, 2024, 13:48 Liam Proven via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:

> I don't know -- there's WINE. It runs 16-bit apps on 64-bit OSes,
> which is more than Windows itself can or will.
>
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to