Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!well!farren From: farren@well.sf.ca.us (Mike Farren) Newsgroups: comp.sys.amiga.programmer Subject: Re: Mike Farren Tutorial. Message-ID: <24045@well.sf.ca.us> Date: 5 Apr 91 03:38:49 GMT References: <20198@cbmvax.commodore.com> <18ead851.ARN0f31@icoast.UUCP> <1991Apr2.002244.11549@cunixf.cc.columbia.edu> <18ec731b.ARN0f5b@icoast.UUCP> <2194@pdxgate.UUCP> Lines: 35 bairds@eecs.cs.pdx.edu (Shawn L. Baird) writes: >hbrinch@icoast.UUCP (Henrik Brinch) writes: >>Ethan Solomita writes: >>> take up 100K+, but then the workbench screen can always be >>> CLOSED! >>Why SHOULDN'T it be closed, I would say it's pretty strange to kill the >>system and leave the WB screen open ! >I think he was talking about the OS routine to close the Workbench screen. >There is only one problem. An application can not count on the ability of >the Workbench screen to be closed. Sure you can. If you really need the extra memory, you are perfectly within your Amiga-friendly rights to complain about it and ask for it. >Now granted, you could tell the user to go remove any offending >programs, but is this really what you want to sell to a consumer? Well, the only time it's a problem is if you need as much memory as possible. This means a 512K machine - and I don't see any problem with saying "Hey, I need a lot of memory" as long as you give the user the choice, instead of taking it all on yourself. >The OS itself eats up a lot more memory than just the workbench screen. >Although, granted, it's pretty small considering what it does (mostly >because a lot of it is in ROM). 80K of RAM. By actual test, NOT including Workbench screen memory. -- Mike Farren farren@well.sf.ca.us