Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!ogicse!pdxgate!eecs!bairds From: bairds@eecs.cs.pdx.edu (Shawn L. Baird) Newsgroups: comp.sys.amiga.programmer Subject: Re: Mike Farren Tutorial. Message-ID: <2194@pdxgate.UUCP> Date: 3 Apr 91 00:44:41 GMT References: <20198@cbmvax.commodore.com> <18ead851.ARN0f31@icoast.UUCP> <1991Apr2.002244.11549@cunixf.cc.columbia.edu> <18ec731b.ARN0f5b@icoast.UUCP> Sender: news@pdxgate.UUCP Lines: 32 hbrinch@icoast.UUCP (Henrik Brinch) writes: >In article <1991Apr2.002244.11549@cunixf.cc.columbia.edu>, 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. If a CLI or other program is running on the workbench (that is, besides workbench itself) the Workbench screen will not close. 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? Your sales would probably drop because of the hassle everyone would have to go to just to run the damned thing. 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). >> -- Ethan >InfoCoast /\ /\_ Henrik Brinch \ cbmehq!cbmdeo!icoast!hbrinch >Technologies /\/ \/ \ Kloevervej 7 \ FidoNet 2:230/112.3 >____________/ \ / \ 2800 Lyngby \ Voice/Fax tel.# +45 42 87 67 23 > / \/ \ Denmark \ "C is SILVER - But ASM is GOLD" --- Shawn L. Baird, bairds@eecs.ee.pdx.edu, Wraith on DikuMUD The above message is not licensed by AT&T, or at least, not yet.