Top Navigational Bar

"Insufficient Memory" Error - Drivers Not Loading into the Upper Memory Block
DocumentID: 616452
Revision Date: 29-Feb-96 1:37:26 PM

The information in this document applies to:
WordPerfect® 6.0 for DOS

Problem

Symptoms: Preview locks the computer, or returns an "Insufficient Memory" or "Invalid Error ID Found" error. The customer had been able to allocate only 520K free conventional memory before entering WP 6.0 DOS. Solutions: Several device drivers were not loading into the Upper Memory Block (UMB), even though they were properly designated to do so by LOADHIGH commands. The customer was using EMM386.SYS with the RAM option, and was excluding a couple of Upper Memory Blocks (such as the video RAM). After examining the system using the DOS command MEM/C, it became apparent that several of the drivers that the user was attempting to load into Upper Memory were being loaded low (into conventional memory). After changing the RAM option on the Device=EMM386.SYS line in the CONFIG.SYS file to a NOEMS option, the area that EMM386 had been using for Page Frame was freed to load devices high, giving the customer 580K conventional memory free before loading WP. After taking these steps, the errors no longer occurred.

How/Why:
Booting "vanilla" resulted in 580K of free conventional workspace (compared to the 520K previously reported), and resolved the problems. By freeing up the page frames, other device drivers and TSRs were able to load high, leaving more conventional memory for the program.

Another user received this error because the user's system was not able to load DOS or drivers or TSRs high. The original CONFIG.SYS listed as follows:
device=c:\dos\himem.sys
device=c:\dos\setver.exe
files=40
buffers=15
dos=high
devicehigh=c:\dos\emm386.sys
devicehigh=c:\mouse\mouse/sys
...

The problem disappeared after editing the CONFIG.SYS to read as follows:
device=c:\dos\himem.sys
device=c:\dos\emm386.sys noems
dos=high
device=c:\dos\setver.exe
files=40
buffers=15
devicehigh=c:\mouse\mouse.sys
...

With the original CONFIG.SYS, the Upper Memory Block (UMB) was not being allocated since the EMM386.SYS device driver line was lacking any parameters to set it up (such as NOEMS or RAM). Also, DOS was not loading high because the command came before the loading of the memory manager. By making the changes listed above, the customer was able to gain sufficient conventional memory workspace to resolve 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.