Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!ukma!seismo!dimacs.rutgers.edu!rutgers!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: trackdisk diskchange interrupt hassle
Keywords: xyz
Message-ID: <18416@cbmvax.commodore.com>
Date: 1 Feb 91 07:15:50 GMT
References: <1991Jan31.103957.18207@phoenix.pub.uu.oz.au>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 27

In article <1991Jan31.103957.18207@phoenix.pub.uu.oz.au> billy@phoenix.pub.uu.oz.au (Jeff Coleman) writes:
>  i am having hassles getting the trackdisk diskchange interrupt stuff
>  to work. Basically what i do i open the device (most usual stuff here)
>  setup a request structure for TD_ADDCHANGEINT as in the rkm pp894
>  sendio it off..
>  and i never seem to actually get into the interrupt handler routine at all
>  when i change the disk. which is a bit strange.

	It does work (the FS uses this to get notification).

>  i notice that CBM say 1/2 of this doesn't work (the removal of the interrupt
>  handler) under 1.3..i'm using 1.3.2 should the interrupt stuff still work??
>  does anybody have a(short) working example of some code (i have read Messydos
>  src , i was hoping there was something a bit clearer) that demos this 
>  stuff???

	RemChangeInt doesn't work in <2.0.  There is a workaround in the
Autodoc or RKM's (Forbid(); Remove(); Permit() if I remember right).  That
workaround is still supported under 2.0, but under 2.0 RemChangeInt works
also.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)