home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!nscf!lakes!rock
- From: rock@lakes.trenton.sc.us (Rockerboy)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: HostileTakeOver of Amiga OS
- Keywords: flame bait lives here
- Message-ID: <wyaywB7w165w@lakes.trenton.sc.us>
- Date: Wed, 06 Jan 93 05:28:55 EST
- References: <1993Jan4.193325.11793@cybernet.cse.fau.edu>
- Reply-To: rock@lakes.trenton.sc.us (Rockerboy)
- Organization: Lakes Public Access
- Lines: 24
-
- spc@pineal.math.fau.edu (Sean 'Captain Napalm' Conner) writes:
-
- > (donning asbestos long johns in preparation of a potential flame-a-rama)
- >
- > I'm currently trying to write some code to take over the Amiga system from
- > the OS, do what ever I want to the hardware, and then return the system back
- > to the OS in as much of the same state as it was before I took it over.
- >
- > So, what I'm wanting to know, is what exactly do I need to do to (in as
- > friendly a mannor as possible) to take over the system from the OS. Code
- > fragments (in any language) would be nice, as well as possible
- > warnings/cavets/etc ... that may be required.
- >
-
- No! No! Don't do it! It's _evil_, don't you understand! My _GOD_,
- don't you recognize the damage your programming will do!? You'll ruin
- the entire future of Amiga if you do this, so _don't_!
-
- But if you really want to, the simplest way is to simply shut down
- interrupts (after preserving them), redirect vectros, preserve the system
- copper lists (see graphics/gfxbase.i for details on that). I like to pop
- up a requestor warning the user I'm taking over his machine, too.
- Allocate any RAM you need, then shut down the OS as mentioned above, do
- your thing, put everything back like you found it, and you're done.
-