Marko Mäkelä wrote: > IIRC, cbmlink -dmco will dump the floppy controller ROM. Yes, I just saw the documentation. In order to avoid confusion, is this correct terminology? Disk controller (Rhialto/Moser) = Controller address space (cbmlink) Bus controller (Rhialto/Moser) = Main address space (cbmlink) In that case, would it be enough to use the cbmlink -dmco and -dmso calls to appropriate addresses, or do we still need to load Rhialto's program to copy from DC to BC? I saw in the cbmlink documentation that the drive might act strange after -dmco has been used, which matches what Wolfgang wrote with the drive getting stuck. I'm not afraid to reset it afterwards, in particular if the dumped data is safely stored on a PC. Then comes the next question: in order to know which chip one has, I suppose we'll need to open up the drives and look for markings. DOS version can be fairly easily read by reading the error channel upon reset. Indeed I only have a 2031 and a 8250LP left, but as I didn't any mention of the 2031 in Wolfgang's list, I suppose it either shares RRIOT with the 2040, 3040 or 4040 or was omitted for one reason or another. There's also the 2031LP which might want to be on the list, as even the 8280 was mentioned... Best regards -- Anders Carlsson Message was sent through the cbm-hackers mailing listReceived on 2011-08-09 14:00:33
Archive generated by hypermail 2.2.0.