![]() |
Error - "Internal Stack Overflow System Halte |
The information in this document applies to:
WordPerfect® 5.1 for DOS
Problem
Solutions: A customer received the error "Internal Stack Overflow System Halted" when retrieving or printing large documents (755 bytes) with DOS 5.0. The problem was corrected by adding the line "STACKS=16,128" after the BUFFERS= line of the CONFIG.SYS file. Another customer was able to correct this error message by adding the line STACKS=0,0 to the CONFIG.SYS file. Customers who have more than 2M of memory can enter a higher number in the STACKS statement. The use of SMARTDrive, a caching system included with DOS that speeds up WordPerfect, is also recommended. The line for SMARTDrive should be added in the CONFIG.SYS file. If customers have 2M or greater memory, they can allocate expanded memory for WP and use the /R option. WP used with the /R option, will run faster than WP used with SMARTDrive. NOTE: The "Internal Stack Overflow" error can be corrected with the STACKS line. This is not a WP or DOS problem. DOS applications should handle their hardware stacks internally. Sometimes programs are feeble and don't handle their hardware stacks correctly. DOS has taken into consideration these programs and allows DOS allocation of the hardware stacks. Any time the STACKS line is required, there is a program loaded that is not allocating its own stacks. These problems should be written as STRs to find out exactly what is causing the problem. |
Answer:
Details:
Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER. |