Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!purdue!haven!mimsy!mojo!russotto From: russotto@eng.umd.edu (Matthew T. Russotto) Newsgroups: comp.sys.mac.misc Subject: Re: What can't it do? Loss of... Keywords: Multi-Finder, multitasking, Finder Message-ID: <1990Jul12.134006.368@eng.umd.edu> Date: 12 Jul 90 13:40:06 GMT References: <82023@tut.cis.ohio-state.edu> <2619@network.ucsd.edu> Sender: news@eng.umd.edu (The News System) Organization: College of Engineering, Maryversity of Uniland, College Park Lines: 27 In article <2619@network.ucsd.edu> pbiron@weber.ucsd.edu (Paul Biron) writes: > >It's even more of a misnomer than you think. >When you switch between applications with Multi-Finder, the >application you WERE using goes to sleep. I may be mistaken >here, I don't get to use Multi-Finder very often because none >of the Macs that I work on have enough memory. (If I am I'm >sure someone will point it out :-) You ARE mistaken, as anyone who has downloaded a file, decoded a Stuffit file, and used Microsoft Word all at the same time knows. >To be truely multi-tasking, an operating system must allow >multiple processes (or applications) to be running AT THE >SAME TIME (well, actually they each get a time slice). This happens, though the foreground application has to be willing to give up a time slice (by calling GetNextEvent or WaitNextEvent) > >The closest thing to true multitasking I've seen on a Mac >is the print spooler. You haven't looked hard enough. -- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu ][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions? Hey! Bush has NO LIPS!