Hello,
I am trying to implement VirtualHere to share several Wibu Codemeter dongles, (I still use only one to test and then we will buy the license) and it works great but I have a problem that I would like to see if it could help me.
Sometimes if you are using the dongle on the client and the internet fails or the internet is very slow on the client side it gives a bsod "STOP 0x0000000A: IRQL_NOT_LESS_EQUAL - usbstor.sys".
Since it only happens sometimes this is not very serious, the serious part is on the side of the server:
Feb 14 17:22:24 Server vhusbdx86_64 [2008]: Device 31 [064f: 03f3] SURPRISE UNBOUND from connection 28
Feb 14 17:22:24 Server vhusbdx86_64 [2008]: Unmanaging device 31 [064f: 03f3]
Feb 14 17:22:31 Server vhusbdx86_64 [2008]: Connection 28 successfully removed (reason: timeout)
Feb 14 17:22:40 Server vhusbdx86_64 [2008]: Warning, could not open device product file /sys//devices/pci0000:00/0000:00:14.0/usb3/3-1/product, error 2 ( No such file or directory)
Feb 14 17:22:40 Server vhusbdx86_64 [2008]: Found High speed device [064f: 03f3] "0x064f, 0x03f3" at address 31
After this error the dongle is no longer accessible and the only way to work again is to remove the dongle physically (on server) and put it back again.
Server OS: Debian 9
Client OS: Windows 7 32 bits and I try 64 bits and have the same problem.
P.S: Sometimes the kernel have this message below but it still works normally
Feb 14 16:48:42 Server vhusbdx86_64[2008]: Device 31 [064f:03f3] UNBOUND from connection 16
Feb 14 16:48:43 Server kernel: [ 4360.677514] usb 3-1: usbfs: process 5737 (vhusbdx86_64) did not claim interface 0 before use
Feb 14 16:50:00 Server vhusbdx86_64[2008]: Device 31 [064f:03f3] BOUND to connection 16
.
Hi, actually you need to use win10 instead of win7 if possible because win7 wont be support be me or microsoft soon, so no fixes are planned for win7 now. However looking at the crash, its not actually in the virtualhere windows driver, rather its in the win7 usb disk driver so its not fixable. I have a wibu codemeter dongle i use for testing and havent seen this issue, but i do use win10 now...
I tried win10 and it works
I tried win10 and it works flawlessly.
My problem is that we currently have lots of equipment with win7 and at this point we can not update all of them.
I'll try to figure out a solution to the windows driver problem.
Thank you very much for your response and help.
New try
Hello Michael,
I have a question about this... Maybe is a stupid question...
This is a Windows driver problem, OK I agree with you but after read a lot of forums about usbstor.sys I'm thinking to try use Zidag software to replace default driver of codemeter (usbstor) by winusb...
Do you think it's a waste of time or maybe can work?
Thanks
.
It wont work because something has to do the function of the usbstor.sys driver, winusb doesnt do this. You really need to be using win10
.
yes but the problem is that if you put the codementer directly on the laptop with Windows7 it always works without any anomaly.
and through the virtualhere the bluescreen does not always happen, usually only happens when the client-side internet connection is weak or fails.