Memory Limitations For Macros, Keyboards, Cut

DocumentID: 602774
Revision Date: 29-Feb-96 1:29:37 PM

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

Problem

Symptoms: The customer would like to know the answers to the following questions: 1. How large is the memory buffer for Cut and Paste? What limitations are there? 2. Is there a limitation on the size of macros or the number of macros? 3. A customer receives the error message "Not Enough Memory" when editing a macro in the WordPerfect 5.1 Macro Editor. The customer can edit a macro that is 9,300 bytes, but cannot edit a macro that is 10,000 bytes. The problem can be worked around in two ways: 1) loading expanded memory, or 2) loading expanded memory but exiting Shell and starting WP from DOS. With either method, the customer can then edit a macro as large as 21K. Why can't the customer edit at least the same size macro with expanded memory as she can without? 4. Another user cannot make changes to a keyboard definition that is over 55K. The customer receives the error "Not Enough Memory", the machine locks after about 25 keystrokes or it simply ignores the changes. What is the size limit to edit a keyboard definition. Solutions: 1. The memory buffer for Cut and Paste is limited only by the disk space and expanded memory available. 2. There is no limitation on the size of macros except in saving them from Editor 3.0. There is a limitation on editing macros within the WordPerfect 5.1 macro editor. The limit is 4-5K, unless the document screen is blank which brings the limit up to nearly 10K. The user should edit larger macros in Editor 3.0. 3. When you load an expanded memory (EM) driver, it consumes part of your conventional memory (CM). When you load Shell, it also consumes part of your conventional memory. When you load both, you have less conventional memory than any other combination of the two. Both the memory manager and Shell must be run in conventional memory. WP treats expanded memory the same way as it would additional disk space for overflow files. Currently, WP code does not allow data overflow to disk which would, therefore, also be true with expanded memory. You will find that this is not the case under WP for Windows where WP is running extended memory and, therefore, is limited only by the available extended memory plus conventional memory. The need to create or edit larger macros is possible in Editor which allows virtual overflow files in terms of macros. Therefore, to have WP 5.1 overcome this limitation, a change in the code would have to take place to allow the use of disk management in terms of macro structures larger than the amount of available conventional memory. 4. The macros are too big in the keyboard layout. The customers was able to save the Shift-F1 key out as a macro file and it's size was 5,929K. The limit the macro editor allows is around 5K. The customer should either CHAIN the macros or not put them in a keyboard layout. Then edit the macros in the Macro Editor that is designed to handle larger macros (macro size limit 64K).

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.