Member Avatar for LestTurk

of running 16-bit or 8-bit applications?

It makes no sense.

If I was behind the development of Windows 7 in general nobody would complain, because my ideas are priceless.

  • 7 Contributors
  • 7 Replies
  • 321 Views
  • 3 Months Discussion Span
  • Latest Post Latest Post by zimbrax

Dani AI

Generated

Short answer: it was not an arbitrary choice but an architectural one. 64‑bit Windows does not include the 16‑bit compatibility subsystem (NTVDM) and the CPU mode that makes real‑mode/virtual‑8086 execution possible is not available when the processor runs in x86‑64 “long mode.” WoW64 translates 32‑bit calls for a 64‑bit kernel but does not and cannot execute 16‑bit code natively.

A bit more detail: 32‑bit Windows provided NTVDM and “Windows on Windows” support so legacy 16‑bit DOS/Win16 programs could run. On an x64 build those kernel pieces are absent because the hardware/privilege model changed; reintroducing full 16‑bit support would have required a large, slow emulation layer and extra maintenance and security surface for very few users. That explains why ’s comment about cost/effort is on the right track, but the root cause is the processor/kernel interaction rather than a simple library decision.

Practical options (building on points from , and ): for DOS-era programs and many old games, use DOSBox (emulates VGA, sound and low‑level DOS behavior). For Windows 16/32‑bit apps that need real Windows services or drivers, run a 32‑bit Windows guest in VirtualBox/VMware/Hyper‑V or use the Windows 7 “XP Mode” VHD if available. For very hardware‑specific titles, hardware emulators like PCem/86Box give higher-fidelity results. If legacy scanners or dongles require 32‑bit drivers, a 32‑bit VM with USB passthrough or a networked service is usually the safest route.

Caveats: some old software talks to hardware directly or installs 16‑bit drivers that simply won’t work even in a VM. Licensing for old OS images and dongle support can be hurdles. Where possible, seek vendor updates or modern replacements to avoid long‑term fragility.

Recommended Answers

All 7 Replies

Member Avatar for Shinedevil

Simply because the libraries for 16 bit applications contain depreciated code that doesn't work with modern 64 bit processors. To write work arounds for these libraries would be time consuming and cost a lot of money, you're lucky you even get compatability mode in my opinion.

Member Avatar for rubberman

Run Linux with qemu installed. Then you can run just about any sort of emulator you want... and often faster than on the original hardware with modern 64-bit x86 systems.

Member Avatar for skilly

i agree with repliers,
virtualization(emulation) can help run some vintage stuff. problems also happen with 32-bit processors(x86)
another workaround would be installing vintage OS on seperate partiton(instead of virtual).
i remeber hearing somewhere the root cause was something like Win7 does not support apps meant to run on a FAT/FAT32 formatted disk, because win7 will not run on FAT itself....

I always try compatiblity options before more drastic measures(depending on importance, like the software that runs my old scanner so old not supported even by XP!)

Member Avatar for cocolio

Emulation its not the same as virtualization jerk!!! in virtualization you are using idle states of the processor to run another OS on your system, while emulation you EMULATE a different instruction set on your system, for example Z80 processor instructions in your x86 or x64 system.

Anyway why are you using such old software, try to upgrade your software, out there is a lot even for free.

Member Avatar for skilly

did i say it was the same? I'm not talking about HyperV, my friend.
what about VMware, virtual PC, virtual box
why don't you teach me all about those programs, cocolio? since you are so smart...OP is banned anyway

Member Avatar for legendster

Not priceless but useless :)

Member Avatar for zimbrax

I have been following other posts and I could find out that this cocolio always writes nonsense about what he doesn't even know and seriously his comments and posts should be considered as spam, not as true contributions. Be careful.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.