sivagnan@handel.ColoState.EDU (Vasanthan Sivagnanadasan) (06/13/88)
I am running MultiFinder 1.0 under finder 6.0 System 4.2 on my Mac SE with 1 Meg of memory. When I open a DA from the apple menu I just get the beep and the DA will not open. But if I just run the finder it opens. How can I solve this problem? S. Vasanthan sivagnan@handel.cs.colostate.EDU vasa@csugreen.BITNET
gillies@uiucdcsp.cs.uiuc.edu (06/14/88)
Hold down the command key to open a DA when memory is low. The key
causes MultiFinder to start the DA in the application's partition
(preallocated memory), not in some new allocation (that fails because
the heap is nearly full). This is documented in your macintosh user's
manual, I believe.
If this doesn't work for you, you might try switching to an
application with plenty of free memory (go to the word processor and
close all your windows?) and try it again.
Don Gillies {ihnp4!uiucdcs!gillies} U of Illinois
{gillies@cs.uiuc.edu}drc@dbase.UUCP (Dennis Cohen) (06/14/88)
In article <6613@sigi.Colorado.EDU>, sivagnan@handel.ColoState.EDU (Vasanthan Sivagnanadasan) writes: > > I am running MultiFinder 1.0 under finder 6.0 System 4.2 on my Mac SE > with 1 Meg of memory. When I open a DA from the apple menu I just get > the beep and the DA will not open. But if I just run the finder it > opens. How can I solve this problem? > There are really two ways of dealing with this, the first being the most painful. The painful method is to get more memory. The not so painful, but annoying way is to hold down the Option key when selecting the DA from the Apple menu. This will cause the DA to load in the heap of the currently executing application. Not holding down the Option key causes the launch of the DA Handler. If you are running some application along with the Finder under MultiFinder, it is quite likely that there will not be enough memory to load a DA such as DiskTop or Acta, which require a fair amount of memory to do their magic. Dennis Cohen Ashton-Tate Macintosh Division dBASE Mac Development Team -------------------------- Disclaimer: Any opinions expressed above are _MINE_!
levin@bbn.com (Joel B Levin) (06/16/88)
In article <374@dbase.UUCP> drc@dbase.UUCP (Dennis Cohen) writes: (In article <6613@sigi.Colorado.EDU>, sivagnan@handel.ColoState.EDU (Vasanthan Sivagnanadasan) writes: (> . . . When I open a DA from the apple menu I just get (> the beep and the DA will not open. But if I just run the finder it (> opens. How can I solve this problem? ( (There are really two ways of dealing with this . . . The not so painful, but (annoying way is to hold down the Option key when selecting the DA from the (Apple menu. . . . A note to those using Suitcase-- If you hold Option while selecting the Apple menu, you don't see any DAs, just the application list. The trick is to FIRST select the Apple menu, THEN press Option, and hold it until you have let the mouse button up over the DA selected. /JBL UUCP: {backbone}!bbn!levin USPS: BBN Communications Corporation ARPA: levin@bbn.com 50 Moulton Street POTS: (617) 873-3463 Cambridge, MA 02238
src-1fd@thoth1.berkeley.edu (06/17/88)
[ computer beeps under multifinder when one tried to load DA ] I had this same problem when I first installed multifinder on my Mac. Not having the manuals, (which cost $$$) I was in the dark. It turns out that Multifinder needs a system file called 'DA Handler' which is loaded much like an application and then the DA's are put in this process's heap. Without the file, multifinder looks for it, and not finding it, simply beeps. If you were out of memory, the DA handler would tell you so. You should have this file as part of the Multifinder system disks. If not, I suppose I can send it to you. (That's ok, right?, or is that not all right any more?) Good Luck, Robert Pfile src-1fd@bartleby.berkeley.edu
brewer@clio.las.uiuc.edu (06/18/88)
gillies at uiucdcsp.cs.uiuc.edu (Don Gillies) writes: > Hold down the command key to open a DA when memory is low. The key > causes MultiFinder to start the DA in the application's partition > (preallocated memory), not in some new allocation (that fails because > the heap is nearly full). This is documented in your macintosh user's > manual, I believe. > > If this doesn't work for you, you might try switching to an > application with plenty of free memory (go to the word processor and > close all your windows?) and try it again. > > Don Gillies {ihnp4!uiucdcs!gillies} U of Illinois > {gillies@cs.uiuc.edu} I think you mean the OPTION key, not the command key. Robert Brewer brewer@clio.las.uiuc.edu {ihnp4 | convex | pur-ee}!uiucuxc!clio!brewer