Thanks to all.
I have done the cleanup thing, as this board has acid damage from the leaking battery problem. Both 2000's I have were given to me for free, and the damage already existed on both of them.
I have also replaced the two sockets that showed any oxidisation problems, ROM & 68000.
I have checked by swapping out all custom chips, power supplys and Floppy drives and the problem exists with floppy drives connected only to the affected board.
When I had the machine in bits and was testing things, I know that I put the floppy drive cable on backwards at the Mobo end. It also could have been on for sometime before I realised, as the drive lights were not facing me and I didn't see the light on DF0: was stuck on.
But hey, as I said earlier the numbers on the plug 33 & 34 have to go to where pin 1 is labled on the board. The plug has been put on back to front I think. There is a pin 1 labeled on the mobo next to the floppy interface, of course I put it on backwards. The other 2000 is exactly the same, it's plug is on backwards, weird.
I'm fairly convinced that something is still not right on the board after the socket replacements. I will have to go do much more tedious testing to try and find what's wrong.
If it's not that, then it must be something to do with the drive cable being put on backwards and some damage to chips/components other than the 68000, Rom or other custom chips.
I have built an OS for the affected 2000 using the good 2000 to set it up. The affected system boots fine from a HDD. But the floppy drives are only accessable at boot time, and will only access for about 30 secs before they start to grind and error. This is just enough time for me to run binddrivers and tell it to continue booting from the HDD.
Cheers and thanks again to all.
:-D :-D