STD*MIS - FAQ - System Errors
Red Screen Messages
Q1: What do I do when I keep getting a large red error message on the screen?
A large red error message may sometimes appear to signify that a significant error has occurred in STD*MIS. This error message is obviously different from other error checks, because this error message is very large (practically covering the entire screen or STD*MIS application window). And, once it occurs, you have just two options:
- View the application screen as it appeared just prior to the occurrence of the error; or
- Quit to DOS (your immediate session with STD*MIS is ended).
A copy of this error message is automatically placed into a file called "ERRLOG.TXT" in the STD*MIS working directory for future reference.
Since there are many reasons (too numerous to list here) why this large red error message occurs, the fix may not be readily apparent from the information listed. Though the large amount of technical information contained within the message is designed to explain the reason for the error, you should contact your STD*MIS Support Person for assistance.
System Freezes
Q1: Sometimes the system freezes and I am stuck with a blinking cursor at "loading data files". What do I do?
The system is not able to load the files. Type Ctrl + Alt + Delete key, highlight STD*MIS and click "End Task". This will be the easiest way to escape out of the system.
The problem may occur because you have opened STD*MIS in more than one window on your workstation. You may look down at the task bar on the bottom of the screen and see that there is more than one STD*MIS prompt there. Make sure you have only one window of STD*MIS open on a single workstation at a time.
The problem may occur because your network environment has changed. You should check with the Network Administrator to make sure "SKIPADS.TXT" is in the subdirectory if you are NOT using Advantage Database Server Software. If this file is missing from the STD*MIS directory on the server you should download this file from the STD*MIS Web Site and copy it into this directory.
The problem may occur because of a high volume of network traffic. Try logging of the system and rebooting your computer.
If the problem persists contact your STD*MIS Support Person.
Processor Stack Fault
Q1: When I try to start STD*MIS, I get an error message: "blogin 0: unrecoverable error; processor stack fault". How do I rectify this error?
The computer does not have enough space to load all the files. Check to be sure that your config.sys/config.nt contains the statements:
FILES=201
BUFFERS=40
If you are using Windows NT you can make this change in two ways. The first, and safest way to accomplish this is to place a copy of your CONFIG.NT file in the directory holding STD*MIS. You can find CONFIG.NT in the WINNT directory under the SYSTEM32 subdirectory. Then you should modify this copy of the CONFIG.NT file by going to a DOS prompt and changing the directory to the STD*MIS directory. Type "Edit CONFIG.NT" <enter>. Scroll down this file until you find the FILES= and BUFFERS= statements. Modify the values in these statements to equal those listed above. Then you should create an icon on your desktop to access STD*MIS. Once you have done this, right click the icon and choose Properties. Select the Program tab and then choose the Windows NT button. Change the value in the Config Filename box to the drive:\directory that holds the modified copy of the CONFIG.NT file. (i.e.; X:\STDMIS\CONFIG.NT). This will allow the DOS session to access the modified file. However, if you attempt to start STD*MIS in a separate DOS session (without using the newly created icon), you will most likely receive the original Processor Stack Fault error.
The second way to rectify this error is to modify your CONFIG.NT file with the statements listed above. To do this go to a DOS prompt and change the directory to WINNT\SYSTEM32. Next, type "Edit CONFIG.NT" <enter>. Scroll down this file until you find the FILES= and BUFFERS= statements. Modify the values in these statements to equal those listed above.
- Page last reviewed: December 16, 2015
- Page last updated: July 12, 2013
- Content source: