It turns out this is linked to an earlier 'wait_for_bsy_to_assert' modification that I made. I've actually updated this piece of code a couple of time. Originally, ADFS would get hung up in this code when trying to access a non existent drive. To get around this I initially added a timeout. I then needed to further update this code to get the *BYE command to function correctly. When I made this further mod, I actually got rid of the timeout and the code would generate a 'Not found' error if BSY was not asserted immediately, otherwise it would continue. That all seemed to work fine with my real HDDs, but not with BlueSCSI, which must take a little bit longer to assert BSY. I've reintroduced a short timeout loop to give the BlueSCSI time to assert BSY, and that seems to have fixed the problem.I'm now going to have to figure out why I get the 'No directory' error message with my patched ADFS...
The only thing I'm not clear about yet, is why I was getting the 'No directory' error, and not getting the 'Not found' error, so I'm still going to have to do some further work on this.
It has also thrown up another issue with BlueSCSI. If I try to access a non existent drive, BlueSCSI seems to get itself a bit locked up. The only way to unlock it is to either reset the beeb, or mount a real SCSI drive first. I'm in discussions with the BlueSCSI folks over on discord about that, although I haven't ruled out a further ADFS issue either.
Statistics: Posted by KenLowe — Tue Mar 04, 2025 11:30 pm