🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.lang.basic
Article #219

Re: QBX Memory Problems

#219
From: Brian Wheeler
Date: Sun, 08 Nov 1992 18:36
39 lines
2742 bytes
In <9211052103.AA07580@horton.jhuapl.edu> randy@horton.jhuapl.edu (Randall L. Schrickel NDM) writes:

>The application I'm working on is rather large (16,000 lines) and is getting
>rather difficult to handle under QBX. Specifically, running out of memory.
>The program itself seems to run fine, it's only when I exit the program and
>return to QBX that I get "out of memory" errors. I have looked at the docs and
>Winer's book to death. I print out all the fre numbers (-1, -2, -3, "foo", 
>and foo$) plus STACK before and after each array DIM, but haven't learned 
>anything from that. Actually, I learned that most of the numbers DON'T change -
>which doesn't seem right. Changing some string arrays from fixed length to 
>dynamic (which I expected to free up some DGROUP) only made things worse (it
>then died with "out of memory" during the execution, when it tried to dim one
>of the string arrays). I'm running on a machine with 8 Mb, qemm, dos 5, and I
>use the /ea switch when starting QBX (no huge arrays). Other people I've talked
>to say it must be DGROUP, but my fre() experiments have not shown this to be 
>necessarily true. Any other suggestions? Does VB/DOS handle memory any better?
>I'm now spending all of my time trying to figure out this problem instead of
>writing and debugging new code!

>much thanks - randy@aplcomm.jhuapl.edu

try using the /ah (arrays high) and /nof (nofrills) switches at the command
line.  Also put "rem $static" (it might be "rem $dynamic"  I can never remember
which one).  That should let you use more memory.

/Nof - takes away some of the fun stuff like help out of QBX...that way there
	is more memory for code/data
/ah - puts arrays into the far heap.  rem $static (like before, it may be
	rem $dynamic.  Gimme a break..its been awhile :) will make the data
	space be allocated at compile time, not at run time.

Hope this helps.
Its not ALL that quirky....
Brian Wheeler
-- 
******************************************************************************
* Brian 'Nautical' Wheeler - These are my opinions, do you hear me?  MINE!
* "Wombats are our friends" - Me
******************************************************************************
Technical Details
Message-ID: <BxEuD6.Ao8@usenet.ucs.indiana.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!destroyer!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!silver.ucs.indiana.edu!bdwheele
References: <9211052103.AA07580@horton.jhuapl.edu>

Show Full Headers
Complete Article Headers
Newsgroups: alt.lang.basic
Path: arc1-ca.pugleaf.net!sparky!uunet!destroyer!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!silver.ucs.indiana.edu!bdwheele
From: bdwheele@silver.ucs.indiana.edu (Brian Wheeler)
Subject: Re: QBX Memory Problems
Message-ID: <BxEuD6.Ao8@usenet.ucs.indiana.edu>
Sender: news@usenet.ucs.indiana.edu (USENET News System)
Nntp-Posting-Host: silver.ucs.indiana.edu
Organization: Indiana University
References: <9211052103.AA07580@horton.jhuapl.edu>
Date: Sun, 8 Nov 1992 18:36:42 GMT
Lines: 39