home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!spool.mu.edu!umn.edu!dell32.ortta.umn.edu!durai
- From: durai@ortta.umn.edu (Durai Venkatasubramanian)
- Subject: Re: Foxpro and Insufficient Memory Errors
- Message-ID: <durai.120.726504552@ortta.umn.edu>
- Lines: 37
- Sender: news@news2.cis.umn.edu (Usenet News Administration)
- Nntp-Posting-Host: dell32.ortta.umn.edu
- Organization: U of Mn
- References: <1993Jan7.222734.20312@nntpd2.cxo.dec.com>
- Date: Fri, 8 Jan 1993 14:49:12 GMT
- Lines: 37
-
- In article <1993Jan7.222734.20312@nntpd2.cxo.dec.com> scott@talguy.cxo.dec.com (Scott Johnson) writes:
- >From: scott@talguy.cxo.dec.com (Scott Johnson)
- >Subject: Foxpro and Insufficient Memory Errors
- >Date: Thu, 7 Jan 1993 22:27:34 GMT
-
- >Is there a command I can run ocassionally during the execution of the program
- >which will cut down and possibly reclaim unused memory? I was hoping there
- >was some sort of garbage collection routine that can be invoked once in a
- >while during the execution cycle of the application.
-
- 4mg to me is quite a lot of memory. You should not get "insufficient
- memory" errors, unless you have tons of TSRs out there, or you are using
- some kind of task switcher to manage multiple applications. Assuming you
- can get rid of unwanted TSRs,...may be you can try one or more of the
- following.
-
- 1. Is DOS loaded high ?
- 2. Are you using foxpro extended version ? <it will take advantage of upper
- memory>
- 3. Are you using any expanded memory managers ? <ms-dos includes himem.sys,
- and emm386 that help you access the upper memory area. make sure you use
- them, unless you want third party memory managers. again, if you are
- using emm386, you should have device=emm386.sys in your config.sys,
- otherwise the 3mg of memory will be ignored>
- 4. mem command (dos) will display the amound of used and free memory in
- the system (mem has several switches)
- 5. in your config.fp, if "dosmem = on", foxpro will use all dos memory with
- any extended memory
- 6. check you config.sys for files, buffers entries <buffers hog memory>
- 7. sys(12) : remaining memory
- sys(23) : ems usage
- sys(24) : ems limit
- sys(1001): foxpro's memory
- sys(1016): memory used by user objects
- 8. if you are using foundation read (or any other type of event driven
- interface), you might use up a lot of memory
-
-