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

From: Ethan Dicks <ethan.dicks_at_gmail.com>
Date: Wed, 9 May 2018 22:02:22 -0400
Message-ID: <CAALmim=1mWoQ9xmHtA+WuaMH4FdZMoDdku3sx1L6Qp4OGdrgQg@mail.gmail.com>
On Wed, May 9, 2018 at 4:28 PM, Spiro Trikaliotis
<ml-cbmhackers@trikaliotis.net> wrote:
> Hello Ethan,
>
> thank you for your tests.

You are quite welcome.

> So it seems we have a general communication problem.

So it would seem.

> 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.

Ah.

I have the capability of compiling firmware and/or application code
for Linux for testing.  I'm fluent in C so I'm not just limited to
monkey testing.  I can poke around in the code and make my own
(thoughtful) mods.  (And I'm offering to be an active part of the
testing process).

> 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. :(

I happened to purchase mine with the IEEE connector but my soldering
skills are fine.

Since you asked Ville, let me say that my cable is a 2m-long lab-grade
shielded IEEE cable that I got from work (10+ years ago) when they
were tossing old test equipment.  It appears to be new or nearly new.
I have other cables as well.  I have it connected as Laptop<->USB Mini
cable<->Zoomfloppy<->2m IEEE cable<->2031.  Nothing else on the bus.

>> $ d64copy 8 foo.d64
>> [Warning] Unknown drive, assuming 1541   [ it hangs at this point, so
>
> 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.

Gotcha.  Just running through the gamut.  I'm not surprised it didn't work.

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

I can check that easily.

-ethan
Received on 2018-05-10 05:00:02

Archive generated by hypermail 2.2.0.