Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ncar!boulder!uswat!uswmrg2!steve From: steve@uswmrg2.UUCP (Steve Martin) Newsgroups: comp.sys.mac.system Subject: Re: Killing the Finder to free up more RAM under Multifinder? Message-ID: <1990May29.142512.25537@uswmrg2.UUCP> Date: 29 May 90 14:25:12 GMT References: <16797@phoenix.Princeton.EDU> Reply-To: steve@uswmrg2.UUCP (Steve Martin) Organization: US West Marketing Resources Group, Aurora CO. Lines: 17 In article lewin@zariski.husc6 (Alex `Reaper' Lewin) writes: > >The way that works for me is to switch to Finder (while another app is >running in MultiFinder), hit the programmer's switch, and do an >ExitToShell() from MacsBug, i.e., type "es". This usually works (fails if >you happen to catch the Mac while it is SystemTask()ing I guess), and >doesn't require compiling anything. I guess it's kind of a hack, but hey. I tried the FKEY method discussed here and find that it works well. It should give the same results as this MacsBug method, but the FKEY will only be called when the system is waiting for an Event, so there should be no possible problem with interupting and interupt! -- Steve Martin | Nothing I say can be held against U S West Marketing Resources Group | Me or my employer! (...!rutgers!bellcore!uswat!uswmrg2!steve)