So
@Hunta 's information helped. The magic sauce was changing my FF.CFG to say 'interace = ibmpc' - which is definitely helping. I'm getting the drive recognized, and it ticks along a bit, but then crashes out to the monitor. I'm guessing this is now a hardware fault somewhere.
Current FF.CFG (note the other stuff like fonts and stuff is there because I wanted ot make sure the gotek was reading the FF.CFG. It is)
Code:
host = dec
interface = ibmpc
old-font = 8x16
two-button-action = eject
nav-loop = no
Using DISK0001 from
@czunit 's download (thank you!) - this is what I get:
Code:
Trying DU0
Starting system from DU0
000002
@
Using DISK0000 it just wedges after 'Starting System'
Using DISK0029 it gets to track 6 and just hangs
Note if I use anything else, I get "Non bootable media in drive" - so i guess that's good?
I'm beginning to suspect a hardware fault. I did recently get a spare RQDX3 at VCF, and I just popped that in, but I get the exact same errors.
Some things I can think of trying. I pulled out the TK50 controller, the two DLV11J's, and the DHV11 card to see if they were mucking up the bus. So the stack is simplified (I understand the 'serpentine' layout of cards in QBUS, I think this is right - at least it's doing the exact same thing it was doing before)
KDJ11 (slots 1-2
M7551 (slots 4-3)
RQDX# (slot 5)
The RD53 isn't even cabled in anymore.
I'm down to grasping at straws here. Is my GoTek flaky? (I don't think so, but it's possible. I have another one, but I'd need to put flashfloppy on it). Having this die after 6 tracks of read data off the image doesn't appear to be a problem with the floppy. CPU board? I'm running one that was fully tested by a known VCF person, it passes diagnostics, but maybe there was something weird here, I dunno. Memory tests pass cleanly, so it's not a RAM issue.
I'm honeslty up for a Zoom call if anyone wants to hang out and I can power this stuff up and down a few times and see what the heck I'm doing wrong.