home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!smurf.sub.org!easix!dino.dinoco.de!quax.GUN.de!peti.GUN.de!simons
- From: simons@peti.GUN.de (Peter Simons)
- Message-ID: <5b4.ANN@peti.GUN.de>
- Date: Tue, 08 Dec 1992 23:25:42 CET
- Organization: * Private Amiga Site Bonn - Member of Individual Network e.V. *
- Newsgroups: comp.sys.amiga.programmer
- Distribution: world
- Subject: Re: Hardware hacking....
- References: <29067@castle.ed.ac.uk>
- X-Newsreader: Ann 0.10
- Lines: 29
-
- In article <29067@castle.ed.ac.uk>,
- alexm@castle.ed.ac.uk (Alex McLean) writes:
-
- > [...] The OS is simply useless for arcade/3D games etc.Sure,if you
- > want to have a 'nice' prog that exits well,use the OS calls,allocate
- > memory,call LFOForbid etc... But games/Demos need the hardware
- > direct-Kill the OS,use the hardware the way you want. [...]
-
- You're absolutely wrong!! It's okay to program the hardware directly, BUT
- you definetly have to know what you're doing. With lots of effects,
- vectors, scrollers, stars etc... you may impress the 16-year-old kids,
- but anyone who owns a harddisk or an accelerator-board will delete your
- demo immediately, if it doesn't return correctly.
-
- What's the problem with allocating the memory you need? Why don't
- disabling the multitasking via Disable(), going to the hardware and
- enabling it afterwards again?
-
- I used to "code" for the scene some months (years??) ago and I can
- proudly say that all of my demos work fine on my new machine.
-
- bye, Peter
-
-
- --
- ____ ____ ____
- /___ /__ /\ / / INTERNET: simons@peti.GUN.de
- ____//___ / \/ / FIDONET: 2:242/7.25
- to you by Peter Simons VOICE: 0228 / 746061
-