Hello,
* On Wed, Jan 19, 2022 at 04:28:51AM -0800 PDrill wrote:
> Copying starts fine. After a few percent the drive starts to bang it's head on
> the wall, most likely because of a read error. I click abort on the CBM
> Transfer and then I get a message saying 'You may need to unplug the Zoom
> Floppy in order to reset it!'. If I do no nothing, it will keep banging for
> ever and Zoom Floppy led flashes like it's doing something. Nothing can be done
> from CBM transfer at this time, init, reset, status, they do nothing. Then I
> disconnect the USB and the drive stops and red led flashes. Reconnecting the
> USB resets (or at least does something) everything and after that everything is
> in order again.
Please contact Steve Gray, the author of CBM Transfer. If it behaves
this way, it is a bug in CBM Transfer.
Why?
When you abort the operation on CBM Transfer, then CBM Transfer should
stop (abort, kill, whatever you want to call it) the running OpenCBM
program.
Looking at your description, it seems it does not kill it. Thus, the
OpenCBM tool (d64copy or else) is still open, so any subsequent call of
an OpenCBM tool (like cbmctrl reset) will fail, as the ZoomFloppy is
still being used by the PC.
By killing the hanging program, CBM Transfer would be able to issue
another one (like cbmctrl reset) to put the ZF again in a usable state.
Unplugging the ZF from USB, you tell Windows to destroy its device
drivers. This is propagated to the OpenCBM tool, which itself stops
working. That's why this work-around works.
However, it is an ugly hack and it is not the way it should be.
> Has to be noted also that clicking abort doesn't stop the drive in any other
> case (fully working floppies with D64 operations or file copy) either, the
> drive will do it's work until it's finished (or starts to bang if the floppy is
> faulty). Again, only solution is to abort the process is to
> disconnect-reconnect the USB cable. I am aware that operations like format
> can't be aborted, so I'm not talking about that, just pure file transfer
> operations.
Well, when you use to OpenCBM tools from the command line, then you can
abort the operation in progress (with Ctrl+C). For formatting, even that
can be aborted by issuing cbmctrl reset.
Thus, what you are encountering is really a limitation of CBM Transfer,
not of OpenCBM or the ZF.
As far as I know, Steve is not on this mailing list. I will write him a
mail off-list, with you in Cc: