papa%pollux.usc.edu@UDEL.EDU (10/04/88)
Received: from CUNYVM by CUNYVM.BITNET (Mailer X2.00) with BSMTP id 5691; Sun, 02 Oct 88 01:10:17 EDT Received: from UDEL.EDU by CUNYVM.CUNY.EDU (IBM VM SMTP R1.1) with TCP; Sun, 02 Oct 88 01:10:14 EDT Received: from Louie.UDEL.EDU by Louie.udel.EDU id aa03247; 1 Oct 88 22:08 EDT Received: from USENET by Louie.UDEL.EDU id aa03147; 1 Oct 88 22:04 EDT From: Marco Papa <papa@pollux.usc.edu> Subject: Updating to 1.4 (was Re: Upgrading to 1.3) Message-ID: <12503@oberon.USC.EDU> Date: 2 Oct 88 00:10:59 GMT Organization: Felsina Software, Los Angeles, CA To: amiga-relay@UDEL.EDU Sender: amiga-relay-request@UDEL.EDU In article <7431@gryphon.CTS.COM> mriley@pnet02.cts.com (Mark Riley) writes: >Look, it's MY mistake that I mentioned 1.3 needs a ROM change. This >stems from lack of information about what version does what. Apparently >1.3 is not the version that is going to introduce major functions >that are not compatible with earlier versions. I think this would >be called 1.4, instead. That may be the one to be scared of, who >knows. Yes, 1.4 will include MAJOR ROM changes. 1.3 ROMS only add autoboot support. >As an example, I understand that there is going to be overscan support >in 1.4 (or whatever it's gonna eventually be called.) What's going to >happen when a program wants an overscan screen using this new function >when running on 1.2. It's not going to get it. I'm sorry, but a >message like "SuperProgram V1.0 needs 1.4 in order to run - Sorry, >you're S.O.L.)" just is not going to cut it with me. I've seen >enough of this on the Mac, why must it happen here? People already >can create overscan displays. Makes no sense to me. Concerning OVERSCAN. Up until the last DevCon. Overscan was just a TOTALLY UNSUPPORTED feature. Everybody was doing it his own way. At DevCon Jim Mackraz promised support for overscan in the next ROM change, version 1.4 (due out who knows, 1989?). He also included SOURCE code in the DevCon disk that shows code that runs today and WON'T be supported by 1.4 and code that runs today and that WILL be supported. So now EVERYBODY that is developing software for the Amiga (and 1.4) can find out how to make it in a compatible way, about one year before the real thing (1.4) comes out. If by the time 1.4 comes out, a software manufacturer has not yet updated his software to be compatible with it, it is totally his own fault, not CBMs. I have updated mine. I know of other companies that have done so. For the people that haven't been at DevCon, CBM will provide the DevCon notes and disk (when Lauren?). THis seems to me to be much better than the way "another company" has been updating his "*****finder"-based OS. -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=