Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.programmer Subject: Re: Mike Farren Tutorial. Message-ID: <1991Apr7.150455.2256@sugar.hackercorp.com> Date: 7 Apr 91 15:04:55 GMT References: <18ead851.ARN0f31@icoast.UUCP> <1991Apr2.002244.11549@cunixf.cc.columbia.edu> <18ec731b.ARN0f5b@icoast.UUCP> Organization: Sugar Land Unix -- Houston, TX Lines: 25 In article <18ec731b.ARN0f5b@icoast.UUCP> hbrinch@icoast.UUCP writes: > BUT judge for yourself, you have from $c0-$7ffff (app. 524000 bytes) > then break the CLI sequence and check your memory (AVAIL you know). > You have the CLI/WB screen (app.(!!!!!) 80K) + the exec/dos system do I > really have to tell you more? I just fired up my Amiga 1000, Workbench 1.3.2. Hit ^D to abort loading, and typed "avail". > If it isn't 200K it's less, but not much less.... still enough memory for > quite some game-effects (levels/sounds etc.). Type Available In-use Maximum Largest chip 421216 94648 515864 420328 fast 0 0 0 0 total 421216 94648 515864 420328 OK, the O/S is using a total of 94648. The workbench screen is overscanned, about 704 by 216. 76032 bytes for that, 1964 for "avail", leaves 16652 bytes used by all system data structures, interrupt vectors, dynamic data used by "avail", etc. Seems significantly less than 200K to me. And you can close the workbench screen without killing the O/S. -- Peter da Silva. `-_-' .