Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!COGSCI.BERKELEY.EDU!bryce From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) Newsgroups: comp.sys.amiga Subject: Re: Memory loss problem Message-ID: <8707220707.AA04457@cogsci.berkeley.edu> Date: Wed, 22-Jul-87 03:07:05 EDT Article-I.D.: cogsci.8707220707.AA04457 Posted: Wed Jul 22 03:07:05 1987 Date-Received: Fri, 24-Jul-87 01:50:48 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: Institute of Cognitive Studies, UC Berkeley Lines: 29 In article <129@jc3b21.UUCP> fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes: >In article <2133@cbmvax.UUCP>, andy@cbmvax.UUCP (Andy Finkel) writes: >> >> ...you could use the hidden Workbench menu item FlushLibs. >> andy > > Boy, there sure are a lot of undocumented or "hidden" features for >this machine. How do you make FlushLibs appear on the Workbench menu? Andy mentioned it in the message just before the one you responded to. From any cli type: loadwb -debug When the dust settles there will be a new "invisible" workbench tool menu. The menu is unlabled and exists just to the right of all the other menu titles. The "debug" option dumps you to a debugger, but you need a terminal attached to the serial port at 9600 baud to use it. The "flushlibs" option causes all resident libraries (and fonts, probably) that have no active users to be kicked out of memory. ----------------------------- |\ /| . Ack! (NAK, EOT, SOH) {o O} . ( " ) bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce U "Success leads to stagnation; stagnation leads to failure."