Zadig Terminates when it tries to list all the devices

laoproject commented 10 years ago

Dear all!

I am trying to use zadig_v2.0.1.162 on Windows 7. I launch and it finds 0 devices.... Then when I press on list all devices zadig terminates. I have crossed similar problem over internet without finding a solution.... any idea?

Thanks

pbatard commented 10 years ago

Download, extract and run DebugView, which you can obtain from here.
Download a custom test version of Zadig from here and run it.
Go to Options → Log Verbosity and set it to Debug.
Go to Options → List All Devices. Zadig should crash.
Go back to DebugbView, save the log and send it to me/copy it here.
Download xusb.exe from here and save it to a directory.
Open a command prompt and navigate to this directory.
Run the command xusb -d 2>xusb.log
Send me the xusb.log or copy it here.

laoproject commented 10 years ago

Hi Pete, thanks for your help!

the debug log:

00000001    0.00000000  [1924] Initialize   
00000002    0.00011243  [1924] QueryContextMenu 
00000003    14.64671898 [3680] Zadig v2.1.0.163     
00000004    14.64764977 [3680] Windows 7 SP1 64-bit     
00000005    14.64797688 [3680] ini file 'zadig.ini' not found - default parameters will be used     
00000006    14.64820862 [3680] default driver set to 'WinUSB'   
00000007    14.66945648 [3680] 0 devices found.

the xusb log:

[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.021001] [00001cc4] libusb: debug [libusb_get_device_list] 
[ 0.025001] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [1B5]
[ 0.026001] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [3F7]
[ 0.026001] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [202]
[ 0.026001] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [220]
[ 0.032002] [00001cc4] libusb: debug [get_api_type] driver(s): iusb3hub
[ 0.032002] [00001cc4] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.032002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [1CD]
[ 0.033002] [00001cc4] libusb: debug [get_api_type] driver(s): usbhub
[ 0.033002] [00001cc4] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.033002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [35]
[ 0.033002] [00001cc4] libusb: debug [get_api_type] driver(s): usbhub
[ 0.033002] [00001cc4] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.033002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [83]
[ 0.033002] [00001cc4] libusb: debug [get_api_type] driver(s): usb3Hub
[ 0.033002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [B9]
[ 0.034002] [00001cc4] libusb: debug [get_api_type] driver(s): usbhub
[ 0.034002] [00001cc4] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.034002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [2F7]
[ 0.034002] [00001cc4] libusb: debug [get_api_type] driver(s): usbhub
[ 0.035002] [00001cc4] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.035002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [88]
[ 0.037002] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [35] (0.0)
[ 0.037002] [00001cc4] libusb: debug [init_device] (bus: 1, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#4&14A2D17D&0'
[ 0.037002] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [83] (0.0)
[ 0.037002] [00001cc4] libusb: debug [init_device] (bus: 2, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#4&19AF4EC3&0'
[ 0.037002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [2E9]
[ 0.037002] [00001cc4] libusb: debug [init_device] got bus number from ancestor #2
[ 0.037002] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.037002] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 59 bytes)
[ 0.037002] [00001cc4] libusb: debug [init_device] (bus: 3, addr: 2, depth: 1, port: 3): '\\.\USB#VID_046D&PID_C52F#5&ED8661&0&3'
[ 0.038002] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [24E]
[ 0.038002] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.038002] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 34 bytes)
[ 0.038002] [00001cc4] libusb: debug [init_device] (bus: 3, addr: 3, depth: 1, port: 2): '\\.\USB#VID_0BDA&PID_2838#00000001'
[ 0.213012] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [155]
[ 0.213012] [00001cc4] libusb: debug [init_device] got bus number from ancestor #2
[ 0.213012] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.632036] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 661 bytes)
[ 0.632036] [00001cc4] libusb: debug [init_device] (bus: 2, addr: 5, depth: 1, port: 5): '\\.\USB#VID_0C45&PID_644F#6&249BCA29&0&5'
[ 0.634036] [00001cc4] libusb: debug [windows_get_device_list] extra GUID: {3DAD1A1C-7D52-4891-8CA3-EE9AA3902090}
[ 0.635036] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [2EE]
[ 0.635036] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.636036] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 46 bytes)
[ 0.636036] [00001cc4] libusb: debug [init_device] (bus: 2, addr: 3, depth: 1, port: 1): '\\.\USB#VID_138A&PID_0011#41E5D4AC789E'
[ 0.637036] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [B9] (0.0)
[ 0.637036] [00001cc4] libusb: warning [force_hcd_device_descriptor] could not infer VID/PID of HCD hub from '\\.\ROOT#UOIP_BUS_DRIVER#0000#{3ABF6F2D-71C4-462A-8A92-1E6861E6AF27}'
[ 0.637036] [00001cc4] libusb: debug [init_device] (bus: 4, addr: 1, depth: 0, port: 0): '\\.\USB#VID_8086&PID_1111#1&30D1A4CF&0&0001'
[ 0.638036] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [2F7] (2.0)
[ 0.638036] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.638036] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.638036] [00001cc4] libusb: debug [init_device] (bus: 2, addr: 2, depth: 1, port: 1): '\\.\USB#VID_8087&PID_0024#5&3401B8B2&0&1'
[ 0.639037] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [88] (0.0)
[ 0.784045] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.784045] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.784045] [00001cc4] libusb: debug [init_device] (bus: 1, addr: 2, depth: 1, port: 1): '\\.\USB#VID_8087&PID_0024#5&823B890&0&1'
[ 0.784045] [00001cc4] libusb: debug [discovered_devs_append] need to increase capacity
[ 0.786045] [00001cc4] libusb: debug [windows_get_device_list] allocating new device for session [14A]
[ 0.786045] [00001cc4] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.788045] [00001cc4] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 177 bytes)
[ 0.788045] [00001cc4] libusb: debug [init_device] (bus: 1, addr: 3, depth: 2, port: 5): '\\.\USB#VID_8087&PID_07DA#6&1355776&0&5'
[ 0.790045] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [1CD] (3.0)
[ 0.790045] [00001cc4] libusb: debug [init_device] (bus: 3, addr: 1, depth: 0, port: 0): '\\.\IUSB3#ROOT_HUB30#4&3302C911&0'
[ 0.796045] [00001cc4] libusb: debug [get_api_type] driver(s): usbccgp
[ 0.796045] [00001cc4] libusb: debug [get_api_type] matched driver name against Composite API API
[ 0.796045] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [2E9] (3.2)
[ 0.796045] [00001cc4] libusb: debug [get_api_type] driver(s): usbccgp
[ 0.797046] [00001cc4] libusb: debug [get_api_type] matched driver name against Composite API API
[ 0.797046] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [24E] (3.3)
[ 0.797046] [00001cc4] libusb: debug [get_api_type] driver(s): usbccgp
[ 0.797046] [00001cc4] libusb: debug [get_api_type] matched driver name against Composite API API
[ 0.797046] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [155] (2.5)
[ 0.798046] [00001cc4] libusb: debug [get_api_type] driver(s): WinUSB
[ 0.798046] [00001cc4] libusb: debug [get_api_type] matched driver name against WinUSB API
[ 0.798046] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [2EE] (2.3)
[ 0.798046] [00001cc4] libusb: debug [get_api_type] driver(s): BTHUSB
[ 0.799046] [00001cc4] libusb: debug [get_api_type] lower filter driver(s): iBtFltCoex;btmhsf
[ 0.799046] [00001cc4] libusb: debug [windows_get_device_list] found existing device for session [14A] (1.3)
[ 0.803046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [2E9]:
[ 0.803046] [00001cc4] libusb: debug [set_composite_interface] interface[0] = \\.\HID#VID_046D&PID_C52F&MI_00#7&1C346353&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.803046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [2E9]:
[ 0.803046] [00001cc4] libusb: debug [set_composite_interface] interface[1] = \\.\HID#VID_046D&PID_C52F&MI_01&COL01#7&7A2DA6F&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.804046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [2E9]:
[ 0.804046] [00001cc4] libusb: debug [set_composite_interface] interface[1] already set - ignoring HID collection: \\.\HID#VID_046D&PID_C52F&MI_01&COL02#7&7A2DA6F&0&0001
[ 0.804046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [2E9]:
[ 0.804046] [00001cc4] libusb: debug [set_composite_interface] interface[1] already set - ignoring HID collection: \\.\HID#VID_046D&PID_C52F&MI_01&COL03#7&7A2DA6F&0&0002
[ 0.804046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [24E]:
[ 0.804046] [00001cc4] libusb: warning [set_composite_interface] failure to read interface number for \\.\HID#VID_0BDA&PID_2838&COL01#7&72DE59E&0&0000. Using default value 0
[ 0.804046] [00001cc4] libusb: debug [set_composite_interface] interface[0] = \\.\HID#VID_0BDA&PID_2838&COL01#7&72DE59E&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.805046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [24E]:
[ 0.805046] [00001cc4] libusb: warning [set_composite_interface] failure to read interface number for \\.\HID#VID_0BDA&PID_2838&COL02#7&72DE59E&0&0001. Using default value 0
[ 0.805046] [00001cc4] libusb: debug [set_composite_interface] interface[0] already set - ignoring HID collection: \\.\HID#VID_0BDA&PID_2838&COL02#7&72DE59E&0&0001
[ 0.805046] [00001cc4] libusb: debug [windows_get_device_list] setting composite interface for [24E]:
[ 0.805046] [00001cc4] libusb: warning [set_composite_interface] failure to read interface number for \\.\HID#VID_0BDA&PID_2838&COL03#7&72DE59E&0&0002. Using default value 0
[ 0.805046] [00001cc4] libusb: debug [set_composite_interface] interface[0] already set - ignoring HID collection: \\.\HID#VID_0BDA&PID_2838&COL03#7&72DE59E&0&0002
[ 0.807046] [00001cc4] libusb: debug [get_api_type] driver(s): WinUSB
[ 0.807046] [00001cc4] libusb: debug [get_api_type] matched driver name against WinUSB API
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_get_device_descriptor] 
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 3.2
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 3.3
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 2.5
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 2.3
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 4.1
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 4.0
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 2.2
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 2.1
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 2.0
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 1.3
[ 0.807046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 1.2
[ 0.808046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 1.1
[ 0.808046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 1.0
[ 0.808046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 3.1
[ 0.808046] [00001cc4] libusb: debug [libusb_unref_device] destroy device 3.0
  Failed.
[ 0.808046] [00001cc4] libusb: debug [libusb_exit] 
[ 0.808046] [00001cc4] libusb: debug [libusb_exit] destroying default context

I hope that is what you needed! thanks again! Vincent

pbatard commented 10 years ago

Thanks, but did you perform steps 3 & 4, as I indicated, before copy/pasting the log from DebugView? If not, please make sure you have Debug verbosity enabled and then try to list all devices, as unless you have made Zadig crash, the first log will be meaningless...

laoproject commented 10 years ago

When I perform the steps 3&4 as described I have no log to appear.... It is only when I capture Win32 that I get the log showed above... I precise that all .exe Have been lauch with admin rights.

pbatard commented 10 years ago

So when you perform 3&4, Zadig crashes without any extra information appearing in DebugView, is that right? If not, please make sure your provide the DebugView log after Zadig crashes. The crash will not prevent Zadig from sending messages to DebugView until it exists, and if there are any messages that occur before the crash, I really want to see them (which is why I asked to use DebugView, as it will keep all messages sent by Zadig).

In other words, did you make Zadig crash before you copied the first log?

dronespeak commented 10 years ago

I have the same situation as being experienced by laoproject. I am using a Samsung Ultrabook running Win7. Any suggestions? Thanks, JohnG

laoproject commented 10 years ago

yes I make Zadig Crash before copying the log.... surprising isn't it?

laoproject commented 10 years ago

I try and i try, but alwsays the same reaction, however debugview doesn't seem stable (it doesn't work and same way at each try...). and I have this message appearing some time: 00000001 0.00000000 [1508] P2PE - m_eITSettingsLoc eProsetIT

dronespeak commented 10 years ago

In my case: Using Device Manager I can see that the 'REAL TEK R2832 U Device' is being recognized when I plug in an R820T SDR device from NooElec. I also see the stock Real Tek High Definition Audio device that was supplied with my laptop. Maybe there is a conflict, or some "safeguard" was installed to make it difficult to use zadig.

dronespeak commented 10 years ago

Pete, A copy of all messages was too long to post, however below, in sequence, are the messages that may be relevant:

00000007    1.20025039  [4468] [ DEBUG ][ 01/30/2014 08:05:46 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000008    1.37423277  [4468] [ DEBUG ][ 01/30/2014 08:05:47 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
00000009    1.45164061  [6404] V: 1/30/2014 8:05:47 AM (tid <no name>, 18) - SeagateHipServAgentAdapter::GetBeaconRawBroadcast()    
00000010    1.45304847  [6404] V: 1/30/2014 8:05:47 AM (tid GetMessageResponse, 20) - BaseHelperAgent::SendMessage(string) - Message=******     
00000011    1.50028837  [4468] [ DEBUG ][ 01/30/2014 08:05:47 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000012    1.80533648  [4468] [ DEBUG ][ 01/30/2014 08:05:47 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000013    1.97428298  [4468] [ DEBUG ][ 01/30/2014 08:05:47 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
00000014    2.10526919  [4468] [ DEBUG ][ 01/30/2014 08:05:47 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000015    2.15891576  [6404] V: 1/30/2014 8:05:47 AM (tid GetMessageResponse, 20) - BaseHelperAgent::ReceiveMessage() message: empty  
00000016    2.15928006  [6404] I: 1/30/2014 8:05:47 AM (tid <no name>, 18) - Null, empty answer or unknown request. Igonoring.  
00000017    2.40520906  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000018    2.57430553  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
00000019    2.62151003  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4636 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: Destructor running, aborting any underlying thread with a deadlock timeout value = 5000 (milliseconds). ]  
00000020    2.62394047  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4636 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 5000 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4636. ]   
00000021    2.73934746  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: Destructor running, aborting any underlying thread with a deadlock timeout value = 5000 (milliseconds). ]  
00000022    2.77389646  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: Destructor running, aborting any underlying thread with a deadlock timeout value = 5000 (milliseconds). ]  
00000023    3.17430496  [4468] [ DEBUG ][ 01/30/2014 08:05:48 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
00000024    3.77440071  [4468] [ DEBUG ][ 01/30/2014 08:05:49 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
---------
00000115    20.63581085 [4468] [ DEBUG ][ 01/30/2014 08:06:06 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000116    20.73748207 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Start calling 
00000117    20.73765564 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Request Mutex Ownership   
00000118    20.73774529 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Call Sabi Function    
00000119    20.73816872 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Succeeded to call (1stByte=DD)    
00000120    20.73831749 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Start calling 
00000121    20.73843002 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Request Mutex Ownership   
00000122    20.73851395 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Call Sabi Function    
00000123    20.74182701 [5312] [SABIv3.2.0.0] Ps:SmartSetting.exe              , <CALL  > MFn:5843h, SFn:77h, Succeeded to call (1stByte=0A)    
00000124    20.93811226 [4468] [ DEBUG ][ 01/30/2014 08:06:06 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000125    21.17786026 [4468] [ DEBUG ][ 01/30/2014 08:06:06 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
-------
00000386    68.65213013 [4468] [ DEBUG ][ 01/30/2014 08:06:54 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000387    68.95211792 [4468] [ DEBUG ][ 01/30/2014 08:06:54 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000388    70.43000031 [7380] In WM_DEVICECHANGE   
00000389    70.43204498 [7380] SetTimer for WM_DEVICECHANGE Started 
00000390    70.54315948 [7380] In WM_DEVICECHANGE   
00000391    70.55563354 [7380] WM_DISPLAYCHANGE KillTimer(10522, 0).    
00000392    70.55679321 [4468] [ DEBUG ][ 01/30/2014 08:06:56 ] [ PID: 4468 ] [ TID: 4640 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 200 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4640. ]    
00000393    70.56865692 [7380] SetTimer for WM_DEVICECHANGE Started 
00000394    70.61137390 [4468] [ DEBUG ][ 01/30/2014 08:06:56 ] [ PID: 4468 ] [ TID: 4648 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: McciMT::Thread putting the underlying thread to sleep for 500 milliseconds. Thread HANDLE = 4294967294. Thread Id = 4648. ]    
00000395    70.68402863 [4468] [ DEBUG ][ 01/30/2014 08:06:56 ] [ PID: 4468 ] [ TID: 4636 ] [ McciMT-Log ] [ McciMT::Thread ] [ Msg: Destructor running, aborting any underlying thread with a deadlock timeout value = 5000 (milliseconds). ]

pbatard commented 10 years ago

@dronespeak, do you see a crash too? I know there is a different issue with RT R2832 devices not being recognized, but that one doesn't cause a crash. This issue is only about Zadig crashing when trying to list all devices. Also, please bear in mind that DebugView is global logging facilities, so A LOT of applications, besides Zadig, do write there. A a matter of fact, in the log above, I actually don't see any message that seems to have originated from Zadig, so it doesn't tekk me much.

Right now, my best guess as to why hat may cause the crash is that there is an usb3Hub driver, for an USB 3.0 hub, which is not currently handling by Zadig when enumerating the bus. But the expectation is that it should just prevent devices on that hub to be listed, not crash the app.

To confirm if usb3Hub is the issue, I would very much like if anyone who has this issue ran the xusb test (steps 6→9).

Or, if you really want to help troubleshooting this issue on a machine where Zadig crashes, and you have access to Visual Studio 2012 or later there, is to try to recompile Zadig from source (from this github project) and then run it in debug mode from Visual Studio. Then it would tell you exactly what caused the crash...

dronespeak commented 10 years ago

Yes, I see a crash too. I am unable to list devices. When I try, zadig "stops working". I have followed your instructions through Step 6. I know how to open a command prompt, but I will need to study... to learn the steps to "navigate to the directory" before I "Run the command xusb -d 2>xusb.log".

dronespeak commented 10 years ago

Sorry, I do not have access to Visual Studio.

dronespeak commented 10 years ago

Pete, Below is a copy of the xusb.log file contents. I see that Microsoft offers a free trial version of Visual Studio, however that might be a steep learning curve for me. Let me know if you need me to make that effort. Thanks for your help. I am excited about exploring SDR, but it appears there is one step that is not workable yet on my laptop.

John

[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.012000] [000023fc] libusb: debug [libusb_get_device_list] 
[ 0.014001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [1CB]
[ 0.014001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [D6]
[ 0.014001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [318]
[ 0.014001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [220]
[ 0.016001] [000023fc] libusb: debug [get_api_type] driver(s): rusb3hub
[ 0.016001] [000023fc] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.016001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [3A1]
[ 0.017001] [000023fc] libusb: debug [get_api_type] driver(s): usbhub
[ 0.017001] [000023fc] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.017001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [3B3]
[ 0.017001] [000023fc] libusb: debug [get_api_type] driver(s): usbhub
[ 0.017001] [000023fc] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.017001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [AF]
[ 0.017001] [000023fc] libusb: debug [get_api_type] driver(s): usb3Hub
[ 0.017001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [B9]
[ 0.017001] [000023fc] libusb: debug [get_api_type] driver(s): usbhub
[ 0.018001] [000023fc] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.018001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [FA]
[ 0.018001] [000023fc] libusb: debug [get_api_type] driver(s): usbhub
[ 0.018001] [000023fc] libusb: debug [get_api_type] matched driver name against HUB API API
[ 0.018001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [6B]
[ 0.020001] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [3B3] (0.0)
[ 0.020001] [000023fc] libusb: debug [init_device] (bus: 2, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#4&44665BF&0'
[ 0.021001] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [AF] (0.0)
[ 0.021001] [000023fc] libusb: debug [init_device] (bus: 3, addr: 1, depth: 0, port: 0): '\\.\USB#ROOT_HUB20#4&841F4DF&0'
[ 0.021001] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [2B6]
[ 0.021001] [000023fc] libusb: debug [init_device] got bus number from ancestor #2
[ 0.021001] [000023fc] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.022001] [000023fc] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 59 bytes)
[ 0.022001] [000023fc] libusb: debug [init_device] (bus: 2, addr: 2, depth: 1, port: 2): '\\.\USB#VID_046D&PID_C526#6&265BE15E&0&2'
[ 0.192011] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [248]
[ 0.193011] [000023fc] libusb: debug [init_device] got bus number from ancestor #2
[ 0.193011] [000023fc] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.438025] [000023fc] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 1118 bytes)
[ 0.438025] [000023fc] libusb: debug [init_device] (bus: 3, addr: 4, depth: 1, port: 4): '\\.\USB#VID_2232&PID_1024#SN0001'
[ 0.441025] [000023fc] libusb: debug [windows_get_device_list] allocating new device for session [1FB]
[ 0.441025] [000023fc] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.442025] [000023fc] libusb: info [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_8086&PID_0189#6&265BE15E&0&5': [31] A device attached to the system is not functioning.
[ 0.442025] [000023fc] libusb: debug [init_device] (bus: 2, addr: 3, depth: 1, port: 5): '\\.\USB#VID_8086&PID_0189#6&265BE15E&0&5'
[ 0.444025] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [B9] (0.0)
[ 0.444025] [000023fc] libusb: warning [force_hcd_device_descriptor] could not infer VID/PID of HCD hub from '\\.\ROOT#UOIP_BUS_DRIVER#0000#{3ABF6F2D-71C4-462A-8A92-1E6861E6AF27}'
[ 0.444025] [000023fc] libusb: debug [init_device] (bus: 4, addr: 1, depth: 0, port: 0): '\\.\USB#VID_8086&PID_1111#1&30D1A4CF&0&0001'
[ 0.445025] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [FA] (3.0)
[ 0.445025] [000023fc] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.445025] [000023fc] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.445025] [000023fc] libusb: debug [init_device] (bus: 3, addr: 3, depth: 1, port: 1): '\\.\USB#VID_8087&PID_0024#5&10E2FC65&0&1'
[ 0.446025] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [6B] (2.0)
[ 0.447025] [000023fc] libusb: debug [init_device] found 1 configurations (active conf: 1)
[ 0.447025] [000023fc] libusb: debug [cache_config_descriptors] cached config descriptor 0 (bConfigurationValue=1, 25 bytes)
[ 0.447025] [000023fc] libusb: debug [init_device] (bus: 2, addr: 4, depth: 1, port: 1): '\\.\USB#VID_8087&PID_0024#5&7B8F2B&0&1'
[ 0.452026] [000023fc] libusb: debug [get_api_type] driver(s): usbccgp
[ 0.452026] [000023fc] libusb: debug [get_api_type] matched driver name against Composite API API
[ 0.452026] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [2B6] (2.2)
[ 0.453026] [000023fc] libusb: debug [get_api_type] driver(s): usbccgp
[ 0.453026] [000023fc] libusb: debug [get_api_type] matched driver name against Composite API API
[ 0.453026] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [248] (3.4)
[ 0.454026] [000023fc] libusb: debug [get_api_type] driver(s): BTHUSB
[ 0.454026] [000023fc] libusb: debug [get_api_type] lower filter driver(s): iBtFltCoex;btmhsf
[ 0.454026] [000023fc] libusb: debug [windows_get_device_list] found existing device for session [1FB] (2.3)
[ 0.457026] [000023fc] libusb: debug [windows_get_device_list] setting composite interface for [2B6]:
[ 0.457026] [000023fc] libusb: debug [set_composite_interface] interface[0] = \\.\HID#VID_046D&PID_C526&MI_00#8&901C111&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.458026] [000023fc] libusb: debug [windows_get_device_list] setting composite interface for [2B6]:
[ 0.458026] [000023fc] libusb: debug [set_composite_interface] interface[1] = \\.\HID#VID_046D&PID_C526&MI_01&COL01#8&1AD57CB1&0&0000#{4D1E55B2-F16F-11CF-88CB-001111000030}
[ 0.458026] [000023fc] libusb: debug [windows_get_device_list] setting composite interface for [2B6]:
[ 0.458026] [000023fc] libusb: debug [set_composite_interface] interface[1] already set - ignoring HID collection: \\.\HID#VID_046D&PID_C526&MI_01&COL02#8&1AD57CB1&0&0001
[ 0.458026] [000023fc] libusb: debug [windows_get_device_list] setting composite interface for [2B6]:
[ 0.458026] [000023fc] libusb: debug [set_composite_interface] interface[1] already set - ignoring HID collection: \\.\HID#VID_046D&PID_C526&MI_01&COL03#8&1AD57CB1&0&0002
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 1.0
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 0.0
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_get_device_descriptor] 
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 2.2
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 3.4
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 2.3
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 4.1
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 4.0
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 3.3
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 3.1
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 3.0
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 2.4
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 2.1
[ 0.459026] [000023fc] libusb: debug [libusb_unref_device] destroy device 2.0
  Failed.
[ 0.460026] [000023fc] libusb: debug [libusb_exit] 
[ 0.460026] [000023fc] libusb: debug [libusb_exit] destroying default context

pbatard commented 10 years ago

Let me know if you need me to make that effort.

Nah, that's fine John. It was only a suggestion in case you were familiar with it.

I do see that usb3Hub in your xusb log too, so this raises the probability that this is what is causing the crash.

I'll try to produce a new test version of Zadig that has support for usb3Hub when I get a chance (which might not be before another couple of days). I sure hope that, with both your help, we'll be able to fix that bug.

dronespeak commented 10 years ago

Thanks Pete. After no complete success - on two machines (Win7 and XP) with the dongle from NooElec, I am getting the impression that I have a defective device, or something has happened with the SDR game such that the downloaded SDRSharp app is effectively non-functioning. I can open SDRSharp and see some dynamic display, however - on both machines - I am unable to increase the VFO setting by more than "24.000". All of the screeshots in instructions I have found online do not match what the display I am seeing. There is no field for direct entry of a desired frequency, other than the digit fields to the right of "VFO" at the top. Near the bottom is a section titled "Frequency Manager (Plugin)", which makes me wonder if I need to find such a plugin (and I have yet to find any such plugins). The NooElec website offers the SDR installer, which I also found on rtlsdr.org/software/windows. I must be missing some step (and I have tried many), or maybe I simply have a defective dongle. More likely to be a cockpit error. Getting close to giving up on SDR.

dronespeak commented 10 years ago

Pete, for what it may be worth, before crashing zadig, I see the following comments in Advanced Mode under Options: Windows 7 SP1 64-bit ini file 'zadig.ini' not found - default parameters will be used default driver set to 'WinUSB' 0 devices found.

laoproject commented 10 years ago

hehehe! i am also using zadig for a SDR application (for high altitude balloon see: http://ukhas.org.uk/guides:sdr_tracker )! Concerning our case, I am currently getting visual studio as soon as I have some results I will post them here!

dronespeak commented 10 years ago

@laoproject: A bit off topic for this thread, but recently I discovered other links with a few bits of info that may be useful for your project: a) User comments on Amazon.com for "NooElec TV28T v2 USB DVB-T & RTL-SDR Receiver, RTL2832U & R820T Tuner" b) http://www.rtl-sdr.com/category/rtl-sdr/ c) http://www.sdrsharpplugins.com/ d) http://www.hamradioscience.com/category/sdr-radio/ e) http://goughlui.com/?p=3841 and other SDR-related posts f) http://sonicgoose.com/using-a-rtlsdr-dongle-for-ads-b/

pbatard commented 10 years ago

OK, here's the news:

I have uploaded a new test version of Zadig with Usb3hub support. Please download it from here and report.
Since a bunch of people seem to be using Zadig with SDR devices, and I don't have one, I ordered the cheapest RTL2832U & R820T Tuner I could find. It will take at least one month before I receive it, so don't expect much help on the SDR/RTL side before that
Right now, my guess about the SDR/RTL drive installation issue is that Windows Update has a default driver for such devices with a higher precedence than the one that Zadig installed. In the Windows world, driver packages are assigned a score, and the ones that go through WHQL (such as the one that a manufacturer such as Realtek may put in Windows Update for their RTL2832U & R820T, so that it gets detected automatically) have a greater score than the ones that aren't WHQL signed, such as the one installed by Zadig (and there isn't much I can do in Zadig about that). Thus, if Windows has to decide between a driver package that comes from WHQL and one that comes from a local application, it may ignore the local one and only allow the WHQL one. This would explain all the RTL2832U & R820T installation woes users are having, and why doing seemingly weird things like setting the date back can help, as this could prevent WHQL driver packages from being recognized as valid. If you run the driver installation from Zadig in debug mode however, and provided it doesn't crash, the log should contain some signs that this is happening. I guess I'll find out more when I eventually get my SDR device.

dronespeak commented 10 years ago

My report: 1) I plugged in the RTL2832U dongle, and looked to find the device was listed in Windows' Device Manager. 2) I downloaded and opened the new test version of zadig, and was able to list devices without crashing zadig. After selecting 'Bulk-In, Interface (Interface 0)', I saw the following in the 'Driver' field: RTL2832UUSB (v64.1.802.2010). The Target Driver field was filled with 'WinUSB (v6.1.7600.16385)'. 3) I clicked the Replace Driver button and after a few minutes the following was displayed: Driver installation was successful. However during that brief installation period, I also saw Norton Auto-Protect kick in. A few moments later Norton stated that it had "removed the driver". Well maybe. 4) Without changing Norton settings... I repeated step 2, and noticed that the RTL2832U was no longer listed in the zadig window. It appeared that I needed to unplug and replug the dongle into the USB port, although this may not have been necessary. Anyway, when I looked in Device Manager, I did not see the RTL2832U listed (as before, under 'Sound, video and game controllers'), and it was not listed anywhere else in Device Manager. However I did see 'Bulk-In, Interface (Interface 0)' under 'Universal Serial Bus drivers'. 5) I followed the steps under 'Automated Installer' on http://rtlsdr.org/softwarewindows. It takes some patience to wait for download script to complete after clicking on the install.bat file. When it is complete, the hope is that "...the WinUSB driver is installed (and) you are ready to run SDR# with the RTL-SDR/USB input device." 6) I opened SDR# by clicking on the SDRSharp application in the sdrsharp folder. Then, next to the Play button, I selected 'RTL-SDR / USB' from the drop-down list. 7) As far as I can tell, SDR# is now working with my RTL2832U dongle! Hooray! That said, I was unable to hear any FM stations, even with the AF gain up. Just static. I have read that the stock antenna is not great. And I live many miles from the nearest commercial FM transmission towers. So maybe it is not surprising that I have yet to discover a station. Or there is some other problem. But at this point it appears that the zadig crash problem has been solved, and that the driver installation was successful on my Win7 laptop.

Thanks Pete!

dronespeak commented 10 years ago

Ah ha! I just clicked the Configure button, then checked the 'RTL AGC' box, turned up the RF gain and wahoo! I am now hearing commercial FM stations!

pbatard commented 10 years ago

I downloaded and opened the new test version of zadig, and was able to list devices without crashing zadig

Aha! So this Usb3hub support was the cause of the crash. That's really good to know - thanks so much for spending time on this and helping with the testing. I really appreciate it!

A few moments later Norton stated that it had "removed the driver". Well maybe.

Are you sure of this? Most Antivirus applications have a log detailing things that they detected and took action with. Can you find the Norton log, and look at what it says around the time you tried the install? All of the driver files installed by Zadig are digitally signed, and Zadig itself is also digitally signed, so I don't see why Norton would have an issue with it. The one thing Zadig does, to make sure the installation succeeds, is generate a one-time certificate for the driver package and install it into the certificate store. Maybe that's what Norton complained about?

wahoo! I am now hearing commercial FM stations!

Glad it worked in the end! ;)

dronespeak commented 10 years ago

Pete, Here is a copy of the Norton security activity item:

Category: Resolved Security Risks
Date & Time,Risk,Activity,Status,Recommended Action,Path - Filename
1/31/2014 8:13:53 PM,High,installer_x86.exe (Suspicious.AD) detected by Auto-Protect,Quarantined,Resolved - No Action Required,c:\users\john githens\usb_driver\installer_x86.exe

Category: Quarantine
Date & Time,Risk,Activity,Status,Recommended Action,Path - Filename
1/31/2014 8:13:53 PM,High,installer_x86.exe (Suspicious.AD) detected by Auto-Protect,Quarantined,Resolved - No Action Required,c:\users\john githens\usb_driver\installer_x86.exe"

And here are the end-user directed comments:

- installer_x86.exe contained...   Suspicious.AD
- Risk: High
- Origin: Not Available
- Activity: Threat Actions performed: 1

Apparently, Norton saw the code as fitting a dangerous profile.

John

pbatard commented 10 years ago

Apparently, Norton saw the code as fitting a dangerous profile.

<Sigh> This has nothing to do with you, but it's really starting to get really annoying...

About half of the Open Source applications I put out there are being falsely detected as potentially malicious by one of these £$%^&*&^%$%^& "security" applications, and I'm spending way too much time submitting these apps, over and over again, to their false positive report program, only to receive an "Oops, our mistake!" from these vendors...

I guess I'll have to submit the installers from Zadig to Norton again. :(

But I have to say this loud and clear: If it prevents a legitimate Open Source applications such as Zadig from performing its job, Norton, and other vendors' security products are a joke.

pbatard commented 10 years ago

I have now released Zadig 2.1.0, which should officially fix the above issue. I will therefore close it.

laoproject commented 10 years ago

Hi pete!

very nice, it works perfectly on my machine! I have this dongle: http://dx.com/p/rtl2832u-r820t-mini-dvb-t-dab-fm-usb-digital-tv-dongle-black-170541#.UvC1nPl5MZ4 and I have succeeded to make it work thanks to you! Next step: transfert digital data through it! Regards Vincent

dronespeak commented 10 years ago

Pete, I really, really appreciate the time you invested in resolving this situation. Cheers! John Githens DroneSpeak LLC

----- Original Message ----- From: "pbatard/libwdi" To:"pbatard/libwdi" Cc:"dronespeak" Sent:Tue, 04 Feb 2014 01:42:58 -0800 Subject:Re: [libwdi] Zadig Terminates when it tries to list all the devices (#24)

Hi pete! 

very nice, it works perfectly on my machine!

I have this dongle: http://dx.com/p/rtl2832u-r820t-mini-dvb-t-dab-fm-usb-digital-tv-dongle-black-170541#.UvC1nPl5MZ4 [1] and I have succeeded to make it work thanks to you! Next step: transfert digital data through it! Regards Vincent

—

Reply to this email directly or view it on GitHub [2].

Links:

[1] http://dx.com/p/rtl2832u-r820t-mini-dvb-t-dab-fm-usb-digital-tv-dongle-black-170541#.UvC1nPl5MZ4 [2] https://github.com/pbatard/libwdi/issues/24#issuecomment-34043769

pbatard commented 10 years ago

Well, this was a bad problem with my application, so there's no way I could leave it alone, and you guys helped a lot more than you realize, by providing logs, running tests, and more importantly sticking around until we could figured it out.

There's no way I could have sorted the issue without your help, and thanks to you, plenty more people should be able to access their SDR hardware as intended, which is good news. :)

pbatard / libwdi

Zadig Terminates when it tries to list all the devices #24

Links: