ZF: Drive only reacts to "cbmctrl reset"

331 views
Skip to first unread message

Spiro Trikaliotis

unread,
Jun 7, 2020, 8:55:34 AM6/7/20
to zoomflop...@googlegroups.com
Hello,

I got a support request by Ruben (who will subscribe here soon), which I
could not help.

He wrote to me:


My drive is only reacting on 1 command and nothing else. That’s the “cbmctrl reset”.

With the “cbmctrl status 8” I get “99, driver error,00,00”


He is running Windows.

I told him to do the tests with XUM1541_DEBUG set, and he gets the following output:

> C:\Program Files\opencbm>cbmctrl reset
> [XUM1541] scanning usb ...
> [XUM1541] scanning bus bus-0
> [XUM1541] device 16d0:0504 at \\.\libusb0-0001--0x16d0-0x0504
> [XUM1541] found xu/xum1541 version 0207 on bus bus-0, device \\.\libusb0-0001--0x16d0-0x0504
> [XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
> [XUM1541] xum1541 serial number: 0
> [XUM1541] firmware version 7, library version 7
> [XUM1541] device capabilities 03 status 00
> [XUM1541] [xum1541_init] No tape support.
> [XUM1541] control msg 2
> [XUM1541] Closing USB link

> C:\Program Files\opencbm>cbmctrl detect
> [XUM1541] scanning usb ...
> [XUM1541] scanning bus bus-0
> [XUM1541] device 16d0:0504 at \\.\libusb0-0001--0x16d0-0x0504
> [XUM1541] found xu/xum1541 version 0207 on bus bus-0, device \\.\libusb0-0001--0x16d0-0x0504
> [XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
> [XUM1541] xum1541 serial number: 0
> [XUM1541] firmware version 7, library version 7
> [XUM1541] device capabilities 03 status 00
> [XUM1541] [xum1541_init] No tape support.
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] write 16 2 bytes from address 00000000000CFCA4 flags 2
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> [XUM1541] Closing USB link

> C:\Program Files\opencbm>cbmctrl status 8
> [XUM1541] scanning usb ...
> [XUM1541] scanning bus bus-0
> [XUM1541] device 16d0:0504 at \\.\libusb0-0001--0x16d0-0x0504
> [XUM1541] found xu/xum1541 version 0207 on bus bus-0, device \\.\libusb0-0001--0x16d0-0x0504
> [XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
> [XUM1541] xum1541 serial number: 0
> [XUM1541] firmware version 7, library version 7
> [XUM1541] device capabilities 03 status 00
> [XUM1541] [xum1541_init] No tape support.
> [XUM1541] write 16 2 bytes from address 00000000000CFCF4 flags 3
> [XUM1541] wrote 2 bytes
> [XUM1541] xum1541_wait_status checking for status
> [XUM1541] return val = 0
> [XUM1541] wait done, extended status 0
> [XUM1541] write done, got 0 bytes
> 99, driver error,00,00
> [XUM1541] Closing USB link

I know a similar behaviour with the xa1541 cable: When the lines are not
correctly connected (either DATA, ATN or CLK), I have seen a similar
behaviour.

Could this be the same problem here? Does anyone see any other reason?


In my eyes, it is NOT the problem Martin Thierer worked on, because the
communication with the ZF seems to be flawless.


Any other ideas?

Regards,
Spiro.

--
Spiro R. Trikaliotis
http://spiro.trikaliotis.net/

Markus Plehn

unread,
Jun 8, 2020, 4:17:00 AM6/8/20
to zoomflop...@googlegroups.com
"I told him to do the tests with XUM1541_DEBUG set"

simple question: how can i activate the debug feature ?

Markus

2020-06-07 14:55 GMT+02:00, Spiro Trikaliotis
<an-zoomfl...@spiro.trikaliotis.net>:
> --
> You received this message because you are subscribed to the Google Groups
> "ZoomFloppy Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to zoomfloppy-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/zoomfloppy-users/20200607125529.GD14430%40hermes.local.trikaliotis.net.
>

RETRO Innovations

unread,
Jun 8, 2020, 12:20:59 PM6/8/20
to zoomflop...@googlegroups.com
To respond.  I can't comment on whether line miswires would cause this
issue, but I can comment that each device is tested with a known working
1541 before shipment (I do a cbmctrl detect with the expected drive
notes being part of the expectation).

Do we know if the drive in question works with a regular CBM machine?

It is possible for the 74ls06 driver to die, though unlikely so soon.

Jim

Spiro Trikaliotis

unread,
Jun 8, 2020, 1:04:39 PM6/8/20
to zoomflop...@googlegroups.com
* On Mon, Jun 08, 2020 at 10:16:57AM +0200 'Markus Plehn' via ZoomFloppy Users wrote:
> "I told him to do the tests with XUM1541_DEBUG set"
>
> simple question: how can i activate the debug feature ?

On Windows:

set XUM1541_DEBUG=9

and then do whatever you are doing (cbmctrl reset, d64copy, ...)


On Linux:

export XUM1541_DEBUG=9

and then do whatever you are doing, or (depends upon your shell; on
bash and some others, this works):

XUM1541_DEBUG=9 cbmctrl ...

That is, just put the XUM1541_DEBUG=9 in front of the command..


For Windows, there is also this option available:

https://spiro.trikaliotis.net/opencbm-debug

although I did not test if DebugView still works with Windows Vista or
above... I only used it on 2000 and XP.

Spiro Trikaliotis

unread,
Jun 9, 2020, 4:57:49 PM6/9/20
to zoomflop...@googlegroups.com
Hello,

* On Mon, Jun 08, 2020 at 11:20:56AM -0500 RETRO Innovations wrote:

> Do we know if the drive in question works with a regular CBM machine?

Ruben, can you tell this? Does your ZF work on a regular CBM machine?

RETRO Innovations

unread,
Jun 9, 2020, 7:27:52 PM6/9/20
to zoomflop...@googlegroups.com
On 6/9/2020 3:57 PM, Spiro Trikaliotis wrote:
Hello,

* On Mon, Jun 08, 2020 at 11:20:56AM -0500 RETRO Innovations wrote:
 
Do we know if the drive in question works with a regular CBM machine?
Ruben, can you tell this? Does your ZF work on a regular CBM machine?


Regards,
Spiro.

He sent me a note that it (a 1571) does.  I think I'll send a new unit out, as I can't imagine why the SW would cause this issue.

Jim


-- 
RETRO Innovations, Contemporary Gear for Classic Systems
www.go4retro.com
store.go4retro.com

Ruben Groen

unread,
Jun 10, 2020, 6:26:08 AM6/10/20
to ZoomFloppy Users
Hi Spiro,

My 1571 works great on a C64 and also with the IECHost.

Jim has been informed.


Op dinsdag 9 juni 2020 22:57:49 UTC+2 schreef Spiro Trikaliotis:

Dan Gahlinger

unread,
Jun 10, 2020, 9:09:59 AM6/10/20
to ZoomFloppy Users
pardon the intrusion but I just want to mention the parallel wiring for 1571 is vastly different from the 1541.
I just ran into this myself.

If this has already been checked, again please excuse my reply.

Dan

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.

Ruben Groen

unread,
Jun 10, 2020, 1:02:32 PM6/10/20
to ZoomFloppy Users
Hi Dan,

Thank you for think along Dan.

But I use my 1571 just with the serial cable.

So no parallel cable needed.

Ruben

Dan Gahlinger

unread,
Jun 10, 2020, 1:20:25 PM6/10/20
to ZoomFloppy Users
I wasn't aware you could use zoomfloppy that way.
everything i read said it was parallel only.

I'm really happy to be wrong and learn something new.
gives me things to try
thank you

dont want to repeat everything but have you tried d64copy cbmxfer gui4cbm4win or other related tools?

Dan

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.

rittwage

unread,
Jun 10, 2020, 4:57:17 PM6/10/20
to ZoomFloppy Users
ZoomFloppy is the only thing connected to the drive?  This kind of thing happens if a C64 is also connected to the chain, regardless of whether it is powered off or not.

Spiro Trikaliotis

unread,
Jun 11, 2020, 12:00:42 PM6/11/20
to ZoomFloppy Users
Hello,
Pete, good point!

Ruben, can you answer this?

Ruben Groen

unread,
Jun 11, 2020, 12:54:14 PM6/11/20
to ZoomFloppy Users
Hi Pete, we already emailed together about writing g64 files.
Yes during my searches for this problem I read somewhere about this and was thus aware of this. But in my case there was nothing else connected to the drive. But thank you Pete for helping! Ruben

Ruben Groen

unread,
Jun 12, 2020, 6:51:36 AM6/12/20
to ZoomFloppy Users
Hi Spiro,

Finally some good news! As we tought it is a software problem.

I installed your latest opencbm-0.4.99.100.

And the drive is finally responding. Many thanks to you Spiro!

It now recognize my 1571 drive.

I can list a floppy.

There are still some problems error messages, hope you can fix them.

Results for now without debug:


C:\Program Files\opencbm>cbmctrl reset
previous command was interrupted, resetting
USB error in xum1541_control_msg: LIBUSB_ERROR_IO

C:\Program Files\opencbm>cbmctrl detect
previous command was interrupted, resetting
 8: 1571
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO
USB deconfig device error: -2 LIBUSB_ERROR_INVALID_PARAM

C:\Program Files\opencbm>cbmctrl status 8
previous command was interrupted, resetting
73,cbm dos v3.0 1571,00,00
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO
USB deconfig device error: -2 LIBUSB_ERROR_INVALID_PARAM

C:\Program Files\opencbm>cbmctrl dir 8
previous command was interrupted, resetting
0 ."0               " 00 2a
65   "sdcmduc.prg"      prg
9    "setboot.prg"      prg
65   "c64-boot.prg"     prg
1    "buttons.prg"      prg
524 blocks free.
00, ok,00,00
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO
USB deconfig device error: -2 LIBUSB_ERROR_INVALID_PARAM

C:\Program Files\opencbm>

Results for now with debug:


C:\Program Files\opencbm>cbmctrl reset
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] control msg 2
USB error in xum1541_control_msg: LIBUSB_ERROR_IO

C:\Program Files\opencbm>cbmctrl detect
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD64 flags 0
[XUM1541] wrote 6 bytes (4d 2d 52 40 ff 02)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD48 flags 3
[XUM1541] wrote 2 bytes (48 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 3 bytes to address 00000000000CFD60
[XUM1541] read 3 bytes (ac 02 0d)
[XUM1541] read done, got 3 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD48 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] ioctl 25 for device 0, sub 0
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = ff
[XUM1541] return val = ff
[XUM1541] write 16 2 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD04 flags 0
[XUM1541] wrote 6 bytes (4d 2d 57 03 40 01)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDA8 flags 0
[XUM1541] wrote 1 bytes (ff)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD04 flags 0
[XUM1541] wrote 6 bytes (4d 2d 57 01 40 01)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDA0 flags 0
[XUM1541] wrote 1 bytes (55)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] ioctl 25 for device 0, sub 0
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = ff
[XUM1541] return val = ff
[XUM1541] write 16 2 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD04 flags 0
[XUM1541] wrote 6 bytes (4d 2d 57 03 40 01)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDA9 flags 0
[XUM1541] wrote 1 bytes (00)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
 8: 1571
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (29 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2a 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2b 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2c 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2d 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2e 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2f 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (30 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (31 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (32 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (33 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (34 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (35 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (36 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (37 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (38 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (39 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3a 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3b 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3c 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3d 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3e 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] Closing USB link
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO
USB deconfig device error: -2 LIBUSB_ERROR_INVALID_PARAM

C:\Program Files\opencbm>cbmctrl status 8
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] write 16 2 bytes from address 00000000000CFDB8 flags 3
[XUM1541] wrote 2 bytes (48 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 38 bytes to address 00000000000CFE10
[XUM1541] read 27 bytes (37 33 2c 43 42 4d 20 44 ...)
[XUM1541] read done, got 27 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDB8 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
73,cbm dos v3.0 1571,00,00
[XUM1541] Closing USB link
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO
USB deconfig device error: -2 LIBUSB_ERROR_INVALID_PARAM

C:\Program Files\opencbm>cbmctrl dir 8
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] write 16 2 bytes from address 00000000000CFD78 flags 2
[XUM1541] wrote 2 bytes (28 f0)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 1 bytes from address 00000000001F6AE0 flags 0
[XUM1541] wrote 1 bytes (24)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD78 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD98 flags 3
[XUM1541] wrote 2 bytes (48 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 38 bytes to address 00000000000CFDF8
[XUM1541] read 13 bytes (30 30 2c 20 4f 4b 2c 30 ...)
[XUM1541] read done, got 13 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD98 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFDC8 flags 3
[XUM1541] wrote 2 bytes (48 60)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 04)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 01)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (00 00)
[XUM1541] read done, got 2 bytes
0 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (12)
[XUM1541] read done, got 1 bytes
.[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (30)
[XUM1541] read done, got 1 bytes
0[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (30)
[XUM1541] read done, got 1 bytes
0[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (30)
[XUM1541] read done, got 1 bytes
0[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (32)
[XUM1541] read done, got 1 bytes
2[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (41)
[XUM1541] read done, got 1 bytes
a[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (00)
[XUM1541] read done, got 1 bytes

[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 01)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (41 00)
[XUM1541] read done, got 2 bytes
65 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (53)
[XUM1541] read done, got 1 bytes
s[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (44)
[XUM1541] read done, got 1 bytes
d[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (43)
[XUM1541] read done, got 1 bytes
c[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4d)
[XUM1541] read done, got 1 bytes
m[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (44)
[XUM1541] read done, got 1 bytes
d[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (55)
[XUM1541] read done, got 1 bytes
u[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (43)
[XUM1541] read done, got 1 bytes
c[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (2e)
[XUM1541] read done, got 1 bytes
.[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (00)
[XUM1541] read done, got 1 bytes

[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 01)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (09 00)
[XUM1541] read done, got 2 bytes
9 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (53)
[XUM1541] read done, got 1 bytes
s[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (45)
[XUM1541] read done, got 1 bytes
e[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (54)
[XUM1541] read done, got 1 bytes
t[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (42)
[XUM1541] read done, got 1 bytes
b[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4f)
[XUM1541] read done, got 1 bytes
o[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4f)
[XUM1541] read done, got 1 bytes
o[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (54)
[XUM1541] read done, got 1 bytes
t[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (2e)
[XUM1541] read done, got 1 bytes
.[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (00)
[XUM1541] read done, got 1 bytes

[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 01)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (41 00)
[XUM1541] read done, got 2 bytes
65 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (43)
[XUM1541] read done, got 1 bytes
c[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (36)
[XUM1541] read done, got 1 bytes
6[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (34)
[XUM1541] read done, got 1 bytes
4[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (2d)
[XUM1541] read done, got 1 bytes
-[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (42)
[XUM1541] read done, got 1 bytes
b[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4f)
[XUM1541] read done, got 1 bytes
o[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4f)
[XUM1541] read done, got 1 bytes
o[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (54)
[XUM1541] read done, got 1 bytes
t[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (2e)
[XUM1541] read done, got 1 bytes
.[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (00)
[XUM1541] read done, got 1 bytes

[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 01)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 00)
[XUM1541] read done, got 2 bytes
1 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (42)
[XUM1541] read done, got 1 bytes
b[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (55)
[XUM1541] read done, got 1 bytes
u[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (54)
[XUM1541] read done, got 1 bytes
t[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (54)
[XUM1541] read done, got 1 bytes
t[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4f)
[XUM1541] read done, got 1 bytes
o[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4e)
[XUM1541] read done, got 1 bytes
n[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (53)
[XUM1541] read done, got 1 bytes
s[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (2e)
[XUM1541] read done, got 1 bytes
.[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (22)
[XUM1541] read done, got 1 bytes
"[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (50)
[XUM1541] read done, got 1 bytes
p[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (47)
[XUM1541] read done, got 1 bytes
g[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (00)
[XUM1541] read done, got 1 bytes

[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (01 01)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (0c 02)
[XUM1541] read done, got 2 bytes
524 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (42)
[XUM1541] read done, got 1 bytes
b[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4c)
[XUM1541] read done, got 1 bytes
l[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4f)
[XUM1541] read done, got 1 bytes
o[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (43)
[XUM1541] read done, got 1 bytes
c[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (4b)
[XUM1541] read done, got 1 bytes
k[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (53)
[XUM1541] read done, got 1 bytes
s[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (46)
[XUM1541] read done, got 1 bytes
f[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (52)
[XUM1541] read done, got 1 bytes
r[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (45)
[XUM1541] read done, got 1 bytes
e[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (45)
[XUM1541] read done, got 1 bytes
e[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (2e)
[XUM1541] read done, got 1 bytes
.[XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (20)
[XUM1541] read done, got 1 bytes
 [XUM1541] read 16 1 bytes to address 00000000000CFDF0
[XUM1541] read 1 bytes (00)
[XUM1541] read done, got 1 bytes

[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read 2 bytes (00 00)
[XUM1541] read done, got 2 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read done, got 0 bytes
[XUM1541] read 16 2 bytes to address 00000000000CFDF8
[XUM1541] read done, got 0 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDC8 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD98 flags 3
[XUM1541] wrote 2 bytes (48 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 38 bytes to address 00000000000CFDF8
[XUM1541] read 13 bytes (30 30 2c 20 4f 4b 2c 30 ...)
[XUM1541] read done, got 13 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD98 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
00, ok,00,00
[XUM1541] write 16 2 bytes from address 00000000000CFDC8 flags 2
[XUM1541] wrote 2 bytes (28 e0)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] Closing USB link
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO
USB deconfig device error: -2 LIBUSB_ERROR_INVALID_PARAM

C:\Program Files\opencbm>

Op zondag 7 juni 2020 14:55:34 UTC+2 schreef Spiro Trikaliotis:

Ruben Groen

unread,
Jun 14, 2020, 3:10:57 PM6/14/20
to ZoomFloppy Users
Hi Spiro,

After installing the *.101 version I still got messages.

And my led is constant blinking also when it's doining "nothing".

Ruben

C:\Program Files\opencbm>cbmctrl detect 8
previous command was interrupted, resetting
 8: 1571
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO

C:\Program Files\opencbm>cbmctrl reset
previous command was interrupted, resetting
USB error in xum1541_control_msg: LIBUSB_ERROR_IO

C:\Program Files\opencbm>cbmctrl dir 8
previous command was interrupted, resetting
0 ."master          " 02 2a
1    "commando"         prg
202  "pl"               prg
50   "nb"               prg
411 blocks free.
00, ok,00,00
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO

C:\Program Files\opencbm>

With Debug:


C:\Program Files\opencbm>cbmctrl reset
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] control msg 2
USB error in xum1541_control_msg: LIBUSB_ERROR_IO

C:\Program Files\opencbm>cbmctrl detect 8
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD64 flags 0
[XUM1541] wrote 6 bytes (4d 2d 52 40 ff 02)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD48 flags 3
[XUM1541] wrote 2 bytes (48 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 3 bytes to address 00000000000CFD60
[XUM1541] read 3 bytes (ac 02 0d)
[XUM1541] read done, got 3 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFD48 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] ioctl 25 for device 0, sub 0
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = ff
[XUM1541] return val = ff
[XUM1541] write 16 2 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD04 flags 0
[XUM1541] wrote 6 bytes (4d 2d 57 03 40 01)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDA8 flags 0
[XUM1541] wrote 1 bytes (ff)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD04 flags 0
[XUM1541] wrote 6 bytes (4d 2d 57 01 40 01)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDA0 flags 0
[XUM1541] wrote 1 bytes (55)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] ioctl 25 for device 0, sub 0
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = ff
[XUM1541] return val = ff
[XUM1541] write 16 2 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 2 bytes (28 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 00000000000CFD04 flags 0
[XUM1541] wrote 6 bytes (4d 2d 57 03 40 01)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 6
[XUM1541] wait done, extended status 6
[XUM1541] write done, got 6 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDA9 flags 0
[XUM1541] wrote 1 bytes (00)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFCE8 flags 2
[XUM1541] wrote 1 bytes (3f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
 8: 1571
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (29 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2a 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2b 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2c 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2d 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2e 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (2f 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (30 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (31 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (32 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (33 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (34 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (35 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (36 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (37 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (38 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (39 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3a 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3b 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3c 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3d 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 2 bytes from address 00000000000CFD18 flags 2
[XUM1541] wrote 2 bytes (3e 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] Closing USB link
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO

C:\Program Files\opencbm>cbmctrl status 8
[XUM1541] scanning usb ...
[XUM1541] device 8086:9c26
[XUM1541] device 0c45:64d2
[XUM1541] device 04f3:0111
[XUM1541] device 8086:9c31
[XUM1541] device 16d0:0504
[XUM1541] found xu/xum1541 version 0207 on bus 2, device 1
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:   0
[XUM1541] firmware version 7, library version 8
[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting
[XUM1541] [xum1541_init] No tape support.
[XUM1541] write 16 2 bytes from address 00000000000CFDB8 flags 3
[XUM1541] wrote 2 bytes (48 6f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] read 16 38 bytes to address 00000000000CFE10
[XUM1541] read 27 bytes (37 33 2c 43 42 4d 20 44 ...)
[XUM1541] read done, got 27 bytes
[XUM1541] write 16 1 bytes from address 00000000000CFDB8 flags 2
[XUM1541] wrote 1 bytes (5f)
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
73,cbm dos v3.0 1571,00,00
[XUM1541] Closing USB link
USB request for XUM1541 close failed, continuing: LIBUSB_ERROR_IO

C:\Program Files\opencbm>


Op zondag 7 juni 2020 14:55:34 UTC+2 schreef Spiro Trikaliotis:
Hello,

Spiro Trikaliotis

unread,
Jun 14, 2020, 5:00:58 PM6/14/20
to ZoomFloppy Users
Hello Ruben,

* On Sun, Jun 14, 2020 at 12:10:57PM -0700 Ruben Groen wrote:

> After installing the *.101 version I still got messages.
>
> And my led is constant blinking also when it's doining "nothing".

That's weird. I don't have an idea what might be the problem.

Martin, do you have an idea what might be going on here?

Martin Thierer

unread,
Jun 15, 2020, 11:48:58 AM6/15/20
to ZoomFloppy Users
Hi Ruben,


After installing the *.101 version I still got messages.

And my led is constant blinking also when it's doining "nothing".

Am I correct to assume that the blinking only starts *after* you issue the first command that communicates with the zoomfloppy? Also, the first command that you have in your log already show the "previous command was interrupted, resetting" message, but that shouldn't be the case for the first command after you booted or re-plugged the usb cable of the zoomfloppy. 

The blinking indicates that the device is busy. That it keeps blinking after a command is no surprise, because apparently the message that is supposed to clear the busy flag runs into some kind of error. It would surprise me, however, if the blinking started after you plugged the usb cable in, even without issuing any command.

Could you please do the following:

1. Unplug all cables from the zoomfloppy. You wrote that you don't use a parallel cable, so that's probably only the usb cable to the computer and the serial cable to the floppy drive.
2. No need to reboot the computer, but a power cycle for the floppy drive couldn't hurt.
3. Reconnect only the serial cable and the usb cable to the zoomfloppy and plug the usb cable into the computer.
4. The run "LIBUSB_DEBUG=9 cbmctrl status 8" and post the output. But please first paste the output into a text file and then attach that file, instead of pasting it all into your message. That makes both the log and your message easier to read.

Thanks!

Martin

Martin Thierer

unread,
Jun 15, 2020, 12:13:50 PM6/15/20
to ZoomFloppy Users
> After installing the *.101 version I still got messages.
>
> And my led is constant blinking also when it's doining "nothing".

That's weird. I don't have an idea what might be the problem.

Martin, do you have an idea what might be going on here?

Hi Spiro,

I have an idea, but it's pure speculation based on the observation that OUT control messages fail, while IN messages seem to work. I have no idea what's causing this and why it would only affect some win installs while others work fine. I think I saw both success and failure on both win 8 and win 10, so that doesn't seem to be the issue. And if everyone used your install script then everyone should be running the same driver, right? Maybe it's a case of some old driver still being active.

That said, both control messages that fail have no payload, so it's worth a shot to convert them to IN messages and see if that helps.

Could you please make a test version based on the changes in this branch so Ruben and the others affected could try if it works for them?


This version still works for me on linux, but for some reason at least linux doesn't seem to like IN control messages with no payload, that's why I have to specify a dummy 1 byte buffer even though the commands don't actually transfer any data. Maybe there's a way around this, but to see if it makes a (positive) difference this little hack should be fine.

Please note that while I also changed the libusb0-specific code, I didn't actually test it with libusb0.

Martin

Ruben Groen

unread,
Jun 15, 2020, 12:56:15 PM6/15/20
to zoomflop...@googlegroups.com
Hi Martin,

The blinking wasn't at first. 

When I start windows and everythings is set, the led is off, but as soon as I do a command it blinks for the activity but when done it is going to blink the whole time.

I have done what you asked.

At point 4 I get lost. The command you give is not working.

So I tried:

1: set LIBUSB_DEBUG=9
enter
2: cbmctrl status 8
enter

This is what you meant?

The result is now in a txt files, that's a very good idea!

Many thanks,

Ruben

Op ma 15 jun. 2020 om 17:49 schreef Martin Thierer <mthi...@gmail.com>:
--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
LIBUSB_DEBUG=9 cbmctrl status 8.txt

Martin Thierer

unread,
Jun 15, 2020, 1:40:43 PM6/15/20
to ZoomFloppy Users
Hi Ruben,
 
At point 4 I get lost. The command you give is not working.

So I tried:

1: set LIBUSB_DEBUG=9
enter
2: cbmctrl status 8
enter

yes, sorry, I made 2 mistakes here: Putting the environment variable in from of the command works on linux, but not on windows. Also, while the libusb output might be useful as well, what I really meant was XUM1541_DEBUG=9. Could you please do the same with "set XUM1541_DEBUG=9" again, please?

But I also have questions regarding the libusb debug output:

1. The output suggests that you are on Windows 8, is that correct? Was the debug output you posted yesterday from the same machine?
2. The output has this line:

99, driver error,00,00

while the output of "cbmctrl status" you posted yesterday said

73,cbm dos v3.0 1571,00,00

The "99, driver error,00,00" basically means that there was an error communicating with the device while "73,cbm dos v3.0 1571,00,00" means communication was successful. Was that a one off error? Do you normally get the status from the device ("00, ok,00,00" would be good, too).

I'm asking because the log you posted yesterday suggests that the communication with the floppy drive is generally working fine, just closing the connection doesn't work (which leads to the "USB request for XUM1541 close failed" error). But the log you posted now suggests that the zoomfloppy couldn't connect to the floppy drive.

@Spiro, could it be this install isn't using the driver from your install script? There are a few things in the debug log that make me suspicious:

1. [ 0.000000] [000019b4] libusb: debug [libusb_init] libusb v1.0.22.11312 (which isn't the latest version 1.0.23, which you'd probably install)
2. A few mentions of "libusb0"
3. [ 0.325840] [000019b4] libusb: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] De parameter is onjuist. I found references to the "ControlTransfer failed: [87]" (which seems to be the underlying problem which finally causes the "USB request for XUM1541 close failed" error) in connection with libusb0, but that might be a coincidence.

Martin

Ruben Groen

unread,
Jun 15, 2020, 2:34:10 PM6/15/20
to zoomflop...@googlegroups.com
Hi Martin,

That's not correct, yes it's still the same machine with windows 10 pro 64 bits

I can't explain the 99 drive error and windows 8?!

Here's the new report

Ruben

Op ma 15 jun. 2020 om 19:40 schreef Martin Thierer <mthi...@gmail.com>:
--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
Debug_Report_15_06_001.txt

Ruben Groen

unread,
Jun 15, 2020, 2:46:24 PM6/15/20
to zoomflop...@googlegroups.com
Hi Martin,

I did the LIBUSB again.

Now the 99 drive error is gone but still Windows 8?!

I have Windows 10 Pro
Version 1903
Build 18362.836

Ruben

Op ma 15 jun. 2020 om 18:13 schreef Martin Thierer <mthi...@gmail.com>:
--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
Debug_Report_Re_LIBUSB.txt

Spiro Trikaliotis

unread,
Jun 15, 2020, 4:41:38 PM6/15/20
to ZoomFloppy Users
Hello Martin,

* On Mon, Jun 15, 2020 at 09:13:50AM -0700 Martin Thierer wrote:

> I have an idea, but it's pure speculation based on the observation that OUT
> control messages fail, while IN messages seem to work. I have no idea what's
> causing this and why it would only affect some win installs while others work
> fine. I think I saw both success and failure on both win 8 and win 10, so that
> doesn't seem to be the issue. And if everyone used your install script then
> everyone should be running the same driver, right? Maybe it's a case of some
> old driver still being active.

If the people installed a libusb1 based version of OpenCBM, they can
still have the old driver.

If they have used the official versions which are libusb0 based, the old
driver would not work at all (as long as they did not use libusbK, but
that was never recommended)


> Could you please make a test version based on the changes in this branch so
> Ruben and the others affected could try if it works for them?
>
> https://github.com/thierer/OpenCBM/tree/in_ctrl_msg

You mean, a Windows test version, right?

> Please note that while I also changed the libusb0-specific code, I didn't
> actually test it with libusb0.

libusb0 does not even compile at the moment (because there was an
misplaced #endif in opencbm/lib/plugin/xum1541/xum1541.c), so it is
clear you cannot test it. ;)

Spiro Trikaliotis

unread,
Jun 15, 2020, 5:23:22 PM6/15/20
to ZoomFloppy Users
Hello,

* On Mon, Jun 15, 2020 at 10:41:36PM +0200 I wrote:
> Hello Martin,
>
> * On Mon, Jun 15, 2020 at 09:13:50AM -0700 Martin Thierer wrote:

> > Could you please make a test version based on the changes in this branch so
> > Ruben and the others affected could try if it works for them?
> >
> > https://github.com/thierer/OpenCBM/tree/in_ctrl_msg
>
> You mean, a Windows test version, right?

It is here:

https://spiro.trikaliotis.net/download/opencbm-0.4.99.101/opencbm-0.4.99.101-modified.zip

Martin Thierer

unread,
Jun 16, 2020, 2:02:07 PM6/16/20
to ZoomFloppy Users
Hi Ruben,

ok, nevermind about the Windows 8 message. Maybe libusb just doesn't know about newer versions.

Is the log you attached to this message really from the first command after you un- and re-plugged the zoomfloppy?

It has this message, which shouldn't happen in that scenario:

[XUM1541] device capabilities 03 status 01
previous command was interrupted, resetting

Martin 

Martin Thierer

unread,
Jun 16, 2020, 2:03:22 PM6/16/20
to ZoomFloppy Users
> > Could you please make a test version based on the changes in this branch so
> > Ruben and the others affected could try if it works for them?
> >
> >     https://github.com/thierer/OpenCBM/tree/in_ctrl_msg
>
> You mean, a Windows test version, right?

It is here:

  https://spiro.trikaliotis.net/download/opencbm-0.4.99.101/opencbm-0.4.99.101-modified.zip

Thanks!

@Ruben, could you please install this version and report back with the log of "cbmctrl status" with "set XUM1541_DEBUG=9"?

Martin

Martin Thierer

unread,
Jun 16, 2020, 2:06:18 PM6/16/20
to ZoomFloppy Users
Hi Spiro,


> I have an idea, but it's pure speculation based on the observation that OUT
> control messages fail, while IN messages seem to work. I have no idea what's
> causing this and why it would only affect some win installs while others work
> fine. I think I saw both success and failure on both win 8 and win 10, so that
> doesn't seem to be the issue. And if everyone used your install script then
> everyone should be running the same driver, right? Maybe it's a case of some
> old driver still being active.

If the people installed a libusb1 based version of OpenCBM, they can
still have the old driver.

Ok, but is it also plausible that it's using libusb v1.0.22.11312 like reported in Ruben's debug log? I haven't checked with my win 10 install yet, but I guess you would install the latest version, which at least on linux is 1.0.23.

If they have used the official versions which are libusb0 based, the old
driver would not work at all (as long as they did not use libusbK, but
that was never recommended)
 
> Please note that while I also changed the libusb0-specific code, I didn't
> actually test it with libusb0.

libusb0 does not even compile at the moment (because there was an
misplaced #endif in opencbm/lib/plugin/xum1541/xum1541.c), so it is
clear you cannot test it. ;)

Oops, that's probably my fault... Sorry about that. I can confirm that I didn't test my patches with libusb0...

Martin 

Martin Thierer

unread,
Jun 16, 2020, 3:39:38 PM6/16/20
to ZoomFloppy Users
I collected the "LIBUSB_DEBUG" log from my (working) win 10 install and compared it to Ruben's log (pasted here but I'll also attach it as a file, in case the formatting doesn't survive):

libusb: debug [libusb_init] created default context      libusb: debug [libusb_init] created default context
libusb: debug [libusb_init] libusb v1.0.22.11312 libusb: debug [libusb_init] libusb v1.0.22.11312
libusb: debug [windows_init_dlls] Will use CancelIoEx for I/O cancellation      libusb: debug [windows_init_dlls] Will use CancelIoEx for I/O cancellation
libusb: debug [get_windows_version] Windows 8 64-bit    libusb: debug [get_windows_version] Windows 8 64-bit
libusb: debug [windows_init_clock] hires timer available (Frequency: 10000000 Hz)       libusb: debug [windows_init_clock] hires timer available (Frequency: 10000000 Hz)
libusb: debug [windows_init_clock] timer thread will run on core #0      libusb: debug [windows_init_clock] timer thread will run on core #0
libusb: debug [htab_create] using 1021 entries hash table        libusb: debug [htab_create] using 1021 entries hash table
libusb: info [winusbx_init] libusbK DLL is not available, will use native WinUSB      | libusb: debug [winusbx_init] using libusbK DLL for universal access
      > libusb: debug [winusbx_init] libusbK version: 3.0.7.0
libusb: debug [winusbx_init] initalized sub API libusbK libusb: debug [winusbx_init] initalized sub API libusbK
libusb: debug [winusbx_init] initalized sub API libusb0 libusb: debug [winusbx_init] initalized sub API libusb0
libusb: debug [winusbx_init] initalized sub API WinUSB  libusb: debug [winusbx_init] initalized sub API WinUSB
libusb: info [windows_init] UsbDk backend is not available      libusb: info [windows_init] UsbDk backend is not available
libusb: debug [usbi_add_pollfd] add fd 0 events 1        libusb: debug [usbi_add_pollfd] add fd 0 events 1
libusb: debug [libusb_get_device_list]  libusb: debug [libusb_get_device_list]
libusb: debug [get_api_type] driver(s): WinUSB        | libusb: debug [get_api_type] driver(s): libusb0
libusb: debug [get_api_type] matched driver name against WinUSB       | libusb: debug [get_api_type] matched driver name against libusb0
libusb: debug [winusb_get_device_list] allocating new device for session [2]          | libusb: debug [winusb_get_device_list] allocating new device for session [25]

Mine is left, Ruben's is right.

I noticed a few things:

1. My install also reports "Windows 8" even though it's Windows 10, so that seems to be normal
2. @Spiro: My install also reports v1.0.22 for libusb, so the question in my other post is moot, but I have a new one for you :)
3. My log has the line "libusbK DLL is not available, will use native WinUSB" while Ruben's install apparently has libusbK, so it seems to use that. In absence of other obvious differences I think this might well be the problem here. In your post on Sunday you wrote "libusbK and WinUSB can be used to implement the libusb1 interface.". Is it possible to force libusb1 to use WinUSB? At least temporarily renaming the dll for a test should work?

Martin
xum1541_win_usb.diff

Spiro Trikaliotis

unread,
Jun 16, 2020, 4:07:07 PM6/16/20
to ZoomFloppy Users
Hello Martin,

* On Tue, Jun 16, 2020 at 11:06:18AM -0700 Martin Thierer wrote:

> Ok, but is it also plausible that it's using libusb v1.0.22.11312 like reported
> in Ruben's debug log? I haven't checked with my win 10 install yet, but I guess
> you would install the latest version, which at least on linux is 1.0.23.

Indeed, I have the 1.0.22 in my Windows binaries. I just updated it in
git, the next version will have 1.0.23.

> Oops, that's probably my fault... Sorry about that. I can confirm that I didn't
> test my patches with libusb0...

It is. :)

Spiro Trikaliotis

unread,
Jun 16, 2020, 4:54:42 PM6/16/20
to ZoomFloppy Users
Hello,

* On Tue, Jun 16, 2020 at 12:39:38PM -0700 Martin Thierer wrote:

> 1. My install also reports "Windows 8" even though it's Windows 10, so that
> seems to be normal

It is.

I had a look into the libusb source. In libusb/os/windows_nt_common.c,
it uses GetVersionEx() (more precisely: GetVersionExA(), the ASCII
version of it instead of the Unicode Version) in function
get_windows_version().

Now, MS has to tell us about this function:
https://docs.microsoft.com/de-de/windows/win32/api/sysinfoapi/nf-sysinfoapi-getversionexa

"Applications not manifested for Windows 8.1 or Windows 10 will return
the Windows 8 OS version value (6.2)."

As I do not have a manifest, it will always report Windows 8.

> 2. @Spiro: My install also reports v1.0.22 for libusb, so the question in my
> other post is moot, but I have a new one for you :)

As I already said, it is part of the installer, which still has 1.0.22.

> 3. My log has the line "libusbK DLL is not available, will use native WinUSB"
> while Ruben's install apparently has libusbK, so it seems to use that. In
> absence of other obvious differences I think this might well be the problem
> here. In your post on Sunday you wrote "libusbK and WinUSB can be used to
> implement the libusb1 interface.". Is it possible to force libusb1 to use
> WinUSB? At least temporarily renaming the dll for a test should work?

Ruben, did you install your driver with zadig? If yes, did you choose
libusbK? Then that's the reason for this.

You can either use zadig again to change to WinUSB, or run my installer
and let it install the drivers. At least, this should work, I have never
tested it.

Beste Grüße

Ruben Groen

unread,
Jun 21, 2020, 3:46:15 PM6/21/20
to ZoomFloppy Users
Hi Spiro / Martin,

I tried so many things so I'm not sure about the driver.

But I did something else, I tried to uninstall the Zoomfloppy like Pete suggested. That was very difficult cause it came every time back. Long story short, I managed to get the Zoomfloppy reported back with the yellow exclamation mark in the device manager.
Then I installed Sipro's *.101 version. Now I did get the red warning sign what I didn't get before. After Installing the Zoomfloppy it is in another place in the device manager. Before it was: something like libusb-win32 folder name, now it is under a folder named: USB-Devices. So there is some change now in the device manager.
Then some testing, at first it looks very promising. Reacting on all commands without error messages, and finally no blinking light anymore, YESSS 

But there was something else going on. After redoing some commands the "status" command gives different outcomes one time it's right "73,cbm dos v3.0 1571,00,00" when I give the command again it says "00, ok,00,00". After a reset command it is okay.
So after the first status command it is okay but as soon as I do another command (any command) it keeps saying " 00, ok,00,00" until I do a reset command.

Any idea what this is, I made some reports, first 2 are the "commands" without and with debug. The other 2 showing the "status" problem.
 (This is there reason why I start the reports now first with the "status" command)  
How stable/unstable is it now? 

Many thanks,

Ruben


Op di 16 jun. 2020 om 22:54 schreef Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net>:
--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
Debug_Report_21_06_002.txt
Debug_Report_21_06_003.txt
Debug_Report_21_06_004.txt
Debug_Report_21_06_001.txt

Ruben Groen

unread,
Jun 21, 2020, 4:18:07 PM6/21/20
to ZoomFloppy Users
....and another error occured with NIBWRITE: it worked before and now I get this error: Successfully loaded G64 file
Error loading plugin 'libusb0.dll': Kan opgegeven module niet vinden.  (126)
Is your X-cable properly configured?



Op zondag 21 juni 2020 21:46:15 UTC+2 schreef Ruben Groen:
Hi Spiro / Martin,

I tried so many things so I'm not sure about the driver.

But I did something else, I tried to uninstall the Zoomfloppy like Pete suggested. That was very difficult cause it came every time back. Long story short, I managed to get the Zoomfloppy reported back with the yellow exclamation mark in the device manager.
Then I installed Sipro's *.101 version. Now I did get the red warning sign what I didn't get before. After Installing the Zoomfloppy it is in another place in the device manager. Before it was: something like libusb-win32 folder name, now it is under a folder named: USB-Devices. So there is some change now in the device manager.
Then some testing, at first it looks very promising. Reacting on all commands without error messages, and finally no blinking light anymore, YESSS 

But there was something else going on. After redoing some commands the "status" command gives different outcomes one time it's right "73,cbm dos v3.0 1571,00,00" when I give the command again it says "00, ok,00,00". After a reset command it is okay.
So after the first status command it is okay but as soon as I do another command (any command) it keeps saying " 00, ok,00,00" until I do a reset command.

Any idea what this is, I made some reports, first 2 are the "commands" without and with debug. The other 2 showing the "status" problem.
 (This is there reason why I start the reports now first with the "status" command)  
How stable/unstable is it now? 

Many thanks,

Ruben


Op di 16 jun. 2020 om 22:54 schreef Spiro Trikaliotis <an-zoomfloppy-users@spiro.trikaliotis.net>:
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-users+unsubscribe@googlegroups.com.

Martin Thierer

unread,
Jun 21, 2020, 4:28:31 PM6/21/20
to ZoomFloppy Users
Hi Ruben,


But I did something else, I tried to uninstall the Zoomfloppy like Pete suggested. That was very difficult cause it came every time back. Long story short, I managed to get the Zoomfloppy reported back with the yellow exclamation mark in the device manager.
Then I installed Sipro's *.101 version. Now I did get the red warning sign what I didn't get before. After Installing the Zoomfloppy it is in another place in the device manager. Before it was: something like libusb-win32 folder name, now it is under a folder named: USB-Devices. So there is some change now in the device manager.

that's good and confirms what we were suspecting. You were still using the old libusb-win32 driver which caused the behaviour you observed.

Then some testing, at first it looks very promising. Reacting on all commands without error messages, and finally no blinking light anymore, YESSS 

But there was something else going on. After redoing some commands the "status" command gives different outcomes one time it's right "73,cbm dos v3.0 1571,00,00" when I give the command again it says "00, ok,00,00". After a reset command it is okay.
So after the first status command it is okay but as soon as I do another command (any command) it keeps saying " 00, ok,00,00" until I do a reset command.

This is perfectly normal. "00, ok,00,00" is the standard response when no error occurred. The drive gives "73,cbm dos v3.0 1571,00,00" response only directly after power on or a reset command. If you always got the "73,cbm dos v3.0 1571,00,00", that was caused by the error you experienced with the libusb-win32 driver. It caused the command to the zoomfloppy that closes the session to fail (that's why the led kept blinking, because the close command is what normally turns it off). So when the next command is issued to the zoomfloppy, it thinks the last command didn't finish and so it sends a reset command to the floppy drive to make sure it is in a known state for the new command. So that's why you always get the "73,cbm dos v3.0 1571,00,00", because the drive was always just reset before the status was queried.
   
How stable/unstable is it now? 

I certainly won't give any guarantees :) There should be a new version out in the next days, but until then you can use the one you have. At least I don't now of any serious issues this driver / opencbm combination has.
 
Martin

Martin Thierer

unread,
Jun 21, 2020, 4:34:34 PM6/21/20
to ZoomFloppy Users
....and another error occured with NIBWRITE: it worked before and now I get this error: Successfully loaded G64 file
Error loading plugin 'libusb0.dll': Kan opgegeven module niet vinden.  (126)
Is your X-cable properly configured?

That's strange. I don't know enough about how nibtools and opencbm work together to give a qualified answer, but could it be that there's still an old version of opencbm around that nibwrite is still using? Maybe in the same directory as the nibtools? Or you might need a newer version of nibtools, but I have a strong feeling my first guess is correct (old opencbm version somewhere).

Martin

Spiro Trikaliotis

unread,
Jun 21, 2020, 4:47:32 PM6/21/20
to ZoomFloppy Users
Hello Ruben,

* On Sun, Jun 21, 2020 at 09:45:58PM +0200 Ruben Groen wrote:
> Then I installed Sipro's *.101 version. Now I did get the red warning sign what
> I didn't get before. After Installing the Zoomfloppy it is in another place in
> the device manager. Before it was: something like libusb-win32 folder name, now
> it is under a folder named: USB-Devices. So there is some change now in the
> device manager.

That's good, now you have the WinUSB driver instead of the libusb-win32
one.

> But there was something else going on. After redoing some commands the "status"
> command gives different outcomes one time it's right "73,cbm dos v3.0
> 1571,00,00" when I give the command again it says "00, ok,00,00". After a reset
> command it is okay.
> So after the first status command it is okay but as soon as I do another
> command (any command) it keeps saying " 00, ok,00,00" until I do a reset
> command.

That's normal behaviour of the floppy!

After a reset, every Commodore floppy outputs its version number
("73,cbm dos v3.0,00,00"). On every other occurrence, it outputs "00,
ok,00,00".

So, this is not a bug, it is exactly like its supposed to be!

Regards,

Spiro Trikaliotis

unread,
Jun 21, 2020, 4:49:05 PM6/21/20
to ZoomFloppy Users
Hello again,

* On Sun, Jun 21, 2020 at 01:18:07PM -0700 Ruben Groen wrote:
> ....and another error occured with NIBWRITE: it worked before and now I get
> this error: Successfully loaded G64 file
> Error loading plugin 'libusb0.dll': Kan opgegeven module niet vinden.  (126)
> Is your X-cable properly configured?

Your nibwrite uses an old install of OpenCBM!

Did you copy the OpenCBM files into the nibtools directory? If yes,
nibtools finds them and tries to use them - this cannot work, because we
are now using libusb-1.0.dll, but your old OpenCBM still searches for
the old libusb0.dll.

You might want to re-install nibtools without copying the OpenCBM files
into its directory.

Regards,

rittwage

unread,
Jun 21, 2020, 9:26:52 PM6/21/20
to ZoomFloppy Users
Yes, grab the latest binaries from https://c64preservation.com/files/nibtools and you should be good. Spiro's latest setup installs the the amd64 OpenCBM if you have x64 OS, so grab the amd64 build of nibtools.

I also had to drop a copy of the libusb 1.0 dll in the folder with nibtools, but that is probably just due to a path error on my setup.

Ruben Groen

unread,
Oct 4, 2020, 3:18:19 PM10/4/20
to ZoomFloppy Users
Hi Guys,

Today I started again to test the ZF.

I created a disk with NIBWRITE and it worked great.

After that I tried to do a NIBREAD but suddenly the ZF wouldn't respond any more like in the beginning.

Only reacts on CBMCTRL RESET and nothing else.

I tried everything, disconnect everything, reboot pc, use other usb port, other 1571 drive. de-installed the ZF driver. Installed again with *.103.

I don't get why I have so many problems with the ZF. One moment working, the other moment nothing working.

I created a log hope you guys know what is going on.

Op ma 22 jun. 2020 om 03:26 schreef rittwage <ritt...@gmail.com>:
Yes, grab the latest binaries from https://c64preservation.com/files/nibtools and you should be good. Spiro's latest setup installs the the amd64 OpenCBM if you have x64 OS, so grab the amd64 build of nibtools.

I also had to drop a copy of the libusb 1.0 dll in the folder with nibtools, but that is probably just due to a path error on my setup.

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/1c7ee336-c320-4322-9057-fff6b07dfdf9o%40googlegroups.com.
Debug_Report_04_10_20.txt

Carsten Jensen

unread,
Oct 5, 2020, 7:02:21 AM10/5/20
to zoomflop...@googlegroups.com


On 04/10/2020 21.18, Ruben Groen wrote:
Hi Guys,

Today I started again to test the ZF.

I created a disk with NIBWRITE and it worked great.

After that I tried to do a NIBREAD but suddenly the ZF wouldn't respond any more like in the beginning.

Only reacts on CBMCTRL RESET and nothing else.

I tried everything, disconnect everything, reboot pc, use other usb port, other 1571 drive. de-installed the ZF driver. Installed again with *.103.

I don't get why I have so many problems with the ZF. One moment working, the other moment nothing working.

I created a log hope you guys know what is going on.


Have you tried if the drive works i.e. in a C64, after this incident?

which drive is it?

does the drive respond in any other way when you try a cbmctrl dir 8, blink, bump whatever?,

and is it set to device 8?


can you try this installer instead?

https://retro-commodore.eu/files/downloads/Tools/OpenCBM%20and%20Tools/

it uses an older opencbm (4.99.98 if I remember correctly). it's not an official installer and not supported by spiro etc,

but then again, I've had loads of positive feedback from people using it.


Virus-free. www.avast.com

mthi...@gmail.com

unread,
Oct 5, 2020, 12:49:55 PM10/5/20
to ZoomFloppy Users
Looks to me as if the ZF can't communicate with the floppy drive. Are you sure the floppy cable is ok? A bad contact might explain why it suddenly stopped working.

Ruben Groen

unread,
Oct 5, 2020, 1:24:00 PM10/5/20
to ZoomFloppy Users
@ Cartsen: Thank you for helping, but I'm not into software that isn't supported by Sipro, he helped me a lot! And it would not help my problem because it all worked fine.

@ Martin: Yes I tried everything, also another IEC cable. Another Drive, all works fine on my C64. So it has to be the ZF. Could it be some loose contact on the ZF PCB? If so, is it not strange that cmbctrl reset still works!? Just like I started.....

Op ma 5 okt. 2020 om 18:49 schreef mthi...@gmail.com <mthi...@gmail.com>:
Looks to me as if the ZF can't communicate with the floppy drive. Are you sure the floppy cable is ok? A bad contact might explain why it suddenly stopped working.

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.

mthi...@gmail.com

unread,
Oct 5, 2020, 2:45:07 PM10/5/20
to ZoomFloppy Users
@ Martin: Yes I tried everything, also another IEC cable. Another Drive, all works fine on my C64. So it has to be the ZF. Could it be some loose contact on the ZF PCB? If so, is it not strange that cmbctrl reset still works!? Just like I started.....

Well, for the reset to go through only one line has to work, so that doesn't mean the rest of the cable is ok. But if it works on a C64, then it's probably not the cable. Btw, what do you mean by "cbmctrl reset" "works" : Does the drive light come on and the motor spin up? Or do you just imply that because there's no error message?

Could you please post the output of "cbmctrl status 8" with LIBUSB_DEBUG=9 set? (Just to be sure, but I doubt that the USB communication is the problem).

Ruben Groen

unread,
Oct 6, 2020, 12:48:03 PM10/6/20
to ZoomFloppy Users
Hi Martin,

Thank you for your quick response and help as always!

I have measured all my IEC cables, I have tried 3 different ones. All are fine.

I have a stack of 3 times 1571 drives to test. All 3 with the latest ROM version *-05.

What I mean is that when I do a CBMCTRL RESET, the drives react with the green light for a few seconds and spinning the motor. Mostly the motor stops after a few seconds but sometimes the motor does NOT stop at all with spinning. Very strange.

I have made 2 reports, CBMCTRL RESET and CBMCTRL STATUS 8.

Hope you can see anything.

Many thanks!





Op ma 5 okt. 2020 om 20:45 schreef mthi...@gmail.com <mthi...@gmail.com>:
@ Martin: Yes I tried everything, also another IEC cable. Another Drive, all works fine on my C64. So it has to be the ZF. Could it be some loose contact on the ZF PCB? If so, is it not strange that cmbctrl reset still works!? Just like I started.....

Well, for the reset to go through only one line has to work, so that doesn't mean the rest of the cable is ok. But if it works on a C64, then it's probably not the cable. Btw, what do you mean by "cbmctrl reset" "works" : Does the drive light come on and the motor spin up? Or do you just imply that because there's no error message?

Could you please post the output of "cbmctrl status 8" with LIBUSB_DEBUG=9 set? (Just to be sure, but I doubt that the USB communication is the problem).

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
Debug_Report_06_10_20_CBMCTRL_STATUS_8.txt
Debug_Report_06_10_20_CBMCTRL_RESET.txt

mthi...@gmail.com

unread,
Oct 6, 2020, 1:54:39 PM10/6/20
to ZoomFloppy Users
Hi Ruben,

thanks for the logs! From what I can tell, I still think the usb communication is working fine and the problem is between the zoomfloppy and the floppy drive. Unfortunately I don't know much about the original zoomfloppy (I don't have one), so I hope someone more experienced with it will weigh in.

I think the ZF has a 7406 output buffer. If it's possible to access the IEC lines with the cable plugged in and you have a multimeter, you could measure the signal levels relative to ground. You have to do this with the IEC cable plugged into both the ZF and the floppy drive and the floppy drive turned on (I don't think anything could happen but maybe better not have a disk in the drive). 

The lines should all measure ~5V when idle. You can then use the "cbmlinetester" command included with opencbm to set and reset individual lines and check the voltage. So for example after a "cbmlinetester -c" the "clock" line should measure near 0V, and after "cbmlinetester -C" it should be back to 5V.

It would also be interesting to know the voltage level of the "reset" line when the motor doesn't stop spinning after a "cbmctrl reset". Also, when this happens: Please check if it stops spinning if you issue a "cbmlinetester -R" command.

Martin

Ruben Groen

unread,
Oct 14, 2020, 6:28:26 AM10/14/20
to ZoomFloppy Users

Hi Martin,

Thanks again, but this is way to complicated for me....

I have ordered a  promicro version on ebay and will resume testing to see where the problem is.

I will inform when it has arrived and did some testing.

Ruben


Op di 6 okt. 2020 om 18:47 schreef Ruben Groen <ruben...@gmail.com>:

Ruben Groen

unread,
Oct 21, 2020, 12:36:56 PM10/21/20
to ZoomFloppy Users
Hi everyone,

I'm desperate! Who can help me???

I received my pro micro XUM1541.

Once the device was plugged in it worked right away, no drivers or software to install.

So the troubles I have with my ZoomFloppy is 100% the hardware of the ZF itselfs because the exact same setup I used with the ZF works with the pro micro. Drive, cable's  everything.

So something of the ZF just broke, no idea what, does some have a hunch? 

I did some tests like a NIBREAD and  that went well.

But then I ran into trouble again. I don't know if it is related but I did a NIBWRITE of a Miami Vice G64 file (it was successful) and I tried to read it on my C64, suddenly my drive began again to make weird noises again. The game did not load but crashed and the C64 rebooted. After that the pro micro can see the drive but not read or write.
When I connected the drive to my C64 I had the same problem as with my other drive. Strange motor noise and "?FILE NOT FOUND ERROR"
So both drives have this problem now, something is "out of balance". 

I have 3 1571 drives, 2 are now not working anymore just by expermenting how is this possible and does someone know if and how to fix it?

I have tried the 1541diagnostic cartridge (worldofjani) but no luck yet.



 

Op wo 14 okt. 2020 om 12:28 schreef Ruben Groen <ruben...@gmail.com>:

SX64 man

unread,
Oct 21, 2020, 1:19:45 PM10/21/20
to ZoomFloppy Users
Your physical drives are most likely fine - what has happened is the copy protected disks have driven the head past track 35 as part of their "bad sectors" protection scheme.
Make your own thin cardstock "transit card", turn the drive off and insert.  It will reset and l push the drive heads back into the proper place so the drives can read proper tracks again.
Ray Carlsen has the answer: (as always!) 
http://personalpages.tds.net/~rcarlsen/cbm/1571/transit.txt

SX64 man

unread,
Oct 21, 2020, 1:20:23 PM10/21/20
to ZoomFloppy Users
The "reverse bump" from the 1541 Jani Cart may also work as well.

On Wednesday, October 21, 2020 at 12:36:56 PM UTC-4 ruben...@gmail.com wrote:

SX64 man

unread,
Oct 21, 2020, 1:24:21 PM10/21/20