This is one of the most common problems a new user can have. The most common problems encountered with programs in the IBM world are:

1. Not Enough Memory;

2. System Configured Incorrectly (or not in a standard fashion);

3. Sound not working or locking system - Screen looks ugly or loses colors;

The most common reason a DOS based program doesn't start is that there is not enough conventional RAM memory. A DOS based computer (IBM PC or compatible) has inherent limits for DOS applications (programs) regarding memory access.

You may have heard of the "640K barrier," which is what NORMAL DOS is limited to... 640,000 bytes of "conventional memory." With DOS 5 and above, or using a special memory enhancement program (such as QEMM or EMM386), there is another 384K of upper memory if made available... but this is usually difficult for the average user to configure correctly.

No matter how much memory a DOS based computer has, the limits on conventional memory is still 640+384 (max) minus xxK being used by the programs and environment being loaded at start up by the Autoexec.Bat and Config.Sys files. Even with 16 Megabytes or more a person can still get the “Not enough memory to Load” message.

Using memory managers is possible (and usually easy) to do. Some basic changes may be all that is required to enhance your systems ability to recognize more of its memory. DOS v6 shipped with MEMMAKER. This program can be very beneficial if you are NOT on a network and don't have any unique cards in your system. I would NOT recommend using it, except as a last resort and knowing that there is a chance it could make matters worse (although less than 20% likely). Remember to make a copy of your current Autoexec.bat and Config.sys files before trying any system changes on your own (even if you’re technically oriented... its better safe than sorry).

A couple popular games on the market require 605KB free conventional memory, others require EMS memory, and yet others require that NO “Protected Mode” software (such as disk compression software) is running in order to operate. Unless these programs are just incredibly awesome, we have purposely tried to stay clear of these serious technical challenges. In most cases, if the program was supplied by us, we have either tried to automate the operation, installation, or provided instructions in the MORE section as to what you will need to do in certain instances. Running “MEM /C” (without the quote marks) will tell you your largest excitable DOS program, Conventional memory, EMS, XMS, and all kinds of goodies. We DO NOT recommend novice computer users attempt to make the changes without a back-up, a smart friend, and/or trained technician handy.

If you purchased a computer completely set up, with all the programs and special cards (i.e., sound cards, modems, and scanners, etc.) then you run a slight risk that the person which set up your system didn't do it quite right, and/or had optimized it for the programs they used most often... not for YOUR needs.

You may need to have a trained computer technician make such changes & optimize the computer for your specific needs. We do NOT recommend the use of MEMMAKER (supplied with DOS v6 xx) as a cure. In fact, MEMMAKER does NOT take some very important factors into account and can actually WORSEN the problems, so you need to be very careful. *Please make a BACKUP of the following files: Autoexec.Bat and Config.Sys before attempting to change them (whether manually or using a program like MEMMAKER).

Some things you can check are:

Video settings, are you running in 640x480 resolution with at least 256 colors? Can you raise the number of colors you are displaying? Is your resolution higher than 640x480 (i.e., 800x600, 1024x768, 1280x1024, 1600x1280)? Maybe you need to lower the resolution to have the fonts, pictures, videos, etc. display larger and/or with more colors.

Memory settings, there are too many contingencies to explain or offer a solution for even most systems. However, an easy way to check your memory usage is to type in MEM /C |more (that’s MEM space forward slash - on the question mark key - C space pipe - which is the vertical dashes usually on the back slash key - MORE). You type this mess from DOS and it will tell you what, where, and how programs are loading into memory. Adding a greater than (>) symbol PRN in place of the pipe MORE will dump the information to your printer.

Know Your System, Whether you get a hold of MicroMedia, Microsoft, Apple, IBM, Packard Bell, Gateway, or another company in this industry, you need to keep the following things in mind:
First, the technician didn’t build your computer and will probably ask what type it is… NOT the BRAND, but what the actual guts are. Your invoice, manual, local tech or a smart friend should be able to help you by filling out a piece of paper stating the CPU, RAM, hard drive size, operating system, video card, sound card, modem type, etc. virtually everything inside your computer plays a part in the WHOLE operation of YOUR system, which makes it different from virtually everyone else’s. Having this information handy will make the technicians job easier and faster.

Second, you called the technician for help… listen and try to follow that persons lead and instructions. Don’t push buttons or try things on your end without their specific direction, and don’t get ahead of them. If the tech is going too fast for you, ask them to slow down and/or explain. If they aren’t helping you, then ask to speak with their supervisor. You called because you couldn’t figure out a solution to what ever the problem or question was, give them a chance to help you… to teach you… and to solve the problem. No one knows everything, and even the most experienced tech gets stumped once in a while. They have rules and policies their job requires them to follow, and most will try their best to solve your problem, or suggest where or how to best solve the problem. Remember, most of them didn’t create the program… they just try to support it.

Third, the communication must be good on both sides. If the tech can’t understand you or you can’t follow them, there will be an obvious problem. Either the tech will need to picture your computer screen in their head OR they will have to recreate it on their computer. If one of these two things can’t happen quickly, then you will need to either try a different approach or a different technician.

Forth, don’t bother calling technical support unless you are in front of your computer. Neither you or the technician can be assured the problem is solved until the solution is tried, and both you and the tech often get frustrated… and you will likely have to start all over with another technician when you call back in (which doesn’t usually help).

Fifth, and lastly, remember there are usually other people waiting on the technicians time also. It is NOT the job of the telephone tech to solve all your computer problems, or to spend time on problems that are caused by programs (including operating systems) that other companies designed and sold you. If the tech exceeds your expectations, goes beyond the call of duty, and helps solve problems faster, better, or more completely than you expected… you might consider writing a letter or sending e-mail to the company they work for. Praise can go a long way… and could make it better for the person who took the time to exceed their duties. The same holds true for real bad, discourteous, or ignorant technicians… complain in writing… the companies will listen!

In most cases, if the above doesn’t work, you can call a good tech out to your house or business for a “general checkup” and maintenance call, which may cost $20 to $50 minimum, but can save you a great deal of time and stress. If you aren’t sure, remember that the worst case scenario is you lose all of your data, re-format, and re-install all of your programs (assuming you have them on floppy disk or CD ROMS). This IS NOT THE GOAL! Be careful, and don’t experiment by making changes you aren’t positive you can undo.

There are dozens of different sound cards and video cards on the market. Some have a lot of features, others are limited. In the Windows world, Microsoft Windows controls the system, the sound, video, mouse, printer, etc. to the best of its ability. This means that if a device works in one Windows program, it will usually work automatically with all other such programs. This is probably the single largest advantage to Windows (besides the Graphical User Interface - GUI).

We have found, however, that this assumption is NOT always true, especially in the Windows 95 world and with DOS programs running through Windows. There are certain problems which we have defined in the past few months that make 100% compatibility impossible. We are actively testing and solving as many known compatibility problems as we can, whenever possible.

DOS, isn't “standard” or “automatic.” If you have ever tried running some of the fancy new games on the market, you already know this. Each DOS program must use it's own video drivers, sound drivers, mouse drivers, etc. therefore incompatibilities are not only possible, but also probable if your system is slightly out of the "ordinary," or configured with non-standard and/or high-end components... or hasn’t had it’s memory usage “tweaked.”

This is even more true for DOS based programs which may or may not have been set up to run under (over, through, and with) one of the many Microsoft Windows versions. In many instances you may never realize a DOS program is being ran (through Windows). Windows 95(r) is often very good at fooling even the experienced end-user. Unless there are problems or incompatibilities the user will only know the program works (or doesn’t).

We have made best efforts in selecting and setting up programs (whether DOS or Windows based) to reduce the surprises for you - the end user. We have either solved all known problems (if any) OR documented them in this file and the MORE file. Most programs, on most systems, ran under normal conditions, run perfectly, or as expected. We hope this is the case with your computer and the program(s) you have purchased from one of our valued distributors.

Things you can check (and try) regarding problems with your sound card are:
 

a) Are your speakers plugged in and powered on? This is surprisingly common.

b) Run the test for 8-bit, 16-bit, and FM sounds from DOS - NOT WINDOWS! Just because you can hear sound in Windows doesn't mean DOS is configured correctly. Most sound cards ship with a sound test program, or have a "Test Sound" in their configuration file. If it doesn't work here, NO DOS game (program) can work effectively.

c) Look in your Autoexec.Bat and Config.Sys files, verify the settings. A220, D1, and I7(or 5) are the most common settings for Sound Blaster and compatibles (A=Address, D=DMA Channel, and I=IRQ or Interrupt).

d) Verify that the program is set correctly. Some programs have a "Setup" or configuration files on the main menu or available through HELP. Other programs have such configuration information accessible through another program. If the program isn’t working as expected, you may have to look in the directory the program exists on the disc or your hard disk drive (if you installed the program) for additional information about the program you are having trouble with.

e) Remember, if the program was intended to run directly from a CD ROM disc, and the setup program is not on the main menu (i.e., a separate program) you will probably have to INSTALL (or copy) the program to your hard disc drive to make it run, as the new settings can't be saved to the CD ROM disc.

e) If your system starts the sound, THEN locks up, chances are you are either getting power feed back from amplified speakers, or having a problem with the 16-bit compatibility. Try selecting regular Sound Blaster (not SB 16 or SB Pro). You may set the IRQ to 7 rather than 5. IRQ 5 began with the release of SB 16, and many older 8 bit card and 16 bit compatibles can't access IRQ 5 correctly or maybe an internal modem is trying to share that setting. If that doesn't work please consult your sound card manual or a local technician, as the problem is too specific to YOUR system and software to attempt a fix over the telephone.