Thanks again for the logs!
I've taken a look to the disassembled code of the 1.3 version to see how the busy interrupt is installed and I've seen that there is code to install the interrupt handler in the VBI too. Then I've seen that I was fooled to think that the driver was using the busy interrupt because I saw the code there but if I read the code correctly in fact the VBL interrupt is used. If I had direct access to the hardware I'd go further but I think now the driver is good enough. If the 1.3 version author decided to use the VBL instead of the busy interrupt he had good reasons
. Just in case I've attached a new driver for the busy interrupt because I saw in the disassembled code (again if I read it correctly) that he installs the interrupt handler first with Setexec() and then with Mfpint(), I thought that one should use one method or the other but let's try this way as a last resort.
Because I'm going to commit the code with the split VBL handler I'd like to test it in the Falcon (we only test it in the ST), it should be ok but to be 100% sure that the code pushed in the repo is working.
And finally could you pack the contents of the disk with which you're doing the tests in your ST and send it to me please, so I can try to replicate the pinging issue if I reach around a ST with 4MB of memory.
Thanks a lot for your patience!
You do not have the required permissions to view the files attached to this post.