DSO5102P

lemoutan

Did you resolve this? I have exact same problem on Windows 64 with apparently successful installation of USB driver, but named "Unknown Device" which suggests not so successful.

lemoutan

Windows 7, 64 bit
On USB (powered) plugin -
(DigitalScope.exe already installed, ready and waiting)
NOTE that the USB installation indicated a problem but the device manager window doesn't show it as a bad device (Yellow !), just an unknown one.
Here is USBDeview's report http://pix.iostuff.org/hantekDSO5012Pusbdev.html of the device - note especially the zero for USB\VID_0000&PID_0000\5&2e6c26e8&0&11        R (and pretty much everything else)

Here's what you get as soon as DigitalScope starts


Here's what you get when you acknowledge message:


Here's what you get as soon as you click on (almost) anything on the app


Here are the DSO5000P_Driver files I was supplied:

1. 41056 Mar  2 12:41 dstcoinstall.dll
   
2. 10103 Mar  2 12:40 dstusb.cat
   
3. 2616 Jan  4  2014 dstusb.inf
   
4. 18272 Mar  2 12:40 dstusbamd64.sys
   
5. 31584 Mar  2 12:40 dstusbia64.sys
   
6. 15456 Mar  2 12:40 dstusbx86.sys

Copy the Code

I can only assume they were installed with the DigitalScope.exe installation since I cannot install them manually (rightclick on .inf) without getting a:

lemoutan

I suppose I should also have told you that - as is quite commonly necessary with USB drivers originated from non-Microsoft ecosystems - I have already been through the 'update driver route' (several times). As the DSO5000P_Driver.zip you just posted contained exactly the same files as the ones already on my system, it was no great surprise to see (after - again - pointing the update driver dialog to the DSO5000P_Driver folder) :

This is hardly surprising since the (as pointed out in my last) USB driver id and vendor ID are both zero (hence the Unknown Device).

Do you actually know anybody running a 64bit Windows 7 system with a working DigitalScope.exe? I don't know how you would find out without either trying it yourself or being lucky enough for such people writing in and telling you

lemoutan

THanks for that. It's good to know that it will work in Win7-64, so one can be reasonably confident that there is a solution and that one is not wasting one's time trying.

Which particular architecture section of the inf file applied, in your case?

1. [DSTDSO.Files.Ext]
   
2. dstusbx86.SYS
   
3. [DSTDSO.Files.Ext.amd64]
   
4. dstusbamd64.SYS
   
5. [DSTDSO.Files.Ext.I64]
   
6. dstusbia64.SYS

Copy the Code

Obviously not the (default) x86 - so is your machine an amd64 or an I64?

As for your rather amusing suggestion that I replace my entire computer because one particular company's drivers are problematic, unless you have a machine for me which I can devote to the 'scope then I think I'll try other avenues first.

For instance I think there's some software knocking around that allows you to 'correct' the vendor/device from 0/0 to (as your inf file shows) 049F and 505A but that may only work for a specific device. Something to do with sigrok? Can't remember. There's also something about disabling windows 7 driver signing checks.

Anyone else can jump in here?

(Later that same reply ...)
I noticed that your picture2.jpg has the device driver in as a completely new windows device class (i.e. Measurement Device) which is completely different from mine which is just getting itself installed as an unspecific USB device within the existing windows device class of 'Universal Serial Bus Controllers'. As long as it keeps installing itself in that branch then I can't see how it's going to create the new Measurement Device class (with its own ClassGuid) - which is of course not already extant on my machine. Is it possible that the inability to create the correct class might be due to an existing, earlier, device of yours (i.e. the Hantek 6022BE - which I still have installed) which uses the same dstusb*.sys driver?

lemoutan

I've already tried all that. Full uninstall (custom - delete all files and registry entries) and reboot. There is now no trace of the 'DigitalScope' installation on this machine. Only the older Hantek6022BE software.
The ClassGuid for the device driver (5444534f-1100-2008-0218-080111008219 = DSO Measurement Device) as specified in a portion of the driver's inf file (reproduced below):

1. [Version]
   
2. Signature="$CHICAGO[        DISCUZ_CODE_0        ]quot;
   
3. Class=USB
   
4. ClassGuid = {5444534f-1100-2008-0218-080111008219}
   
5. provider=%ODM%
   
6. LayoutFile=layout.inf
   
7. CatalogFile=dstusb.cat

Copy the Code

is still, however, present in the registry (traces remain under ControlSet001 and ControlSet002 and - fatally - under CurrentControlSet) after reboot, as are also the

1. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_049F&PID_505A

Copy the Code

and

1. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\USB\VID_049F&PID_505A

Copy the Code

and

1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_049F&PID_505A

Copy the Code

entries.

These are simply not deletable by hand (e.g via regedit run as administrator) and - as far as I can tell - as long as those entries (for the vendor and device in question) remain then any time the live DSO5102P is plugged into this machine, the association of the equipment with a USB device (specifically the unknown one mentioned in earlier posts) rather than 'Measurement Device' will be made and the new device class creation (the aforementioned DSO Measurement Device) cannot and will not be performed. There seems to be no way out of this on this machine. It seems forever clobbered.

Of course it is possible to install on another (Windows 7 64bit) PC. That doesn't help with this machine - the one I need it on. Somehow these old unremovable registry entries from the (by now obviously mis-installed) earlier attempts are preventing this. This is - as you can imagine - awfully frustrating.

lemoutan

I don't use AV software other than taking care and using the occasional scan to verify a cleanliness I've maintained for over twenty years over several machines.

I'll have to figure out some more drastic measures to remove remaining traces of the driver. If I succeed I will of course let you know.

Thanks for your time.