With like a week until Windows 10 comes out .. this is pretty relevant.Any "build" users of Windows 10 know if the EZScan software will work ahead of the launch of this OS?
Any info would be appreciated. Thanks in advance.
Try this right click on the icon for the program.I have attempted to utilize the "fix" we used in Windows 8/8.1 to no avail. Help
Will this also work substituting 'Windows 7' for 'Windows 8' in your example?Try this right click on the icon for the program.
Click on properties
Click on compatibility
Where it says compatibility mode
Click on box that says
Run this program in compatibility mode for
Choose windows 8
Click on apply.
Your program should now be working.
I had no problems Don on the final production version of Windows 10 released today .... they work just fine. It is not rocket science and I posted the YouTube video to help the people that need it.What's utterly stupid is that Whistler (along with GRE before them) is not providing an "unsigned driver".
Whistler provides a .INF file that tells Windows "here is a USB CDC device; when you see this Vendor ID / Product ID, use this Microsoft driver (USBSER.SYS) that's already installed on the system".
The driver (USBSER.SYS) comes from Microsoft as part of the Windows installation. One must presume that it is already "signed" by Microsoft.
I understand that there's a workaround.I had no problems Don on the final production version of Windows 10 released today .... they work just fine. It is not rocket science and I posted the YouTube video to help the people that need it.
I totally understand what you are saying .. and I agree.I understand that there's a workaround.
My point was that such a workaround shouldn't be required. USBSER.SYS is a Microsoft driver supplied by Windows. It's not an "unsigned driver".
The .INF file supplied by Whistler is not a "driver". The driver is the .SYS file. The .INF file merely says "use this Microsoft driver".
That's the stupid part. The .INF file is not the driver. The .INF file merely points to the .SYS file (the driver). The .SYS file comes from Microsoft.I totally understand what you are saying .. and I agree.
I just tried to just install the INF (after removing it the driver) .. and you get "The third-party INF does not contain driver signature information" when you try to install it. Thus the need for the 'work around' to install it.