Posted: Sat Aug 10, 2013 1:20 am
I don't know for sure, but I think the problem is our Delcom USB drivers are not digitally signed. Actually we didn't write the WinUSB drivers--Microsoft did; we only generated the CAT and INF files that provide the information to Windows to associate the Delcom USB interface to WinUSB. With XP, the OS didn't care that the CAT/INF files weren't signed. With Vista/Win7, the OS complained, but allowed the user to continue with the installation. As I understand it from reading the web, Win8 won't allow installation with unsigned CAT/INF files, even though the WinUSB files themselves are signed by Microsoft.
Why aren't the Delcom WinUSB drivers signed? Because at the time we generated these, it cost $2000 to get a certificate. It appears that the cost of the certificate may have fallen to around $200 now, but I don't remember how to construct the CAT and INF files anymore. So there is likely quite a bit of labor involved also.
Of course, we don't know for sure if signed drivers would provide a functioning interface in Win 8, or with the newer hardware that is likely being used with Win8.
Why aren't the Delcom WinUSB drivers signed? Because at the time we generated these, it cost $2000 to get a certificate. It appears that the cost of the certificate may have fallen to around $200 now, but I don't remember how to construct the CAT and INF files anymore. So there is likely quite a bit of labor involved also.
Of course, we don't know for sure if signed drivers would provide a functioning interface in Win 8, or with the newer hardware that is likely being used with Win8.