Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!midway!clout!chinet!miroc!reaper!mmm
From: mmm@reaper.Chi.IL.US (Michael Marvin Morrison)
Newsgroups: comp.sys.amiga.hardware
Subject: Re:  NEW Commodore Upgrade for A1000 Owners!
Message-ID: <mmm.1495@reaper.Chi.IL.US>
Date: 25 May 91 01:30:02 GMT
References: <1991May07.224440.2764@ariel.unm.edu> <D4RL21w161w@nstar.rn.com> <1991May8.012740.26800@cunixf.cc.columbia.edu> <1991May13.172116.1@wombat.newcastle.edu.au> <21865@cbmvax.commodore.com>
Lines: 46

In article <21865@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>In article <1991May13.172116.1@wombat.newcastle.edu.au> c8927218@wombat.newcastle.edu.au writes:
>>Who buys a 3000 for games ???
>
>	I do (well, use it).  Indy 500 on a 3000 is _great_ (IMHO).
>
>>I haven't found a utility that won't run on the 3000 yet (SA4D requires 1.3)
>>, although heaps of games don't work...but who cares ?
>
>	SA4d and SA4djr both will be functional in the next 2.0 release
>(their bug was kludged around as of beta 37.86 or so).

I have a dumb question.. If the software doesn't run because of a bug in it,
then why is Commodore 'kludging' the ROMS?  Agreed that it is a DAMN big
inconvience to obtain an upgrade (both from user & vendor standpoint) but
if C= knows what the bug was then why not just report it to the company and
have them fix it.  Now if said bug was in 2.0 then a FIX is in order, not
a kludge (obviously).  Too many kludges spoil the ROMS.  IMHO.
I simply can't imagine a company not willing to fix a piece of productivity
software because it doesn't run under the new OS, especially if the problem
was THEIR fault in the first place.  Maybe if Commodore didn't have to 
debug other peoples code, 2.0 would have been out by now.  Again IMHO.  And
again assuming that it wasn't a prob with 2.0.

>	In earlier 2.0 releases (2.00-2.03), a fair percentage of games didn't
>run.  A few careful kludges and a LARGE percentage run under 2.0.  Those
>that don't work with '030's are no better than before, of course.

Hopefully these kludges don't effect the speed of the new OS, as that should
not be comprmised.  Actually, I am interested in knowing what some of these
people did.  They must have been jumping directly into the ROMS at some point,
for disk access?, to snag some known code?

Sorry to come down like this, but it has been burning me for some time now.
What debugging tool does C= use to find out all of these goodies?

>-- 
>Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
>{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
>Disclaimer: Nothing I say is anything other than my personal opinion.
>"No matter where you go, there you are."  - Buckaroo Banzai

--
Michael M Morrison              /|                            |\
mmm@reaper.chi.il.us <or>      | |     Cold Steel on Ice      | |
reaper!mmm@miroc.chi.il.us      \|                            |/