Hello Ville, * On Wed, Mar 15, 2017 at 06:56:27PM +0200 Ville Laustela wrote: > I have now tested and my 2031 can read a 1541-formatted disk (from another drive) just fine. That's good. > d64copy won’t work (drive led starts blinking as if it has an error > condition, but as I quit d64copy, it resets the bus and I can’t see > the error). That's expected. d64copy does not know anything about a 2031. That's a really big pity, as the 2031 is the drive that is most similar to a 1540/1541, and it should be relativly easy to get it working. Unfortunately, I never owned one. > cbmctrl doesn’t seem to like the 2031 too much; it doesn’t > recognise it (cbmctrl detect -> 8: *unknown*, footprint=<DBDC>) That's interesting. I would have expected a footprint of FFFF, at least according to the ROM I have. The footprint is the contents at $FF40, and in the only ROM dump I have of a 2031, this is AAAA - identical to a 1540, and I would have expected cbmctrl to detect it as a 1540. Can you please try if you can dump the ROM and send it to me? $ cbmctrl download 8 0xc000 0x4000 rom2031.dump and send me the file rom2031.dump. It should be 16384 byte if everything worked out fine. If the file is less then 16384 byte, it might help if you repeat this process. Additionally, I would be interested in ALL results you got with this command, as it can tell me if and what problems you had. Oh, and don't be surprised, the command can take some minutes to finish! Can you read out the (physical) marking of the ROM chips, too? It is written on top of the ROM chips. The only ones I know are 901484-03 (for $C000-$DFFF) and 901484-05 (for $E000-$FFFF). Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ Message was sent through the cbm-hackers mailing listReceived on 2017-03-15 18:00:02
Archive generated by hypermail 2.2.0.