On Sat, 16 Mar 2019 19:53:12 -0400, in alt.comp.os.windows-10, Paul
wrote:

Instead, it's a message
which is telling you that there is no WOW subsystem available
to run 16 bit code on a 64 bit OS.

Or the NTVDM. Microsoft wasn't willing to port either of them. This
software is all about 2 decades old (or more), unless you're talking
about a recycled 16-bit InstallShield for a 32-bit app. AFAIK, 16-bit was
essentially deprecated on Windows in 1995, though companies still wrote
stuff for MS-DOS before NT4 and the DirectX HAL (for games, display and
sound) hit. But both WIN-G and the GDL sucked, after all. 16-bit was gone
almost entirely a few years later, and good riddance to preemptive
multitasking tying up your entire machine with a crash. Ah, memories.

I don't blame them for calling it quits, but it wasn't impossible. They
could have ported it to 64-bit. They just couldn't recycle the 32-bit
code to do it, and they'd be running the WOW layer on top of the WOW64
layer, which is a bit too Frankenstein for good sense. So why do it at
all? It is a good question.

But Windows XP games like he's talking about are 32-bit and 64-bit, and
WinAero is pretty trustworthy AFAIK. The core Zone games were ported to
Win 7 x64. That's where WinAero got them from, and before that you'd have
to hack them in a hex editor yourself.

A lot of XP games will run on Windows 10, but, excepting the WinAero
package, it's advisable you don't put them in the Program Files (x86)
directory. Most XP gaming stuff isn't designed with ACLs or multi-user
environments in mind.

--
Zag

West of House
There is a small mailbox here.

read leaflet
"WELCOME TO USENET!

USENET is a game of adventure, danger,
and low cunning. In it you will
explore some of the most amazing
territory ever seen by mortals. No
computer should be without it!"