Windows/DOS Error Messages

Many people think they no longer have DOS if they are running Windows '95 or Windows '98.  In actuality, they are using DOS 7.  Therefore, even windows programs will still encounter DOS errors.

DOS Errors are displayed in brackets in the error message line.  For example:

 PROC PRO1020  LINE 84  EBRAND.NTX (2)            

DOS Error 2

When a DOS Error 2 message is shown, it means that a file, necessary  for the operation in which you are engaged, can not be found.  This  usually results from a disk crash, or someone tampering with the  files and/or directories.  The first step is to reboot the computer,  and try again.  If the problem continues, then do a listing of the  The Auto Shop Writer subdirectory to try and find the file.  If it is  truly gone, run a disk drive diagnostics to see if the FAT table has been damaged.  Usually the file will still be on the drive, but its  pointer information will be missing from the FAT.  You may wish to  use some commercially available utilities to recover the file, or  you can restore it from your last backup.

DOS Error 4

In your CONFIG.SYS file, you must have files set to at least 101.  If you have a number less than this, you will most likely incur the  DOS Error 4.  DOS normally provides for opening two files.  You must set the limit  higher when using The Auto Shop Writer.  The recommended number is 101, but other programs may need more, so a higher number will not cause  problems.

DOS Error 5

Your network has denied access to the file you need.  There are several reasons.  First, perhaps you need the file exclusively, and someone else is using it.  Once they exit from the file, you can go back and perform the task.

More frequently, someone aborted the program while a file was open.  This means that the network server still has the file locked in its "lock table".  To fix this problem, you must exit the program on all machines, and actually shut down the server ( power off completely ) to erase the lock table from memory.

Divide By Zero

The Auto Shop Writer must perform many calculations when handling data.  Among these is division, which is used when calculating averages and  percentages. Computers do not like to divide by the number 0, and  provide this error message.  Although

every attempt is made to trap 0's in the denominator,  occasionally an operator will not enter all of the necessary data.  This leads to the error.  No harm will be caused to the system with  this problem, nor will any data be changed or damaged.

Numeric Overflow

In this case, the computer has a number which is too large to fit  into the record space allocated in the file.  For example, your  system has a workorder that totals $10,463,297.88.  To conserve  storage space, The Auto Shop Writer assumes that workorders will not  exceed $99,999.99.  The large number will not fit in the space set  aside, and you will have the error message.  Usually you will find that this problem occurs because you have  entered erroneous data.  Charging $12,000 for each of 80 spark plugs  is probably not accurate on an 8 cylinder vehicle.

If you get this message, quit the program, and restart it again.  Then go to the workorder, and find the part with **** in the price  location of the parts listing.  Enter the correct information.      

Insufficient memory / Memory fault error

Your system is complaining that you do not have enough memory  available to run the program. In today's computers, this is a rare occurance.  However, you may have been running some windows programs that did not clean up after themselves, and they left a lot of garbage open in memory which is wasting space.  By shutting down your windows system, and then restarting it, you will have clear memory, and your problem will probably quit occuring.

General Protection Fault

The most common message when Windows has a problem is a GPF error message that yields virtually no helpful information.  Generally these will occur when another program is somehow conflicting with The Auto Shop Writer.  If you encounter this message, exit the program, re-enter the program, and see if it occurs again.  If not, it was "transient" and cannot be traced.  If it does occur, then completely shut down Windows, and start the computer again.  If the problem goes away, it was caused by garbage left in the system by another program.  If it still exists, send us an email with as much description of the problem, and how it occured, as you can remember.