home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.misc
- Path: sparky!uunet!spool.mu.edu!agate!usenet.ins.cwru.edu!gatech!hubcap!charlet
- From: charlet@hubcap.clemson.edu (Charles E "Rick" Taylor IV)
- Subject: Re: Gremlins are munching my memory! (FastRam)
- Message-ID: <1993Jan5.181527.13640@hubcap.clemson.edu>
- Organization: Clemson University
- References: <crystal.726198900@glia> <1993Jan5.150348.24088@daimi.aau.dk> <1993Jan5.173028.25995@ra.msstate.edu>
- Date: Tue, 5 Jan 1993 18:15:27 GMT
- Lines: 26
-
- jmpierce@whale.st.usm.edu (Jimmy Malcolm Pierce) writes:
-
- >20659@daimi.aau.dk (Carsten S|rensen) writes:
- >>crystal@glia.biostr.washington.edu (Crystal) writes:
- >>
- >>>I can't find the memory muncher that is eating my Fast RAM :<
- >>
- >>I think that the problem could be that the programs you run open some
- >>.libraries ... Because the libraries are not always flushed from the mem when
- >>they are not used WHICH IS FRUSTRATING :) The solution is to add an argument
- >>to your loadwb command in your startup-sequence. Like "LOADWB -DEBUG" (or is
- >>it "LOADWB DEBUG"?) Anyway, when you do this an extra menu will appear next
- >
- > The 'loadwb -debug' option is on pre-WB 2.04. For WB 2.04 use
- > avail /flush as there is no loadwb -debug in Wb 2.04. DJ.
-
- Hogwash. RTFM, page 8-83. "The -DEBUG option makes a special developer menu,
- Debug, availible in the Workbench menu bar." I also know this is true for
- 2.04 since the first thing I did when I switched from 1.3 is to change the
- LoadWB to a LoadWB -debug. :)
-
- --
- + Rick __ + EMAIL:charlet@hubcap.clemson.edu + //\ + /|\ It's +
- | /aylor | IRC : Tomalek / The Romulan | \X/--\miga 500 | J rainy |
- +-------------+----------------------------------+----------------+----------+
- + "Every Girl Already Has A Boyfriend" --- Murphy's Law Of Dating... +
-