home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.amiga.programmer:18249 comp.sys.amiga.hardware:22536
- Path: sparky!uunet!munnari.oz.au!uniwa!newsman!meek
- From: meek@csu.murdoch.edu.au (Lindsay Meek)
- Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
- Subject: Re: HostileTakeOver of Amiga OS
- Date: 7 Jan 1993 22:27:48 GMT
- Lines: 17
- Message-ID: <1iiap4INN648@newsman.csu.murdoch.edu.au>
- References: <1993Jan4.193325.11793@cybernet.cse.fau.edu>
- NNTP-Posting-Host: fizzy.csu.murdoch.edu.au
- Keywords: flame bait lives here
-
- Well, one thing to do before running amok is to own the blitter
- properly using OwnBlitter(graphics.library) and DisownBlitter, and
- waiting for the blitter to finish before doing anything to the chip
- registers. I never had any problems when not using these calls however,
- disabling-the-hell out of everything seems to work fine for all the
- current Amigas (but not any future ones if they generate their own
- interrupts using different chips).
- Make sure you wait for the disk drive to finish writing before
- you disable everything however, otherwise your drive will validate
- and the blocks queued for writing will be lost. Does anybody know a
- commidore unauthorised naughty-bit of code for doing this?
-
- Anarchy rules
- (especially when you have a bug ridden operating system)
- Lindsay
-
-
-