Xref: utzoo comp.sys.amiga.applications:745 comp.sys.amiga.advocacy:2224 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!lll-winken!taurus!aldebaran!schweige From: schweige@aldebaran.cs.nps.navy.mil (Jeffrey M. Schweiger) Newsgroups: comp.sys.amiga.applications,comp.sys.amiga.advocacy Subject: Re: Kickstart 2.0 Message-ID: <2136@aldebaran.cs.nps.navy.mil> Date: 23 Apr 91 18:15:05 GMT References: <1991Apr22.084438.1975@rulway.LeidenUniv.nl> <91112.172405IO91461@MAINE.BITNET> <2133@aldebaran.cs.nps.navy.mil> <111465@tut.cis.ohio-state.edu> Reply-To: schweige@taurus.cs.nps.navy.mil (Jeffrey M. Schweiger) Followup-To: comp.sys.amiga.advocacy Organization: Naval Postgraduate School, Monterey CA Lines: 69 In article <111465@tut.cis.ohio-state.edu> watters@anaconda.cis.ohio-state.edu (david r watters) writes: schweige@cs.nps.navy.mil (Jeffrey M. Schweiger) writes: < <>Now, for more conjecture and opinion. I happen to agree that 2.0 should not <>be released until it's ready. Releasing an intermediate version of it, was, <>IMHO, necessary for the A3000, as otherwise some of the 3000's features, not <>presently part of other Amigas (ECS Denise, 2meg Agnus - although MegaChip <>2000 addresses this one). < I would rather wait a little while longer, and allow <>Commodore to get 2.0 right, than to have them get stuck supporting multiple <>configurations. I'm also quite happy that many of the Commodore engineers <>take time to participate on Usenet. They don't have to. <