On 2 Jan 2004 at 11:51, [EMAIL PROTECTED] wrote: (...) > > Since the original IOP.RPTR asks for D2.B to be set, does this not mean that old > programs > calling the routine might find peculiar things happening? For example, the contents > of D2.L could > have $FF as the top byte. D2 might have been -1 before D2.B was set with the > required pointer > events return. In that case any job event sent to the program would cause a spurious > return. > > What steps have been taken to prevent this?
I've just come back - it seems to me that these are 2 different calls .RPTR and .RPTRT. Only the second has the additional parameters (from the start). So no overlap or problem there! Wolfgang
