Re: Mysterious 1541 behaviour

Maybe, the bug is on the computer's side.  Maybe, after sending a command 
to the drive, the computer is tricked into thinking that the drive already 
"strobed" the DATA line.  So, it prematurely reads the parallel bus.

Maybe, there is a race between the two devices -- which one gets to the bus 
first?  If there is no delay, then the drive wins.  If there is a delay, 
then the computer wins -- but, it reads the bus's idle state, instead of a 
valid byte.

The drive then puts its first byte on the bus before the computer 
acknowledges the false byte.  The drive thinks that the acknowledgement  is 
for its valid byte.  So, it happily sends the second byte.


       Message was sent through the cbm-hackers mailing list