Re: ZoomFloppy - formatting a disk in a 2031 disk drive

From: Spiro Trikaliotis <ml-cbmhackers_at_trikaliotis.net>
Date: Wed, 9 May 2018 22:28:28 +0200
Message-ID: <20180509202828.b2rdtydppt7g32bx@hermes.local.trikaliotis.net>
Hello Ethan,

thank you for your tests.

So it seems we have a general communication problem.

Does anyone else have success or was unsuccessfull with other IEEE
drives (4040, 8x50, ...)?

I never tested the ZF with IEEE devices, at least not directly. I have a
IEC2IEEE adapter (by Jochen 'NLQ' Adler), but this does not help us in
debugging the IEEE protocol of the ZF.

I could try to solder the IEEE connector to my ZF, but my soldering
skills are near to non-existant, and I fear I might brick my ZF. :(



* On Wed, May 09, 2018 at 03:57:39PM -0400 Ethan Dicks wrote:
 
> (and an attempt to download ROM code)
> 
> $ cbmctrl download 8 0xc000 0x4000 rom2031.dump
> .,A transfer error occurred!
> cbmctrl: download: Resource temporarily unavailable

It would be interesting to know the size of the rom2031.dump file. Is it
always of a specific length, or does the length vary? Which lengths do
you get?
 
> $ d64copy 8 foo.d64
> magic = 0x3337
> magic = 0x4243
> [Warning] Unknown drive, assuming 1541   [ it hangs at this point, so
> I type ^C ]

This is not surprising, d64copy cannot handle IEEE drives. It does
not even have an option to use the original protocol, so you are stuck
there.

You could try imgcopy instead, it should be able to handle 2031 drives,
at least according to its documentation. I never tested it myself.


For cbmcopy, this is different, there, you have the --transfer=original
(-to) option.


Regards,
Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/
Received on 2018-05-09 23:01:41

Archive generated by hypermail 2.2.0.