The original GAME.EXE suffers from the infamous "Runtime error 200" at
startup on modern computers (starting with around 200 MHz).  This is
binary-patched in ERROR200.EXE, so run that instead if you do experience
the problem (or better yet, run the original in DOSBox with low enough
"cycles" setting - e.g., the typical default of 3000 works fine, and you
can go for higher settings like 10000 as well).

Additionally, on modern laptops with Bay Trail CPUs (Atom-derived), the
picture is corrupted (has 2 pixel wide vertical lines, then more errors
accumulate in those columns):

<solardiz> Testing my #ZeroNights non-slides on bare metal, I ran into and researched a bug in Intel Bay Trail CPUs with unaligned writes to VGA memory
<solardiz> On at least N2815 and N3530, unaligned writes in VGA mode 13h & ModeX are skipped if they cross 8-byte but don't cross cache line boundary
<solardiz> Apparently not in Intel's errata found in October 2014, Revision 009 "Specification Update" for N- and J- series CPUs. Where do I report?
<solardiz> BIOS update (for maybe more recent Intel microcode) didn't help. Probably a silicon bug, but might be fixable (helpful MOV*/STOS*, anyone?)
<solardiz> The corresponding unaligned reads appear to return all 1's (so 0xffff for 16-bit, etc.) regardless of actual video memory contents
<solardiz> The issue is not seen e.g. on i7-2600K (a much older CPU also with integrated graphics). Also not seen on affected CPUs when in SVGA modes.

The same issue might affect other Silvermont core CPUs (such as 8-core
Atom CPUs intended for servers).  It's just even less likely that you'd
run the game on those, especially on bare metal.

As usual, running in DOSBox helps against this CPU issue as well.
