Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: Mike Farren Tutorial. Message-ID: Date: 8 Apr 91 19:33:05 GMT References: <18ec731b.ARN0f5b@icoast.UUCP> <2194@pdxgate.UUCP> <24045@well.sf.ca.us> <1991Apr7.150747.2338@sugar.hackercorp.com> Organization: Not an Organization Lines: 30 In article <1991Apr7.150747.2338@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >In article <24045@well.sf.ca.us> farren@well.sf.ca.us (Mike Farren) writes: >> >The OS itself eats up a lot more memory than just the workbench screen. > >> 80K of RAM. By actual test, NOT including Workbench screen memory. > >Wow, I just did the test myself and came up with ~16K. You must have had some >extra stuff running. >-- >Peter da Silva. `-_-' >. I just booted a 1MB A500 (one floppy) with the 1.3.2 workbench disk and came up with 467416 CHIP & 483568 FAST, or a total of 97K used including the normal, non-interlaced (default) workbench screen which takes ~32. That was by breaking out of the boot sequence. Running a memory flush, you get another 1K freed up. The AVAIL program takes 6K, and the CLI, including stack, around 5K. So, the grand total used by the OS if you boot a game and close the workbench screen is 52KB, leaving ~460KB free on a 512K machine. -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA