home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os9
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!torn!watserv2.uwaterloo.ca!watserv1!norton.uwaterloo.ca!bcwhite
- From: bcwhite@norton.uwaterloo.ca (Brian C. White)
- Subject: Re: Need ideas on gpp problems
- Message-ID: <BzJDqK.LHz@watserv1.uwaterloo.ca>
- Sender: news@watserv1.uwaterloo.ca
- Organization: University of Waterloo
- References: <1992Dec4.150851.1@skyler.mavd.honeywell.com> <1gqd5kINNdkp@agate.berkeley.edu> <1992Dec19.054041.3991@microware.com>
- Date: Sun, 20 Dec 1992 02:32:43 GMT
- Lines: 20
-
- In article <1992Dec19.054041.3991@microware.com> smcgee@microware.com (Scott McGee) writes:
- >One trick I found for "sometimes" getting around such problems is to do a
- >shell #1000000
- >just before a command that needs a lot of ram. That will boot all the sticky
- >modules out of memory but still fail for lack of mem, resulting in a null
- >command. Cute trick. (I got it from my boss!)
-
- I always use "unlink #99999" just because I like the idea of "unlinking
- memory".
-
- Brian
-
- -------------------------------------------------------------------------------
- INTERNET: bcwhite@sunee.uwaterloo.ca |
- DELPHI: BrianWhite (@delphi.com) | #include <disclaimer.h>
- COMPUSERVE: 70313.3344 (@compuserve.com) |
- -------------------------------------------------------------------------------
- Any given program contains at least one bug and can be shortened
- by one instruction. Therefore, all programs can be
- shortened to one instruction that won't work.
-