On Wed, Mar 15, 2017 at 1:13 PM, Spiro Trikaliotis <firstname.lastname@example.org> wrote: >> I have now tested and my 2031 can read a 1541-formatted disk (from another drive) just fine. That's how I use my ZoomFloppy. The 2031 is normally attached to a PET and I have a dedicated 1541 for my ZF. I remember having communications difficulties with my ZF on an Ubuntu laptop. Haven't tried it in a few years. Should see where things are now. I have zero problems with my ZF and Linux and my 1541. >> d64copy won’t work... > > That's expected. d64copy does not know anything about a 2031. Sure. Would love to see it working, though. > 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. I would think it shouldn't be too far different. Same DOS, etc., just a different physical interface. > Unfortunately, I never owned one. I have one. Been using it for many years with real PETs. More portable than a 4040. >> 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 I can try this too. > 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). Those are the ones on zimmers.net (and are likely the only ones ever released). I can check mine to be sure. -ethan Message was sent through the cbm-hackers mailing listReceived on 2017-03-15 18:01:53
Archive generated by hypermail 2.2.0.