Xref: utzoo comp.sys.amiga.tech:948 comp.sys.amiga:19924
Path: utzoo!utgpu!water!watmath!clyde!att!mtunx!rutgers!cmcl2!nrl-cmf!ames!lll-tis!lll-winken!lll-lcc!pyramid!cbmvax!bryce
From: bryce@cbmvax.UUCP (Bryce Nesbitt)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: Problem with trackdisk.device
Keywords: Disk, Trackdisk
Message-ID: <3967@cbmvax.UUCP>
Date: 8 Jun 88 17:20:22 GMT
References: <3822@pasteur.Berkeley.Edu>
Reply-To: bryce@cbmvax.UUCP (Bryce Nesbitt)
Organization: Commodore Technology, West Chester, PA
Lines: 12

In article <> koster@cory.Berkeley.EDU.UUCP (Kevin Oster) writes:
|
|I am having trouble accessing the disk hardware directly. It seems that
|there is an interrupt server that works with the trackdisk.device that
|sets up the hardware registers the way it sees fit to set them on a regular
|basis...
|   It's things like this that make me want to murder the Amiga software
|design team.

Maybe you really want to kill the documentation team :-).  There is
a prefect, defined, multitasking mechanism for getting to the disk
hardware.  It's called the "disk.resource", and the RKM contains
documentation for it.  See "disk.doc" and "GetUnit".