Top Navigational Bar

Expanded Memory Locking System
DocumentID: 607592
Revision Date: 29-Feb-96 1:32:29 PM

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

Problem

Symptoms: The customer has Expanded memory running and tries to load WP 5.1. Every time, without exception, the program will eventually lock. The customer can type fine, but when a function key is pressed, the system locks. Sometimes they can press one key without a problem, but another key will lock the program. When the program locks, the screen goes blank, and a message flashes across the screen saying "Your Program Violated Privilege Rules."

When the customer doesn't load EMM, the program works fine; /NE also works fine. The customer tried /W=120/512 and /W-93/256 which also locked the machine before they could get to the document screen. Solutions: WPCorp has had several reports of 5.1 not working in expanded memory, and have yet seen a case where WordPerfect was the source of the problem.

The offending memory managers fall into two categories:
1.      Those which take Extended memory and cause it to emulate Expanded memory.
2.      Those which do not fully support the LIM specification.

The most frequent complaints come from those in category one. This is because WP does something called "data aliasing," which cannot be done in most extended memory situations. The 01/19/90 and later releases do not work with data aliasing, therefore allowing WP to work with more emulators.

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.