home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.amiga.programmer:18352 comp.sys.amiga.hardware:22625
- Path: sparky!uunet!paladin.american.edu!gatech!nscf!lakes!rock
- From: rock@lakes.trenton.sc.us (Rockerboy)
- Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
- Subject: Re: HostileTakeOver of Amiga OS
- Keywords: flame bait lives here
- Message-ID: <yH31wB5w165w@lakes.trenton.sc.us>
- Date: Thu, 07 Jan 93 17:18:45 EST
- References: <1iiap4INN648@newsman.csu.murdoch.edu.au>
- Reply-To: rock@lakes.trenton.sc.us (Rockerboy)
- Organization: Lakes Public Access
- Lines: 13
-
- meek@csu.murdoch.edu.au (Lindsay Meek) writes:
-
- > 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?
-
- Augh! Yes! You've no idea how many times I've screwed up a disk with my
- source code on it while testing. You know the routine: save the source,
- pop into the monitor to give your code a spin, and you forget that
- _damned_ second write the OS does all the time. Blammo, screwed disk.
- 'Swhy I have a requester pop up asking if it's okay to take over the
- machine. It can really hurt people, otherwise.
-