RTP57 error ? URGENT !! (AREV Specific)
At 16 JUN 1998 11:47:10PM Steve (Hong Kong) wrote:
Hi Experts,
I've got the following error message while running a AREV 3.12 program on NT 4.0 or either Novell client machine.
Error message:-
RTP57 LINE 1 B28 NOT ENOUGH STRING SPACE, OUT OF MEMORY.
NOT ENOUGH MEMORY TO EXECUTE DEBUGGER, CURRENT PROGRAM ABORTED.
After this error message, the workstation halt.
Regards,
Steve
At 17 JUN 1998 02:18AM Don Bakke wrote:
This sounds like the workstation isn't getting enough conventional memory. If you can bring up the command window by pressing F5 and then type in WHO, what amount does it show for available memory? It should be close to 300K for decent performance. Anything less than 200K can easily run into problems.
If limited conventional memory is the problem, then you will need to optimize the computer's memory to give AREV as much as possible when it is launched.
dbakke@srpcs.com
At 17 JUN 1998 03:02AM Steve - Hong Kong (Respose to Don) wrote:
Hi Don,
Actually, the available memory from 'who' is 273196, is this good enough ? Moreover, what do I do if I want to increase the conventional memory of the PC ?
Cheers,
Steve - Hong Kong
At 17 JUN 1998 05:05AM Andrew P McAuley wrote:
Reboot in DOS and run MEMMAKER - see if this helps. As Don says you need more low RAM freed up.
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 17 JUN 1998 08:46AM Don Bakke wrote:
Well I've seen much worse, but it really depends on what your system actually does and whether or not it cleans up after itself when loading various programs. Here are some tips:
1. Run MEMMAKER (or install QEMM, it works well most of the time) as Andrew suggested to maximize conventional memory.
2. If you aren't already doing so, make sure Expanded memory is enabled and load AREV with at least 1-2 MB using the "/X Mxxxx" command line parameters where "xxxx" represents the number of KB. So allocating 2 MB would look like "/X M2048". You can go as high as 4 MB (4096). Verify that expanded memory is working by looking at your WHO window again and two lines underneath Available memory will tell you if Expanded Memory is active or not.
3. Make routines that are seldom used expendable.
4. Avoid using {} when refering to dictionary items that are data fields. Using @RECORD is better since {} loads the program stack.
The last two assume you are the developer. There are certainly other good ideas that I haven't thought of. Andrew, Aaron, Steve, and Victor I'm sure could compile a list five times as long, but these are your best bets for getting started.
dbakke@srpcs.com