pf@cpsc53.UUCP (Peter Fry) (05/14/87)
Quick question: I am using the timer.device (UNIT_VBLANK). Do I have to cancel outstanding timer requests before closing the device and exit'ing? [Of course.] OK then, how? I would prefer a command that caused all outstanding requests to be returned with an error status, CMD_FLUSH would be great - if it was supported by the device. ( The following options are not available to me: 1) Wait for all outstanding requests to return. (Next week option.) 2) Do not issue requests that will not complete by the end of the program. (Precognition option) ) I would prefer not to have to maintain my own list of (potential) timer requests and do the messy sums myself - considering the driver must contain the code to do that already. Peter C. Fry at AT&T CPSC, Atlanta GA ihnp4!cpsc53!pf "Activate the fail-sXAL S AN>
dillon@CORY.BERKELEY.EDU (Matt Dillon) (05/15/87)
>I am using the timer.device (UNIT_VBLANK). Do I have to cancel outstanding >timer requests before closing the device and exit'ing? >[Of course.] Of course. >OK then, how? AbortIO() + WaitIO() >I would prefer a command that caused all outstanding requests to be returned >with an error status, CMD_FLUSH would be great - if it was supported by >the device. Sorry, no go. You have to keep track of outstanding requests yourself. Using the Amiga library support, you would have to AbortIO() + WaitIO() each outstanding request before closing the device. I posted a package a while back called DIO which does what you want. I will attempt to send it to you via mail. -Matt