Gamers need to understand batch files

Question: I have a new Acer computer and cannot seem to get NHL 97 working. I have read the manuals over and over again and each time I think I have it right, I go to run it and my computer locks up. I then have to unplug the computer and run Scandisk to get it going. I have done this at least 10 times now and am afraid I am doing damage to it. Any ideas on what I am doing wrong? Have had a friend or two come by and they can’t get it working, either. Please advise solution or should I just throw this $80 game out the window?
Frustrated

Answer: It seems that PC game players often have to become computer experts to indulge their hobby. While most Mac games are plug-and-play, Windows and DOS users still live in a netherworld between editing configuration files and instant rock-’em-sock-’em action.
Let’s deal with your problem first and then I’ll go over some tips for video game players on the PC.
Your first source for a solution should be Electronic Arts tech support page on the Web. It’s comprehensive, simple to navigate, and is an example of how all companies should run tech support online.
Check out support.ea.com/.

Now here are some basic game tips for all video game players on the PC platform. Historically, game setup has been a chore because under Windows 3.1 and DOS, gamers had to configure their computers manually to free up enough memory so the game would load. The problem was that in the pre-Windows 95 days, the ever-so-precious first 640K of RAM had to be rationed out to programs otherwise they wouldn’t run. This meant editing configuration files on a boot floppy disk. They included both autoexec.bat and config.sys. Both of these files were used to put mouse drivers and memory managers in place before the machine booted. If you open one up with an ASCII text editor (like Notepad), you’ll see a bunch of lines of “code.”
These lines, which may seem like nonsense to a new user, are simply DOS commands.

Mastering DOS batch files isn’t an easy thing to do, but if you want to become a hardcore gamer and play a lot of the old DOS titles, a good place to start is your game manual. Most DOS-based game manuals have easy-to-follow steps and usually you can be up and running in a short time if you follow directions carefully.

The next place to look for help is your MS-DOS manual. It explains the rudiments of batch file architecture.

Among the most common problems with DOS games are missing drivers in either your autoexec.bat or config.sys file on your boot up floppy. Drivers are little programs that allow your computer to access different types of hardware. Problems typically arise when the video drivers, the mouse driver, sometimes a CD-ROM driver, is missing. There’s no easy way to troubleshoot these problems without the help of someone who knows what they are doing. Find an expert and ask them to teach you. Here are some quick tips for those who have a little experience and need a kick start:

  • Video drivers: Usually, the game needs a VESA driver. You should be able to get this from your video card manufacturer. Also check on the floppy disks that came with the card.
  • Mouse drivers: Most often, you’ll be able to fix this by looking in your mouse directory and finding the program that runs your mouse. Let’s say you find it in the mouse directory and it’s called mouse.exe. Just add the line c:mousemouse.exe to your boot floppy’s autoexec.bat file with an ASCII text editor.
  • CD-ROM: Your CD-ROM driver is a little more difficult, but you should be able to get the appropriate autoexec.bat command from your CD-ROM manual.

If this whole column frightens you, take heart, Microsoft attempted to remedy the nasty DOS-configuration situation with DirectX under Windows 95. DirectX is a piece of software that allows a game to get directly at the hardware resources on a computer without having to go through all kinds of behind-the-scenes software layers.

Before DirectX came along, game developers complained to Microsoft that Windows 95 slowed down game performance considerably. DirectX was the solution. When you buy a game, look for a Windows 95 logo, if you want to skip the grief DOS games create. Typically, a box will say it’s Windows 95 compatible and uses DirectX. If this is the case, when you install the game it should also install DirectX first. To determine what version you’re running now, locate the file Ddraw.dll in your c:windows system directory and right-click on it. Then select Properties and then the Version tab. Version 4.04.00.0068 means you’re using DirectX version 3 or 3a. If Ddraw.dll is missing, DirectX is not installed on your machine. Your game should install DirectX for you, but if you want to, install DirectX 3.0a on your own. This is recommended for those with MMX-enabled processors.
If all else fails or if you’re looking for more information on DirectX, visit the DirectX website.