Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!news.nd.edu!grumpy.helios.nd.edu!rcook
From: rcook@grumpy.helios.nd.edu
Newsgroups: comp.sys.mac.system
Subject: Re: All about sys 7.0 <long>
Message-ID: <1991Apr15.055431.7509@news.nd.edu>
Date: 15 Apr 91 05:54:31 GMT
References: <BAUMGART.91Mar27172632@info7.esquire.dpw.com> <91087.123233EHYOUNK@MTUS5.BITNET> <1991Apr2.024426.28729@isc.rit.edu> <1991Apr13.014000.29394@sbcs.sunysb.edu>
Sender: news@news.nd.edu (USENET News System)
Reply-To: rcook@grumpy.helios.nd.edu ()
Organization: Univ. of Notre Dame
Lines: 20

In article <1991Apr13.014000.29394@sbcs.sunysb.edu>, dtiberio@eeserv1.ic.sunysb.edu (David Tiberio) writes:
|> In article <1991Apr2.024426.28729@isc.rit.edu> jjwcmp@isc.rit.edu (Jeff Wasilko) writes:
|> >
|>   Another major problem is memory. Mac programs assume that most of the 
|> system memory will be free. When it is multitasking, it will want a big
|> chunk of memory oor it won't work. It may also damage the memory of another
|> program. On an Amiga or a UNIX system, this will never happen. A 10k 
|> application will only use about 10k. Therefor, if you have 1 meg, you can 
|> run that application 100 times!
|> 

On a true multitasking system like OS/2 and unix, a 10K program running 
100 times should take up 10K, plus some overhead for each program to hold
registers and temporary data.  Assuming 1K overhead for each program (not a 
bad assumption for a 10K program) then you could run this program 999 times on
a 1000K system.

Robert Kelley Cook
U. Of Notre Dame '91
  I'm still open to job suggestions . . .