Andrew said:
(e-mail address removed) says...
XP Mode is only availble for Business and Ultimate versions. I don't
think it will install with the Home versions.
Nope, it's for the following editions of Windows 7:
- Professional
- Ultimate
- Enterprise
What is this "Business" edition you mention? Never heard of it. You
are correct that it won't install in the Home editions. That's because
Microsoft added the VMM (virtual machine manager) to accomodate
*business* (their primary and preponderous revenue source) so they could
continue running their legacy applications. Home users aren't
considered a sufficient customer base to add this component and then
have to support it. For them, perhaps they can use another VMM (but it
won't appear as seamless as XP Mode). Also, whether using XP Mode (a
VM), VMWare, VirtualBox, DOSbox, or other some other VMM, the hardware
(except the CPU) is emulated which means the program ran inside a VM
will be slower. For a game like Solitaire the performance penalty might
not be noticable but for a game that makes lots of video updates, like
some car racing game, then the slowdown may be intolerable. That's when
you start looking at multi-booting (sorry, I hate Microsoft's dual-boot
scheme) to run a *separate* OS from a different partition. Alas, that
means you'll need a separate license for Windows XP to load it
separately (versus XP Mode which is a license for Windows XP for use
under specific Windows 7 editions).
From the OP's reply (to Paul), "Win 7 Ultimate X64", so the OP has the
necessary edition to install the XP Mode component. Despite that the OP
has a 64-bit version of Windows 7, I believe "Windows XP" is the 32-bit
version (i.e., the emulated hardware in the VM is 32-bit - only the CPU
is real in an VM but you can install 32-bit operating systems on a CPU
capable of 64-bit addressing). Since Windows XP supported 16-bit
applications (as long as they didn't do direct hardware interfacing, as
do some video games, or attempt to use ancient [DOS-mode] memory
managers) then those old apps should run under Windows XP. From a quick
scan of the games list in the enterainment pack, they don't look like
they require a complicated video interface but probably just use the
system API to paint their windows.
If the game does use non-allowed methods to manipulate the screen, often
when it wants to go into fullscreen mode, it may not load or it will
hang. Sometimes setting the "Disable Integration Features" under XP
Mode will get the game to run but not always. If that doesn't work,
toss the game or find a newer version that is more well-behaved with
video updating. However, even if disabling integration works to get the
game loaded, it will probably run pretty slow. For those really old DOS
games (which may look like GUI Windows apps), you might have to go with
a 3rd party VM solution, like DOSbox.
For running old 16-bit apps in the Windows XP VM (XP Mode), you may have
to configure Windows XP to run them in separate memory spaces; see
http://technet.microsoft.com/en-us/magazine/ff756590.aspx. A problem
that I see mentioned is that a 32-bit program will run on Windows 7 x64
but it uses a 16-bit installer program which won't run on that OS.
Sorry, but I can't find any old 16-bit installers (with a 32-bit program
payload) to test since I don't have software that old. Since XP Mode is
running a 32-bit version of Windows XP and since that supports 16-bit
addressing apps, the 16-bit installer should run under XP Mode.
Users might complain about downward compatibility but eventually to go
forward means cutting the strings that drag down an OS. If your
critical or very important apps require an old OS then that's what you
should stick with. New doesn't mean better. You're supposed to plan
for the migration, not just hope it all works. I bet if pushed, the OP
really cannot give a good reason why he needed the 64-bit version of
Windows versus the 32-bit version. After all the excuses crash about
64-bit apps being faster and finding they aren't, the last excuse if
realized is that more than 4GB of memory can be installed - yet the
majority of their 32-bit applications won't address more than 2GB
allocated for user-mode processes. There aren't a lot of 64-bit apps
around yet because there's no advantage yet. There are high-CPU and
mega-memory apps, like AutoCAD or video editing, but the end users that
use them of which there are few can still do their work with 32-bit apps
and 2GB memory for them. Since the OP is asking about games, it is
unlikely this is a workhorse desktop for company use so there was
probably no good reason to move to 64-bit but like many they got conned
by salesman and advertising.
Although the OP wants to play old games on Windows 7, XP Mode was not
specifically designed to play games. It was a *business* solution so
companies could continue using legacy applications and give them time to
migrate or update their software. It was an attempt to overcome the
inertia that kept companies back on Windows XP.
Also, if you right-click the .EXE file, you can try one of the
Compatiblity modes.
That won't fix the problem of trying to run a *16-bit* installer or app
under Windows 7 *64-bit*.