Path: utzoo!utgpu!water!watmath!clyde!burl!codas!mtune!mtgzz!drutx!clive From: clive@drutx.ATT.COM (Clive Steward) Newsgroups: comp.sys.mac Subject: Re: Multifinder 1.0 (w/Macterminal or Word)troubles Message-ID: <6232@drutx.ATT.COM> Date: 16 Dec 87 09:19:52 GMT References: <48@qucis.UUCP> Organization: resident visitor Lines: 42 in article <48@qucis.UUCP>, cordy@qucis.UUCP (Jim Cordy) says: > > The new system/finder/multifinder seem not to work quite right for me. > What am I doing wrong? > > 1) MacTerminal 2.2 crashes the system. > 2) Double clicking on a Word document gets a message about not being able to > find an application for this document. Would someones from Apple and Microsoft like to comment on these? I stopped using MacTerminal 2.2 because it wouldn't boot as part of as Set Startup group without funny messages; and as noted, it does rather seem to crash. Word 3.01 generally works, but after a while, bombola, at least in my experience. Often around saving or printing time, but not necessarily (perhaps that's just the Murphy's law part). Even if it's the only thing (and newly) up under Multifinder besides the finder. The recent note about certain applications loading low on the memory map, I believe, implicates one of our friends here.... Thus, though boot blocks perhaps shouldn't matter, setting my hard disk (45 meg MacBottom) up to 80k over standard, just like the distribution disks for Finder6.0/Multifinder, really helps most situations. I can almost always open das under the Da manager now, and surely have less crashes. Can anyone verify that Word 3.01 is/isn't truly crash-free under heavy use with Multifinder? About all I'm running extra is Suitcase, and for me it's definitely not. Finder 6.0 si, alone under Multifinder, no. It would be nice to know. Heck, even my own programs sometimes do things I think they shouldn't -- just uncovered a bug which would cause a (signal caught and dealt with, at least) bus error in my natural language system for AT&T -- a case where a sentence with a percent sign in it could slip through and get run through a sprintf, thus trying to access wherever a random spot on the stack pointed to. How about it, guys? Clive Steward