ZF: Drive only reacts to "cbmctrl reset"

[Spiro Trikaliotis]

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]

"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]

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]

* 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]

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]

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]

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]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/a4c32a2e-3e7a-48bc-9790-8ad159e9cf21o%40googlegroups.com.

[Ruben Groen]

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]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/65724bb3-f2ca-414b-9607-788e57183dd5o%40googlegroups.com.

[rittwage]

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]

Hello,

Pete, good point!

Ruben, can you answer this?

[Ruben Groen]

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]

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]

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]

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]

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]

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

https://github.com/thierer/OpenCBM/tree/in_ctrl_msg

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]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/851118d2-ca81-4842-a35b-12fd879a6ef4o%40googlegroups.com.

[Martin Thierer]

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]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/bd9f9bdc-4fc9-400c-b148-2b9abad824f7o%40googlegroups.com.

[Ruben Groen]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/4b40f5f1-5d48-49e7-8bec-afb1b025f8f4o%40googlegroups.com.

[Spiro Trikaliotis]

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]

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]

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]

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

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]

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

[Spiro Trikaliotis]

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]

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]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/20200616205439.GH8043%40hermes.local.trikaliotis.net.

[Ruben Groen]

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

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]

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

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]

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]

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]

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.

[Carsten Jensen]

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]

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]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/6388165f-c8dd-4681-bf03-dd13affb5313n%40googlegroups.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).

[Ruben Groen]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/8179b234-fe9e-4a4d-b7a4-7f947f81e984n%40googlegroups.com.

[mthi...@gmail.com]

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]

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]

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]

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]

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]

https://www.google.com/imgres?imgurl=http%3A%2F%2Fpersonalpages.tds.net%2F~rcarlsen%2Fcbm%2F1541%2Ftransit%2520card.jpg&imgrefurl=http%3A%2F%2Fpersonalpages.tds.net%2F~rcarlsen%2Fcbm%2F1541%2F&tbnid=7HDtf2K5-4GZNM&vet=12ahUKEwiWmpHkmcbsAhUcK1kKHYaAA8sQMygAegQIARB_..i&docid=aDhutZlR2NlGBM&w=756&h=498&q=1541%20transit%20card&ved=2ahUKEwiWmpHkmcbsAhUcK1kKHYaAA8sQMygAegQIARB_

[SX64 man]

One thing I did not know and did not mention - the 1571 transit card is slightly different than the original 1541 (see info in first link article put the tab in the correct place)

[RETRO Innovations]

On 10/21/2020 11:36 AM, Ruben Groen wrote:
> 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.

I'm happy to send out another.  THough they are are all tested when they
leave here, some get battered quite a bit and who knows what they endure
on their way to the customer.  Expect a note tomorrow night as I fill
orders.
>
> Jim

[Ruben Groen]

Hello SX64 man,

We thought about something like that too, but forgot to test with the card.

I have an original 251171-03 transit card. I have tried it in both drives with no luck.

Also already tried the Jani Reverse Knock, no luck.

Thank you for helping!

Ruben

Op wo 21 okt. 2020 om 20:16 schreef RETRO Innovations <go4r...@go4retro.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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/bd3717bb-9f4a-42dc-712d-1b350c87f61f%40go4retro.com.

[Ruben Groen]

@ Jim, Many Thanks! I will mail you tomorrow.

Op wo 21 okt. 2020 om 20:16 schreef RETRO Innovations <go4r...@go4retro.com>:

On 10/21/2020 11:36 AM, Ruben Groen wrote:

--
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/bd3717bb-9f4a-42dc-712d-1b350c87f61f%40go4retro.com.

[Spiro Trikaliotis]

Hello Jim,

I don't want to be nitpicking, but: If the ProMicro based device has the
same problem now (or the floppy you have connected to it?), I doubt it
is a problem of the ZF.

Let's have a look at the tests which I will write in another mail.

Regards,
Spiro.

--
Spiro R. Trikaliotis

https://spiro.trikaliotis.net/

[Spiro Trikaliotis]

Hello Ruben,

* On Wed, Oct 21, 2020 at 06:36:43PM +0200 Ruben Groen wrote:

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

Let's start with debugging the communication.

Can you please connect one of the "broken" drives and issue the
following commands from the PC side:

cbmctrl download 8 0x8000 0x8000 rom1.bin

and again

cbmctrl download 8 0x8000 0x8000 rom2.bin

The commands needs some minutes to execute, so, please be patient. Wait
at least 5 minute before assuming that something went wrong.

Are the files rom1.bin and rom2.bin both 32768 byte in size?

Then, compare the files rom1.bin and rom2.bin. On Windows, this can be
done with

fc /b rom1.bin rom2.bin

On Linux, just try

diff rom1.bin rom2.bin


If the files have the size of 32768 byte and are equal, than the
communication of the ZF with the drive works.


Another test to do in order to find out if the drive has a problem is to
try to format a disk.

Either use

cbmctrl pcommand 8 n0:name,id

on the PC side, or

OPEN 1,8,15,"N0:NAME,ID"

on the C64 side with a disk in the drive which will be erased.

Does the command succeed? Can you have a look at the directory
afterwards?

[Spiro Trikaliotis]

* On Wed, Oct 21, 2020 at 10:20:23AM -0700 SX64 man wrote:
> The "reverse bump" from the 1541 Jani Cart may also work as well.

Is the "reverse bump" any different from the drive starting to format
and doing the bump (or not doing it if it has a track 0 sensor)?

[RETRO Innovations]

On 10/21/2020 2:11 PM, Spiro Trikaliotis wrote:
> Hello Jim,
>
> * On Wed, Oct 21, 2020 at 01:16:41PM -0500 RETRO Innovations wrote:
>> On 10/21/2020 11:36 AM, Ruben Groen wrote:
>>> 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.
>> I'm happy to send out another.  THough they are are all tested when they
>> leave here, some get battered quite a bit and who knows what they endure on
>> their way to the customer.  Expect a note tomorrow night as I fill orders.
> I don't want to be nitpicking, but: If the ProMicro based device has the
> same problem now (or the floppy you have connected to it?), I doubt it
> is a problem of the ZF.

I agree.  I read Ruben's comment as the ZF would not work, and the Pro
Micro did (then it developed another problem, but I was under the
impression the Pro Micro still will read the status channel and such,
while the ZF will not).

>
> Let's have a look at the tests which I will write in another mail.

But yes, if both units are now suffering from the same issue, my comment
will be different.

Jim

[Ruben Groen]

Hello Spiro,

You could be right I’m just a simple user. But the difference now is that ZoomFloppy only reacts on “cbmctrl reset” and nothings else with my “broken” 1571 drives. And the Pro micro still reacts with “cbmctrl reset, status 8, detect 8”, but with “cbmctrl dir 8” it fails but that’s the drive problem.
I will do some more tests tomorrow, I have some other drives 1541 or 1541 II.
I have one good 1571 drive left so that one I’m not going to use until the problems are solved.
If you have suggestions how an what to test I would gladly do.
I can make video’s if necessary.
All help is welcome.
Thanks to all!

Ruben

> Op 21 okt. 2020 om 21:11 heeft Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net> het volgende geschreven:
>
> Hello Jim,

> --
> 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/20201021191106.GA1898%40hermes.local.trikaliotis.net.

[Ruben Groen]

Hi Spiro,

I just read these suggestions, I will do those tomorrow.

I will let you know.

Ruben

> Op 21 okt. 2020 om 21:16 heeft Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net> het volgende geschreven:
>
> Hello Ruben,

> --
> 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/20201021191558.GB1898%40hermes.local.trikaliotis.net.

[Ruben Groen]

Hi Jim,

You where right. There still is a difference between the 2 devices.

Ruben

> Op 21 okt. 2020 om 21:18 heeft RETRO Innovations <go4r...@go4retro.com> het volgende geschreven:

> --
> 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/bf91cd46-bcbe-83a0-c91c-61b0e627b1af%40go4retro.com.

[ruben...@gmail.com]

Hi Spiro,

This is what happens:

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin

could not open output file: rom1.bin: Toegang geweigerd.

download:  Access denied.

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin

could not open output file: rom2.bin: Toegang geweigerd.

download: Access denied.

C:\Program Files\opencbm>cbmctrl pcommand 8 n0:name,id

C:\Program Files\opencbm>

Does not format.

Ruben

Op woensdag 21 oktober 2020 om 21:16:01 UTC+2 schreef Spiro Trikaliotis:

[ruben...@gmail.com]

Hi Sipro,

OPEN 1,8,15,"N0:NAME,ID" 

It reacts  on the command and seems to do something but when done the green light keeps blinken and when I do a LOAD"$",8 it does SEARCHING FOR $ and then ?FILE NOT FOUND ERROR. The same disk loads fine in another drive.

Ruben

Op woensdag 21 oktober 2020 om 21:16:01 UTC+2 schreef Spiro Trikaliotis:

Hello Ruben,

[ruben...@gmail.com]

Hi Spiro,

The same test on same drive with Pro Micro:

C:\Program Files\opencbm>cbmctrl reset

C:\Program Files\opencbm>cbmctrl status 8

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

C:\Program Files\opencbm>cbmctrl detect 8

 8: 1571

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin

could not open output file: rom1.bin: Toegang geweigerd.

download: Toegang geweigerd.

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin

could not open output file: rom2.bin: Toegang geweigerd.

download: Toegang geweigerd.

C:\Program Files\opencbm>cbmctrl dir 8

74,drive not ready,00,00

C:\Program Files\opencbm>

As you can see with the same setup the "broken" drive still reacts on status and detect and the ZF does not. But with a dir 8 the problem occurs.

Because almost everything seems to work accept read and write on both drives...

-------------------------------------------------------

Same test with Pro Micro and 1541-II:

C:\Program Files\opencbm>cbmctrl reset

C:\Program Files\opencbm>cbmctrl status 8

73,cbm dos v2.6 1541,00,00

C:\Program Files\opencbm>cbmctrl detect 8

 8: 1541-II

C:\Program Files\opencbm>cbmctrl dir 8

0 ."0               " 05 2a

664 blocks free.

00, ok,00,00

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin

could not open output file: rom1.bin: Access denied.

download: Toegang geweigerd.

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin

could not open output file: rom2.bin:  Access denied. 

download: Toegang geweigerd.

C:\Program Files\opencbm>cbmctrl pcommand 8 n0:name,id

C:\Program Files\opencbm>cbmctrl dir 8

0 ."name            " id 2a

664 blocks free.

00, ok,00,00

C:\Program Files\opencbm>

As you can see the disk loads and also formats.

Ruben

Op woensdag 21 oktober 2020 om 21:16:01 UTC+2 schreef Spiro Trikaliotis:

Hello Ruben,

[ruben...@gmail.com]

Hi Spiro,

The Access denied was a administrator problem.

Test it with the Pro Micro and 1541-II and okay:

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin

................o

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin

................o

both Rom files are 32kb

C:\Program Files\opencbm>fc /b rom1.bin rom2.bin

Comparing files rom1.bin and ROM2.BIN

FC: no differences encountered

C:\Program Files\opencbm>

Test it with the Pro Micro and the "broken" 1571:

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin

................o

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin

................o

This is strange! Both rom files are 0kb

C:\Program Files\opencbm>fc /b rom1.bin rom2.bin

Comparing files rom1.bin and ROM2.BIN

FC: no differences encountered

Test it with ZoomFloppy and same "broken"  1571:

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin

.,A transfer error occurred!

C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin

.,A transfer error occurred!

C:\Program Files\opencbm>

Ruben

Op woensdag 21 oktober 2020 om 21:16:01 UTC+2 schreef Spiro Trikaliotis:

Hello Ruben,

[Tregare]

try cbmctrl download 8 0x8000 0x7fff 1571rom1.bin

unless my math is wrong , 0x8000 plus 0x7FFF is 0xFFFF. since the rom starts at 0x8000 it should only be 0x7FFF long.

--

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/b6410239-4a91-4552-9c34-90d729f18aadn%40googlegroups.com.

[Spiro Trikaliotis]

Hello Ruben,

* On Thu, Oct 22, 2020 at 08:26:03AM -0700 ruben...@gmail.com wrote:

> Test it with the Pro Micro and 1541-II and okay:
>
> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin
> ................o
> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin
> ................o
>
> both Rom files are 32kb

Are they exactly 32768 byte long?

> C:\Program Files\opencbm>
>
> Test it with the Pro Micro and the "broken" 1571:
>
> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin
> ................o
> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin
> ................o
>
> This is strange! Both rom files are 0kb

This means that there has been a transfer problem. cbmctrl is not very
verbose here.

> Test it with ZoomFloppy and same "broken" 1571:
>
> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin
> .,A transfer error occurred!
>
> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin
> .,A transfer error occurred!
>
> C:\Program Files\opencbm>

Ok. So, the transfer starts, and some things are transmitted. However,
it stops somewhere. This means the transfer is not reliable.

If the 1541-II would not work, I would have said that your XUM1541
(ProMicro) is broken. However, as the 1541-II works, this is unlikely.

It is either a broken 1571 (which you already assume), or we have a very
subtle bug in the IEC routines. But: I doubt it.

Which version of OpenCBM do you have? 0.4.99.103? (I ask because there
was a "fix" to make cbmctrl download more robust, which could hide a
problem with the 1541-II)

Can you repeat the test with the 1541-II some times, and does it always
succeed?

[Spiro Trikaliotis]

* On Fri, Oct 23, 2020 at 12:34:12PM -0700 Tregare wrote:
> try cbmctrl download 8 0x8000 0x7fff 1571rom1.bin

No!

> unless my math is wrong ,

it is!

> 0x8000 plus 0x7FFF is 0xFFFF. since the rom starts at
> 0x8000 it should only be 0x7FFF long.

The area from 0x8000 to 0x8000 is 1 byte long. (0x8000 - 0x8000 + 1)
The area from 0x8000 to 0x80FF is 256 (= 0x0100) byte long. (0x80FF - 0x8000 + 1)
The area from 0x8000 to 0x8FFF is 4096 (= 0x1000) byte long. (0x8FFF - 0x8000 + 1)
The area from 0x8000 to 0xFFFF is 32768 (= 0x8000) byte long. (0xFFFF - 0x8000 + 1)

[Tregare]

Ty spiro, I haven’t had to do hex math in a while

--
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/20201023213125.GG1898%40hermes.local.trikaliotis.net.

[Carsten Jensen]

>> Test it with ZoomFloppy and same "broken" 1571:
>>
>> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom1.bin
>> .,A transfer error occurred!
>>
>> C:\Program Files\opencbm>cbmctrl download 8 0x8000 0x8000 rom2.bin
>> .,A transfer error occurred!
>>
>> C:\Program Files\opencbm>

As a side note, have you checked the power supplies of your drives?

they should give 5v and 12v out


It has been seen (first hand) that a 1541-II psu was defective, giving
higher voltages

and while it seemed ok, it gave very strange behaviors.

If the psu is not OK it could have permanently affected your transfer
devices.


/Carsten




--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[Ruben Groen]

Hi Guys,

A quick update for so far: 

The read/write problem is finally solved!!!! It was my stupid own stubborness. My drives where just serviced all 3 and "heads" were cleaned. I use all brand new old stock 3M floppy disks (sealed boxes). So I was so sure that it could not be the obvious, but it was!! I cleaned the "heads" and I can read floppy's again on my C64. I do have another problem to solve, because both drives don't stop spinning, new challenge.... to be continued....

@  Carsten thank you for thinking along,  but I guess power is good so far. But we will keep it in mind.

@ Spiro the both rom's of the test with Pro Micro and 1541-II are indeed both the same and 32.768.

I hope to continue testing tomorrow.

Ruben

Op za 24 okt. 2020 om 10:06 schreef Carsten Jensen <toms...@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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/170928aa-1038-40fe-412d-a093db94e0a6%40gmail.com.

[Ruben Groen]

I just tested a NIBWRITE but it failed:

Successfully loaded G64 file

Using device #8

Drive Version: 73,CBM DOS V3.0 1571,00,00

Drive type: 1571

Bumping...

Initializing

Sending 1571 SRQ support code...

Uploading floppy-side code ($0454 bytes, $300-$754)...done.

Starting custom drive code...Started!

Testing communication...done.

Passed initial communication test.

Testing code upload...done.

Passed code verification test.

Passed all basic port checks.

Testing track capacity at each density

--------------------------------------------------

USB error in xum1541_ioctl cmd: LIBUSB_ERROR_IO

USB error in xum1541_ioctl cmd: LIBUSB_ERROR_IO

What could this be?

Ruben

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

[Ruben Groen]

@ Spiro, I now managed to download the rom from the 1571 with the Pro Micro.

both files are the same and 32.768.

The ZF still gives a "transfer error occurred!"

I formatted a floppy on that drive with my C128 and formatted  1328 Blocks Free, I also formatted on my C64 664 Blocks free and could access the directory (List)

I use your *.103 version.

Ruben

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

[Spiro Trikaliotis]

Hello Ruben,

* On Wed, Oct 28, 2020 at 07:28:09PM +0100 Ruben Groen wrote:
> @ Spiro, I now managed to download the rom from the 1571 with the Pro Micro.
> both files are the same and 32.768.
> The ZF still gives a "transfer error occurred!"

That's weird.

Can you send me one of the files, so I can have a look if it look ok?

Also: You can compile OpenCBM yourself, can't you?

In the file opencbm/lib/upload.c, can you please modify the lines 35 and
36 from

enum { RETRIES_UPLOAD = 5 }; //!< \brief how many retries to do when communication errors occur on upload
enum { RETRIES_DOWNLOAD = 5 }; //!< \brief how many retries to do when communication errors occur on download

to

enum { RETRIES_UPLOAD = 1 }; //!< \brief how many retries to do when communication errors occur on upload
enum { RETRIES_DOWNLOAD = 1 }; //!< \brief how many retries to do when communication errors occur on download

(that is, change the numbers "5" to "1")

compile and install OpenCBM and try the "cbmctrl download" command again?

Does it still result in a file of 32768 byte?

> I formatted a floppy on that drive with my C128 and formatted  1328 Blocks
> Free, I also formatted on my C64 664 Blocks free and could access the directory
> (List)
> I use your *.103 version.

So, if I understand you correctly, you have two problems at the moment:

1. The "transfer error occurred" after the download of the ROM file
2. The USB error when using nibtools.

Other than that, everything looks as if it works as expected?

[Ruben Groen]

Hello Spiro,

Yes it is very weird, I still have the suspicion that the ZF is broken somehow.

Sorry I can't compile.

I will send you the rom files.

Yes I know it's all very confusing at the moment.

I have 2 problems right now:

1) I have 1 ZF that only reacts on cbmctrl reset and nothing else, but it has worked before. That's why I think I got the "transfer error occurred".

2) The Pro Micro seems to work fine (reacts on all commands, also formatting and coping D64 to floppy) but gives an error with NIBWRITE, seems an USB driver error.

Ruben

Op wo 28 okt. 2020 om 20:58 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.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/20201028195849.GB23902%40hermes.local.trikaliotis.net.

[Nate Lawson]

> On Oct 28, 2020, at 1:29 PM, Ruben Groen <ruben...@gmail.com> wrote:
>
> 2) The Pro Micro seems to work fine (reacts on all commands, also formatting and coping D64 to floppy) but gives an error with NIBWRITE, seems an USB driver error.

The error is just a general one when the device didn’t respond.

Are you using nibwrite with a 1571 drive (and SRQ nibbling)?

-Nate

[Raj Wurttemberg]

Hey Ruben,

I tried to follow this thread back as far as I could.  Are you doing this under Windows (10?) or Linux (distro?)?  Let me know what your setup is, end-to-end and I'll try and set up a system just like yours to see if I can duplicate the issues you are experiencing.

/Raj

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/CAFCST02G5QJd1RcJ8qd_bC0Dwye_hZapX1qL6-n6vXSuZ-HR%3Dg%40mail.gmail.com.

[Ruben Groen]

Hello Nate,

Yes your are right! I use a 1571! SRQ not 100% sure but I guess that goes automatically. 

I did a NIBWRITE and location of the file. No extra commands but if I look at the log I see 1571 SRQ support code

 “Successfully loaded G64 file

Using device #8

Drive Version: 73,CBM DOS V3.0 1571,00,00

Drive type: 1571

Bumping...

Initializing

Sending 1571 SRQ support code...

Uploading floppy-side code ($0454 bytes, $300-$754)...done.

Starting custom drive code...Started!

Testing communication...done.

Passed initial communication test.

Testing code upload...done.

Passed code verification test.

Passed all basic port checks.

Testing track capacity at each density

--------------------------------------------------

USB error in xum1541_ioctl cmd: LIBUSB_ERROR_IO

USB error in xum1541_ioctl cmd: LIBUSB_ERROR_IO”

So what do you think is going wrong?

Ruben

Op 28 okt. 2020 om 21:47 heeft Nate Lawson <na...@root.org> het volgende geschreven:



--
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/1C018DEE-39B0-43C2-A306-BC4A5B692BC2%40root.org.

[Ruben Groen]

Hello Raj,

I do use windows 10 pro 64bits. 

Thanks for helping!

What do you all need to know?

Ruben 

Op 28 okt. 2020 om 21:55 heeft Raj Wurttemberg <ra...@c64.us> het volgende geschreven:



To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/CAF%3DTY61BC1KcqkDDjjcQu4feMoq7DdgNi22imV3Dd_%3DcmuWR3g%40mail.gmail.com.

[Ruben Groen]

@ Nate forgot to mention, this test was done with a Pro Micro because of my failing ZF at the moment. 

Ruben

Op 28 okt. 2020 om 22:38 heeft Ruben Groen <ruben...@gmail.com> het volgende geschreven:



[Raj Wurttemberg]

Hey Ruben,

OK.  So Windows 10 ---> USB cable --->  Zoom Floppy --->  IEC ----> [ I571?? ]

Is that right?

/Raj

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/73ECFC95-43CF-4ED6-9167-96D906C1591F%40gmail.com.

[Raj Wurttemberg]

Alrighty!  I think I'm setup like you:

C:\Program Files\opencbm>cbmctrl detect
 8: 1571

C:\Program Files\opencbm>cbmctrl status 8
73,cbm dos v3.0 1571,00,00

I formatted  fresh floppy and did a directory

C:\Program Files\opencbm>cbmctrl.exe dir 8
0 ."testdisk        " 01 2a

664 blocks free.
00, ok,00,00

What can I test or compare for you?

/Raj

[Raj Wurttemberg]

These are my install notes for a fresh install of OpenCBM and the nibtools:

- Downloaded OpenCBM from here:
https://opencbm.trikaliotis.net/opencbm-8.html
http://www.trikaliotis.net/Download/opencbm-0.4.99.99/opencbm-0.4.99.99.zip

- Downloaded Zadig: https://github.com/pbatard/libwdi/releases/download/b730/zadig-2.5.exe

- Connected ZoomFloppy
- Ran Zadig and changed the driver to libusb-win32

- Opened admin command prompt
- Changed to directory with OpenCBM (example c:\zf\opencbm

- Typed 'install zoomflopy'.  Install completed successfully:
=== OpenCBM v0.4.99.99 for  ZoomFloppy
=== installation done

- Added 'C:\Program Files\opencbm' to the path

C:\Program Files\opencbm>cbmctrl detect
 8: 1571
 
C:\Program Files\opencbm>cbmctrl status 8
73,cbm dos v3.0 1571,00,00

- Downloaded nibtools from here:
https://c64preservation.com/files/nibtools/

- Copied the nibtools to,  'C:\Program Files\opencbm'

- Did a d64copy.  Looks good:

C:\Program Files\opencbm>d64copy.exe -vv 8 testdisk.d64
[Debug] transfer mode is 0
[Debug] decided to use transfer mode 3
[Info] Trying to identify drive type
[Info] drive 08 (1571): 00, OK,00,00
[Warning] growing image file to 683 blocks
[Info] copying tracks 1-35 (683 sectors)
 1: *********************
 2: *********************
 3: *********************
 4: *********************
 
- Did a nibread. Looks good:
 
C:\Program Files\opencbm>nibread.exe 8 testdisk.nib

nibread - Commodore 1541/1571 disk image nibbler
(C) Peter Rittwage
http://c64preservation.com
Built Oct 21 2020 10:30:50

Drive Version: 73,CBM DOS V3.0 1571,00,00
Drive type: 1571
Bumping...
Initializing
Sending 1571 SRQ support code...
Uploading floppy-side code ($0454 bytes, $300-$754)...done.
Starting custom drive code...Started!
Testing communication...done.

Passed basic communication test.

18.0: (2)
Cosmetic Disk ID: '01'
Format Disk ID: '01'

 1.0: (3) 7681 [CBM OK]
 2.0: (3) 7681 [CBM OK]
 3.0: (3) 7681 [CBM OK] (weakgcr:1)
 4.0: (3) 7681 [CBM OK]
 

- Did a nibwrite:

C:\Program Files\opencbm>nibwrite.exe -D8 disk01.g64

nibwrite - Commodore 1541/1571 disk image 'remastering' tool
(C) Peter Rittwage
http://c64preservation.com
Built Oct 21 2020 10:30:50

* Use Device 8

Reading G64 file...
Tracks:84
Size:7928
 1.0: (3:7681) 0%
.
.
.
 41.0: (1:6779) 100%

Successfully loaded G64 file
Using device #8
Drive Version: 73,CBM DOS V3.0 1571,00,00
Drive type: 1571
Bumping...
Initializing
Sending 1571 SRQ support code...
Uploading floppy-side code ($0454 bytes, $300-$754)...done.
Starting custom drive code...Started!
Testing communication...done.

Passed basic communication test.

Testing track capacity at each density
--------------------------------------------------

Density 0: 6241 6242 (300.43rpm) margin:1
Density 1: 6658 6657 (300.44rpm) margin:1
Density 2: 7133 7133 (300.41rpm) margin:0
Density 3: 7681 7681 (300.44rpm) margin:0
--------------------------------------------------
Drive motor speed average: 300.43 RPM.
Track capacity margin: 6

 1.0: (3:7681) WRITE
 2.0: (3:7681) WRITE
 3.0: (3:7681) WRITE [weak:1]
 4.0: (3:7681) WRITE
 .
 .
 .

So far, everything worked.

/Raj

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/CAFCST01qMrrFxAR5fEH9_OD4caF5vB2rKvn3_T_AecSTJxgimg%40mail.gmail.com.

[Nate Lawson]

There was a bug in 1571 SRQ mode that was introduced in v8 in 2018 (or 2017?). In any case, upgrade to the latest firmware as of Sept 2019 and you’ll be fine.

-Nate

> To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/1B68E4AD-F01E-40AC-ABD9-9BDDF1A8EC26%40gmail.com.

[Ruben Groen]

Hello Nate,

Thank you that could really be the problem, I checked my Pro Micro and it has V07 firmware.

Can you send me the V08 Pro Micro firmware? Or where to find it? And the command line for updating?

Ruben 

Op do 29 okt. 2020 om 01:55 schreef Nate Lawson <na...@root.org>:

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/213BE376-5072-411B-861F-C2E9D7C1945C%40root.org.

[Ruben Groen]

Hello Raj,

No I idea how you got this working, I never managed it this way, because of Windows 10 drivers.

I uninstalled all ZF usb drivers like Pete described and then installed Spiro's *.103 version with the "new" Windows 10 drivers.

After that it finally worked with V08 firmware. So I use a completely different setup then you do now. Other USB drivers and opencbm version.

But pretty soon after that my ZF stopt working.

So we are first now finding out what is wrong with it. In the meantime I bought a Pro Micro from eBay to test everything else to find out the problem of the ZF. (so excluding things like cables drives etc.)

Everything seems to be working fine with the Pro Micro now except nibbling but that is probably the firmware issue.

With Spiro we are looking into whether my ZF is not working any more.

Ruben

Op do 29 okt. 2020 om 00:51 schreef Raj Wurttemberg <ra...@c64.us>:

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/CAF%3DTY62agqsG13uKpGQpb3LHfVzZdNtVxsWNsSsUFW8%2BBPZTcw%40mail.gmail.com.

[Ruben Groen]

Hi Nate,

I tried this, but this is not working:

C:\Program Files\opencbm>xum1541cfg devinfo
finding device...
xum1541 device, model 5 (PROMICRO), firmware version 7

C:\Program Files\opencbm>xum1541cfg -t PROMICRO update xum1541-ZOOMFLOPPY-v08.hex
finding and preparing device for update...
error: device type 5 does not match firmware type 2

Ruben

Op do 29 okt. 2020 om 01:55 schreef Nate Lawson <na...@root.org>:

There was a bug in 1571 SRQ mode that was introduced in v8 in 2018 (or 2017?). In any case, upgrade to the latest firmware as of Sept 2019 and you’ll be fine.

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/213BE376-5072-411B-861F-C2E9D7C1945C%40root.org.

[RETRO Innovations]

On 10/29/2020 3:16 AM, Ruben Groen wrote:
> Hello Nate,
>
> Thank you that could really be the problem, I checked my Pro Micro and
> it has V07 firmware.
> Can you send me the V08 Pro Micro firmware? Or where to find it? And
> the command line for updating?

There should be a copy of the firmware in the opencbm directories, along
with a program to update.

Jim

[Raj Wurttemberg]

I don't know if this is the official location but I found the 08 version here:

https://github.com/zyonee/opencbm/tree/master/xum1541

I don't have a ProMicro but I found these instructions for installing the firmware:

https://github.com/tebl/C64-XUM1541/blob/master/documentation/firmware.md

(My ZF with 07 runs fine. Should I upgrade it?)

/Raj

--
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/2efb3d39-132f-d766-4eb0-ef47e3b72188%40go4retro.com.

[Nate Lawson]

This is exactly why forks are bad. The v8 in zyonee/opencbm was built with an old version of the board .h file that still has the bug in iec_srq_write(). The version of code in the official repo is fixed so you can build it there:

https://github.com/OpenCBM/OpenCBM/tree/master/xum1541

Any reason you can't buy a ZoomFloppy instead? I make nothing from this but at least it’s only a single board to support.

-Nate

> To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/CAF%3DTY60fVhMK-T7TGHmrOcPW9bV1OL%2BW6oLnBAXKDo-NuMXAvw%40mail.gmail.com.

[Raj Wurttemberg]

Agreed completely.  Do you think that we could get a link to the official GitHub repo on the instructions web site?

(https://opencbm.trikaliotis.net/opencbm-8.html). I could be wrong, but I don't think that the location for the firmware is mentioned.

Sometimes finding the correct information for this project can be a fair amount of work. 

Appreciate everyone's hard work and dedication to this project!  You guys are amazing!

/Raj

To view this discussion on the web visit https://groups.google.com/d/msgid/zoomfloppy-users/5153B55F-6BB1-4FF8-9C8E-99A4E836C0C9%40root.org.

[Spiro Trikaliotis]

Hello,

For some reason unknown to me, the firmware for the PROMICRO was *not* in
the repo!

It seems I forgot to add it.

I re-compiled and pushed it, it is available now.

Note: You must know if it is a PROMICRO with 7406 inverter (file
xum1541/xum1541-PROMICRO_7406-v08.hex), or one without inverter (file
xum1541/xum1541-PROMICRO-v08.hex).

YOU MUST USE THE RIGHT ONE!

You can find the files online here:
https://github.com/OpenCBM/OpenCBM/tree/master/xum1541


However, it is not easy to flash it. At the moment, xum1541cfg is not
able to flash it! The PROMICRO uses 32U4, while the ZF uses 32U2 µC. So,
xum1541cfg does not recognise the PROMICRO once it is in bootloader
mode.

Additionally, the v07 firmware did not support going into bootloader
mode at all! This has been fixed with v08, but this does not help anyone
with a v07 firmware.

Thus, to flash the PROMICRO, you need an ISP programmer at the moment,
that is, an external device.

That's a limitation of the PROMICRO implementation.

[Spiro Trikaliotis]

* On Thu, Oct 29, 2020 at 11:20:01AM -0400 Raj Wurttemberg wrote:
> I don't know if this is the official location but I found the 08 version here:
>
> https://github.com/zyonee/opencbm/tree/master/xum1541

The zyonee repository has been integrated into the official OpenCBM one.
Please, use that instead.

> I don't have a ProMicro but I found these instructions for installing the
> firmware:
>
> https://github.com/tebl/C64-XUM1541/blob/master/documentation/firmware.md

Unfortunately, this only works if there is no firmware yet on the
PROMICRO. If it already has one, it does not work, as you cannot set it
back into bootloader mode that easily.

(This is not completely true: As the PROMICRO has the bootloader, you
might have luck getting it to work. However, at least my PROMICRO had a
timeout of 1 second. In this time, my Linux did not even recognize the
device, so I could not flash it. I re-compiled the firmware myself after
setting a longer firmware, and now, I can do it with avrdude.

So, this might be worth a try additionally to what I wrote in my last
mail about needed an external device.

> (My ZF with 07 runs fine. Should I upgrade it?)

If you use IEEE 488 devices, especially the 2031 floppy: Yes.

Otherwise, most probably not.

[Spiro Trikaliotis]

* On Thu, Oct 29, 2020 at 01:25:35PM -0400 Raj Wurttemberg wrote:
> Agreed completely.  Do you think that we could get a link to the official
> GitHub repo on the instructions web site?
> (https://opencbm.trikaliotis.net/opencbm-8.html). I could be wrong, but I don't
> think that the location for the firmware is mentioned.

While I do not think that it belongs in this section, we could add a
section on how to add the firmware. This is very xum1541 specific,
though.

I see that xum1541cfg is not even mentioned in the manual. This might
not be optimal.

Any text proposals are welcome! :)

> Sometimes finding the correct information for this project can be a fair amount
> of work. 

Understood. But, please understand that I am not good in writing
documentation for an end-user. I always take the view of a developer.
So, I have to depend on others contributing here.

There are many blog posts and other articles about OpenCBM out there.
Unforunately, many of them are really outdated or take shortcuts that I
would not recommend, as they might break.

From my point of view, instead of everyone writing about his
experiences, it would be much more helpful for everyone if these people
would try to help to improve the official documentation, so anyone can
see it.

But, I guess this is one of the downsides of modern technology where
everyone can setup a blog or write on social media or whatever.

[Spiro Trikaliotis]

Hello Ruben,

* On Thu, Oct 29, 2020 at 09:38:55AM +0100 Ruben Groen wrote:

> I tried this, but this is not working:

As I wrote elsewhere: It will not work, because:

> C:\Program Files\opencbm>xum1541cfg devinfo
> finding device...
> xum1541 device, model 5 (PROMICRO), firmware version 7

1. this firmware version of the PROMICRO does not support going into
bootloader mode, so you won't be able to do this.

> C:\Program Files\opencbm>xum1541cfg -t PROMICRO update xum1541-ZOOMFLOPPY-v08.hex

2. You are using the wrong firmware. As the old one identifies as
model 5 (PROMICRO), you need xum1541-PROMICRO-v08.hex

If it were model 6 (PROMICRO_7406), as I have one, it would be
xum1541-PROMICRO_7406-v08.hex, but this is not the case for you

3. For some reason I do not understand at the moment, xum1541cfg does
not want to work with the PROMICRO at all, even with the v08
firmware. This might be related to the 32U2 vs 32U4 processor
difference, I did not investigate yet, though.

> finding and preparing device for update...
> error: device type 5 does not match firmware type 2

You can be happy of this test: It found out that you wanted to flash a
firmware of type 2 (ZOOMFLOPPY) on a device of type 5 (PROMICRO).

Without it, if the flash had succeeded, you would have bricked your
device. With an ISP programmer, you should be able to unbrick it again,
but without it, your chances are low to get it working again.

[Spiro Trikaliotis]

Hello Raj,

* On Wed, Oct 28, 2020 at 07:51:16PM -0400 Raj Wurttemberg wrote:
> These are my install notes for a fresh install of OpenCBM and the nibtools:
>
> - Downloaded OpenCBM from here:
> https://opencbm.trikaliotis.net/opencbm-8.html
> http://www.trikaliotis.net/Download/opencbm-0.4.99.99/opencbm-0.4.99.99.zip

NO, please!

> - Downloaded Zadig: https://github.com/pbatard/libwdi/releases/download/b730/
> zadig-2.5.exe

Again, NO!

Note that your notes are outdated. DON'T DO THIS!

[Spiro Trikaliotis]

Hello Ruben,

* On Wed, Oct 28, 2020 at 09:29:28PM +0100 Ruben Groen wrote:
> Hello Spiro,
>
> Yes it is very weird, I still have the suspicion that the ZF is broken somehow.
>
> Sorry I can't compile.

I forgot you are on Windows.

I will try to generate a DLL at the weekend, and I will send it to you,
so you can have a test.

> I will send you the rom files.

They are ok.

> 1) I have 1 ZF that only reacts on cbmctrl reset and nothing else, but it has
> worked before. That's why I think I got the "transfer error occurred".

I make a proposal: Send the ZF to me via mail, and I will have a look. I
believe it is cheaper and should be faster from the NL (am I right?) to
Germany than to the U.S., right?

> 2) The Pro Micro seems to work fine (reacts on all commands, also formatting
> and coping D64 to floppy) but gives an error with NIBWRITE, seems an USB driver
> error.

Yes, the NIBWRITE error seems to be the firmware problem Nate mentioned.
I forgot about that.

[Nate Lawson]

> On Oct 29, 2020, at 2:29 PM, Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net> wrote:
>
> However, it is not easy to flash it. At the moment, xum1541cfg is not
> able to flash it! The PROMICRO uses 32U4, while the ZF uses 32U2 µC. So,
> xum1541cfg does not recognise the PROMICRO once it is in bootloader
> mode.

I could update xum1541cfg for this. I think there’s a way to tell the device model for the firmware image.

> Additionally, the v07 firmware did not support going into bootloader
> mode at all! This has been fixed with v08, but this does not help anyone
> with a v07 firmware.

You mean this was buggy for the ProMicro only or also ZoomFloppy?

-Nate

[Raj Wurttemberg]

Hey Spiro,

I guess I'm confused.  I was following the instructions (for Windows) from this site:

https://opencbm.trikaliotis.net/opencbm-8.html

Is there a better or different set of instructions?   I'm happy to help with the documentation.  Your skills on the actual program itself are greatly appreciated.

Thanks,

/Raj

--
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/20201029215000.GG23902%40hermes.local.trikaliotis.net.

[Carsten Jensen]

changed from ZF: Drive only reacts to "cbmctrl reset"

On 29/10/2020 22.39, Spiro Trikaliotis wrote:
> * On Thu, Oct 29, 2020 at 01:25:35PM -0400 Raj Wurttemberg wrote:
>> Agreed completely.  Do you think that we could get a link to the official
>> GitHub repo on the instructions web site?
>> (https://opencbm.trikaliotis.net/opencbm-8.html). I could be wrong, but I don't
>> think that the location for the firmware is mentioned.
> While I do not think that it belongs in this section, we could add a
> section on how to add the firmware. This is very xum1541 specific,
> though.
>
> I see that xum1541cfg is not even mentioned in the manual. This might
> not be optimal.
>
> Any text proposals are welcome! :)
>
>> Sometimes finding the correct information for this project can be a fair amount
>> of work.
> Understood. But, please understand that I am not good in writing
> documentation for an end-user. I always take the view of a developer.
> So, I have to depend on others contributing here.
>
> There are many blog posts and other articles about OpenCBM out there.
> Unforunately, many of them are really outdated or take shortcuts that I
> would not recommend, as they might break.
>
> From my point of view, instead of everyone writing about his
> experiences, it would be much more helpful for everyone if these people
> would try to help to improve the official documentation, so anyone can
> see it.

Since that you've moved the source to github, why not deprecate the old
site, and start using

github / https://docs.readthedocs.io/en/stable/

for documentation where people better can contribute, and easier to update.


My own motivation on contributing or rather lack hereof, is a private
matter, and not for this list.


/Tomse

[Spiro Trikaliotis]

Hello Nate,

* On Thu, Oct 29, 2020 at 03:08:38PM -0700 Nate Lawson wrote:

> > On Oct 29, 2020, at 2:29 PM, Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net> wrote:
> >
> > However, it is not easy to flash it. At the moment, xum1541cfg is not
> > able to flash it! The PROMICRO uses 32U4, while the ZF uses 32U2 µC. So,
> > xum1541cfg does not recognise the PROMICRO once it is in bootloader
> > mode.
>
> I could update xum1541cfg for this. I think there’s a way to tell the device model for the firmware image.

Yes, this should be possible. I did not have time to look at this myself
yet.

> > Additionally, the v07 firmware did not support going into bootloader
> > mode at all! This has been fixed with v08, but this does not help anyone
> > with a v07 firmware.
>
> You mean this was buggy for the ProMicro only or also ZoomFloppy?

It was only buggy for the ProMicro. More precisely, it was intentionally
left out because xum1541cfg did not work with the PROMICRO.

The ZF works flawlessly in this respect, at least for me.