home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!unix!clipper!kontos
- From: kontos@clipper.ingr.com (Thorne Kontos)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Big mistake - A compromise (of sorts)
- Keywords: Lack of new AGA hardware manual
- Message-ID: <1992Dec18.211223.29630@clipper.ingr.com>
- Date: 18 Dec 92 21:12:23 GMT
- Organization: Intergraph Advanced Processor Division - Palo Alto, CA
- Lines: 23
-
-
- Since I believe I started this thread, let me put forth a compromise
- solution. There are two classes of people who will continue to write
- software for the Amiga. The professional programmer who is attempting to
- create a piece of software that may become a viable commercial product
- is one of these. The other is the hardware hacker/demo coder who writes
- "demos" for fun. The obvious solution given that Commodore does not wish
- to release the AGA specs, is to release code that will allow the hacker
- to bang the hardware, yet return to the normal OS when the demo is
- finished. A generic piece of code that covers all Amigas (regardless of
- configuration) would be perfect. In this manner, the demo coders can happily
- bang the hardware all they want, but by using this snippet of code, the
- computer can be returned to its "normal" state, without having to do
- the three finger salute and reboot the machine which is so prevalent among
- the current demos that I have seen. So what do you think?
- IMHO, this solution works well, and satisfies all. Commodore does not
- have to release the AGA specs. Demo coders will be able to continue to code
- demos, but they will be OS friendly demos. Professional programmers can and
- will continue to use the normal OS function calls.
-
- Thorne K. Kontos
- System Engineer
- Intergraph A.P.D.
-