3.0.15_b7

when I toggle zadig to 'Advanced mode', here's the log of driver installation.
do you have something similar?
Using inf name: DMX_USB_PRO.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created 'C:\usb_driver\DMX_USB_PRO.inf'
libwdi:info [wdi_prepare_driver] Vista or later detected - creating and self-signing a .cat file...
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\dmx_usb_pro.inf'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\usb_driver\DMX_USB_PRO.cat'
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)' from 'Root' store
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)' from 'TrustedPublisher' store
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\usb_driver\DMX_USB_PRO.cat'
libwdi:info [SelfSignFile] successfully deleted private key
Driver Installation: SUCCESS


maybe it worth trying to remove C:\usb_driver and reinstall WINUSB driver...
just a thought...

++

Here's mine


ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
libwdi:info [detect_version] Windows Vista
9 devices found.
Using 'C:\usb_driver' as extraction directory.
Using inf name: USB_Serial_Converter.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created 'C:\usb_driver\USB_Serial_Converter.inf'
libwdi:info [wdi_prepare_driver] Vista or later detected - creating and self-signing a .cat file...
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\usb_serial_converter.inf'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\usb_driver\USB_Serial_Converter.cat'
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)' from 'Root' store
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)' from 'TrustedPublisher' store
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_0403&PID_6001 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\usb_driver\USB_Serial_Converter.cat'
libwdi:info [SelfSignFile] successfully deleted private key
Driver Installation: SUCCESS
9 devices found.


And I tried your suggestion (renamed C:\usb_driver to 'old_usb_driver and reinstalled, but still no luck...

Colin

And can y ou try tout set the lisbusb debug level to 4 And start DL from the command line (via cmd.exe)
Thanx.
++

ola, good morning. Rapport a touchosc qui bugue qd l'osc writer est en marche,suis-je le seul avec ce bug?

TouchOSC worked fine (in both directions) with b7, when I demonstrated it to a friend on a PC.
(Have not verified it on OS X yet)

Best regards,
Noël

@Colin,
I've tried in the win box to set LIBUSB_DEBUG=4 and to run DL but the log are not displayed...
I've tried to remove all usb related things from the win box, but I didn't succeed to do what I want _ ultraDMX micro is always connecting....
frankly, I don't know what to do next as I do want to update the libusbx but I don't want to let you behind...

do you have the possibility to try on another win box?

++

Hi Nico,

Same here with DEBUG=4 and running DLight from the cmd line - no log produced.

I have an old laptop also running Vista - I'll try and get it set up and running the b7 version. Will report as soon as possible

Regards

Colin

Hi Nico,

It's my laptop!!!!

I fired up my old machine (Win Vista, as the 'newer' one) and making sure I had installed 3.0.15_b7, loaded a test file, and Bingo, it connected to the DMXMicro USB straight away...

So, my problem, not yours. Obviously something to do with what's running on the 'bad' driver install - but really odd,since it still connects to the b3 libusb-1.0.dll.

:huh:

Colin

@Colin,
sadly this is a good news
and I can't explain why it uses libusbK driver instead of WINUSB... moreover why the b3 libusb.dll works as the newer on do not...
don't you (or a friend) have an enttec usbPro widget to see if behavior is the same?
did ultraDMX is called the same on both of your computers? I mean here, it's called DMX_USB_PRO while yours is called USB_Serial_Converter...

so I'll publish another beta tomorrow as a last check.

++

b8 online.
last shot...

++

@Colin,
here's the answer form the libusbx mailing list:

> according to the first line of the user's log, libusbx try to use libusbK
> drivers instead of WINUSB ones:
>
> [ 0.000000] [00001450] libusbx: debug [libusb_init] created default context
> [ 0.000000] [00001450] libusbx: debug [libusb_init] libusbx v1.0.14.10576
> [ 0.000000] [00001450] libusbx: debug [init_polling] Will use CancelIoEx for
> I/O cancellation
> [ 0.036000] [00001450] libusbx: debug [winusbx_init] using libusbK DLL for
> universal access
>
> is there's a simple way to remove libusbK driver?

No libusbx will use libusbK.dll by default if it is present. If it is
not present, libusbx will then fall back to WinUSB only mode
where libusb0.sys/libusbk.sys will not be supported.

You can ask your friend to upgrade libusbK to its latest version.
If your friend wants to uninstall libusbK, then he should be able
to use the uninstaller provided (Start Menu -->UsbK Development Kit
-->Uninstall UsbK Development Kit). To make sure libusbK.dll is gone,
you can go to Windows\System32 and Windows\SysWow64 directory
to check the presence of libusbK.dll. Take note Windows\SysWow64
directory will only be present for 64bit Windows.

@Nico

2 Questions...

1) I have found the libusbK.dll in ..\Windows\System32 - but as the Start Menu does *not* have an uninstaller (because presumably it was installed by Zadig?), can I just remove/rename the libusbK.dll from ..\System32 - is it safe to do so?

and

2) There is *also* a copy of libusb-1.0.dll in ..\System32. This has a much older file version number - 1.0.8.8331. a) should it be there? b) should I replace it with the newest version (or even the one that works from DL3..15_b3)?

Regards

Colin

Hi Colin,

1) I have found the libusbK.dll in ..\Windows\System32 - but as the Start Menu does *not* have an uninstaller (because presumably it was installed by Zadig?), can I just remove/rename the libusbK.dll from ..\System32 - is it safe to do so?

yeah it's safe to remove it.
we can suppose that it's only zadig that have installed it

2) There is *also* a copy of libusb-1.0.dll in ..\System32. This has a much older file version number - 1.0.8.8331. a) should it be there? b) should I replace it with the newest version (or even the one that works from DL3..15_b3)?

remove it also.
DL use the one that is in the bin directory of DL.

zadig do not install libusb.dll, it only install drivers and preferably WINUSB one.

++

Hey Nico...

Bingo!!!

Removing the libusbK.dll from Windows\System32 allows the newest libusb-1.0.dll to be used and DLight 3.0.15_b8 connects to the DMX Micro ...

Will keep checking though...

Regards

Colin

I like your bingos
so we can close this unwanted chapter.
please keep on testing the b8 as it can be identical to the release.

violently happy

++