Windows 7 – Old Games Won’t Play.. Help! (Updated)

5 6 Methods For Getting Old Programs To Run On New Computers

This article is an updated and improved version of  Windows 7 – Old Games Won’t Play.. Help!, a “reader question” article that has proven quite popular. It seems quite a few people want their 12-year old, 16-bit, Gen 1 games to play on latest generation, 64-bit machines, (I don’t blame them) but it doesn’t always work. Here are some tips for solving the problem. They are in the appropriate order, IMHO. (These work in Vista as well.)

1) Turn off “hardware acceleration”. A common cause of errors and “playability issues” is the old games’ use (or lack of) of hardware “acceleration”, which is referring to the “video card”, or more accurately, the graphics driver. Most graphics drivers allow you to turn off the hardware acceleration (which may resolve your issue).
Click Start in the lower left corner of Windows.
Click Control Panel, click Appearance and Personalization, click Personalization, click Display Settings, and then click Advanced Settings.
Click the Troubleshoot tab, and then click Change Settings.Move the Hardware Acceleration slider until it is one notch to the right of None. This is the basic acceleration setting.
Click OK twice, and then close the window.
Restart the computer.

[you can also get there via the graphic adapter’s Properties in Device Manager]

[Note: Change Settings will be disabled if the graphics card drivers do not support disabling hardware acceleration. You may need to check the video card manufacturer’s website, and download the latest driver.]

2) You may need set the troublesome games to launch in “Compatibility Mode”, and tell them to run under Windows XP SP2. This article, https://techpaul.wordpress.com/2009/06/28/compatibility-tricks-for-old-programs-new-machines/ shows you how. The “Compat Mode” section is about half way down the page.

3) You might need to try repeating Step 2, but this time install directly to your C:\ drive (by default, Windows will install programs to C:\Program Files or C:\Program Files(x86) folder) using the “Custom install” option during set up. This will eliminate some of the Permissions issues that keep older programs from running correctly.

4) You may also – if the game is old enough – need to turn off all but one CPU core. This is called “setting the affinity”. Also see, Compatibility Tricks for Old Programs, New Machines. If this resolves your issue, the article includes a download for a tool to make this setting ‘stick’.

5) For really old, DOS-based games, install DOSBox. DOSBox is a great tool, especially for old games. I would suggest reading the tutorial, here: http://www.dosbox.com/wiki/DOSBoxShortcuts#Windows

6) Though I view this as a bit of a ‘last resort’, you can install a “virtual machine” and run the game in there.
* If you have the Professional, Enterprise or Ultimate edition of Windows 7, you can download XP Mode – which is really Virtual PC – for free. If you have other editions of Windows, grab Virtual PC 2007 from the same place.
* Perhaps a better alternative is using VMWare Server (free), from www.vmware.com/products/server. I have read that the VMWare handles the hardware acceleration better.

In both cases, you’ll have to supply the copy of (old) Windows yourself, and install it (into the “virtual machine”) from scratch.

… I hate to say, but it is possible that you may try all these things and get unsatisfactory results. I keep an old Pentium II machine (Windows 98) around just for playing those old games (which I wouldn’t dream of connecting to the Internet!). The games play best on the hardware/OS of their day. You might need to do the same. Or.. say goodbye to your old friends.

Progress!

Copyright 2007-2011 © “Tech Paul” (Paul Eckstrom). All Rights Reserved.

---

>> Folks, don’t miss an article! To get Tech – for Everyone articles delivered to your e-mail Inbox, click here, or to subscribe in your RSS reader, click here. <<

---

Share this post :

Stop Error Solution #8 – SigVerif

Vista Stop Error: “A recent hardware changes, or unsigned driver, has prevented Windows from loading..”

The Blue Screen of Death (BSOD) is an error screen displayed by  Microsoft Windows after encountering a critical system error which can cause the system to shut down to prevent damage. (They are not always blue anymore – sometimes you see a black screen, saying only “Stop: 0x000000F1”, or some other similar, ‘helpful’ hexadecimal string – but they are still called “bluescreens”.)

Bluescreen (Stop errors) on NT-based Windows systems are usually caused by poorly-written device drivers or malfunctioning hardware. Way back when dinosaurs roamed, in the Win9x era, incompatible DLLs or bugs in the kernel of the operating system could also cause BSOD’s. (There are different types and causes of stop errors, a good summary can be seen here.)
With Vista, Microsoft got a bit more restrictive, and it can happen when an unsigned device driver is found.

Microsoft got a a little tired, I guess, of taking the rap for the poorly written, and often amateur, device driver-caused BSOD’s. (People tend to blame Windows for the crash..) And so they, over the years, have tried various ways to get the hardware vendors to write and release good driver software, and rewarding those that did with the coveted Microsoft Compatible seal of approval (usually a logo on the box), and placement on the WHQL (Windows Hardware Compatibility List). But.. hardware vendors build, box, and ship, devices.. not program code, or study all the minutia of the OS kernel.

Digital “signatures” (in this instance) are one way to determine if the driver was written by the kid down the street. When a driver has been tested and approved in Microsoft’s own labs, it gets a super-special digital certificate. And with Vista, you pretty much gotta have that driver, or expect stop errors. These Microsoft-signed drivers are available through Windows Update, and the “Update driver” feature (a subset of “Add new hardware”).

(For more on troubleshooting and/or installing device drivers, see my Plug and Play series.)

Tip of the day: In Windows XP and Vista there is a utility that you can use to scan your all your installed drivers. It will report any it finds that don’t have a “signature”. This is a great way to ‘zero in’ on the (possible) cause of the Stop error.

Use the Sigverif.exe tool to identify unsigned device drivers installed on your Windows XP/Vista computer. To use the tool, perform the following steps:

1) Open Start menu, select Run, type Sigverif and then click OK.

The File Signature Verification tool will open. Click “Start”.

The scan will run, and ideally produce the following result…

But if it finds anything, it will produce a list of funny-named files… like “msndis5.sys” which are your unsigned drivers (or, they’re signed.. but not Microsoft super-specially signed). Hopefully it will be a list of one.

2) Use your favorite search engine to find out what the funny-looking driver belongs to. (In my example, it turns out that msndis5.sys is a part of NetStumbler – a very popular wireless “hotspot” locator.) Now you will know which device, or program, needs your attention to cure the BSOD.

3) Remove the offensive device driver.
There’s options to how you go about this. In the case of my example, it is a program. So, I can uninstall the program, or look for a newer version (update) of the program.
If it were a device, I would go into Device Manager (see, If It Ain’t Broke – Don’t Fix It), select the device in question and try:
* “Update driver. If that says ‘no dice’ (“The best software is already..”),
* “Rollback driver”. If that is not available, or fails to stop the Stop errors,
* “Uninstall”, then reboot. Windows will reinstall the device, and it will grab the driver from the WHQL.

Hopefully, this will resolve your issues. If not, you should start looking at your hardware itself. I’ve run long, so..

Today’s free download: Google Calendar Sync.
For anyone who relies on a digital calendar to keep them on track, Google Calendar Sync is a must-have application. The free download isn’t fancy or even pretty–a simple log-in and options list comprises the system tray icon. However, the meat of the application is what it can do, which is flawlessly add details of Outlook calendar items to Google’s Calendar, and vice versa.

Copyright 2007-9 © Tech Paul. All rights reserved. post to jaanix

Share this post :