home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!bunyip.cc.uq.oz.au!news.qut.edu.au!qut.edu.au!podesta
- From: podesta@qut.edu.au
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: New hardware reference guide?
- Message-ID: <1992Nov18.134641.58767@qut.edu.au>
- Date: 18 Nov 92 13:46:41 EST
- References: <1992Nov15.104025.10090@sth.frontec.se> <1992Nov16.130752.18379@imada.ou.dk> <OAHVENLA.92Nov17002933@lk-hp-4.hut.fi>
- Organization: Queensland University of Technology
- Lines: 32
-
- In article <OAHVENLA.92Nov17002933@lk-hp-4.hut.fi>, oahvenla@snakemail.hut.fi (Osma Ahvenlampi) writes:
- > In article <1992Nov16.130752.18379@imada.ou.dk> breese@monet.imada.ou.dk (Bjoern Reese) writes:
- > [...]
- >>doesn't release a new Hardware Ref Guide, featuring the AGA
- >
- > This is the whole point. C= won't release the Hardware information, because
- > that would mean saying that it's OK to directly access hardware, when it's
-
- I don't get it. What's the big deal????
- Why don't Commodore just release it and say something like:
-
- "BANGING THE HARDWARE IS NOT UPWARDLY COMPATIBLE"
-
- Then all of us who don't give a damn about upward compatibility
- (ie. in demos and some games) can write our demos and have fun, and
- those who want to write software that will last forever can go through
- the OS.
-
- People have argued that you should write a ECS version, using hardware, and
- include an OS friendly AGA version. WHY??? If your gonna go to all that
- trouble, just write an ECS version, and change the hardware routines
- for the AGA versions. Even machine code can be modular :) If a new machine
- comes out, we insert new code. This way we are always getting the most out
- of the system...rather than just wasting MIPS by going through the OS.
-
- I mean the OS is GREAT. I love it. It's one of the reasons that Amiga rules..
- but its a development environment, not a demo or game environment.
-
-
- James.
-
- Disclaimer: The above opinions are mine...obviously
-