INF is not valid in windows 7 when install the driver for an labview exe file

[bhl3302]

Hi all, I have a labview program that work with a USB dongle board. This program and its driver can be installed in windows xp properly to make dongle work. But when this package was used for windows 7, when installed driver, it always showed "INF is not valid" and driver cannot be installed in Windows 7 properly. Could you give me any idea how should I do to make it compatible with Windows 7? Is it related to any NI-VISA package that I can download from Internet? Thank you very much!

[RavensFan]

It sounds like a problem you need to ask the vendor of this USB dongle board to see if they have drivers compatible with Windows 7.  What exactly does this board do?

[bhl3302]

This is a board we used to communicate with an IC. The strange thing is, some people can use it well in English version windows 7, but east asian version windows 7 cannot support it. So I think the driver itself supports windows 7, but different version windows 7 may have variations. Do you know that does Labview provide any support to this kind of case? Thank you! 

[RavensFan]

If Windows isn't supporting the driver properly, then there is no way for LabVIEW to be able to work with it.  NI-VISA interacts with the Windows drivers.  If the Windows drivers are broken, then there is no way for VISA or LabVIEW to make it magically work.

[amezam]

Hello Bhl3302,

Thanks for posting at NI forums! I think you should follow RavensFan advice on contacting the vendor for information on the driver’s support, or if you have a readme file, you could check on that. Also, are the Windows XP and Windows sharing the same architecture (32 or 64 bits)? Maybe the driver is not compatible with one of them, in case it changed. I did a quick search on the error message you're getting, and I found this forum in which they give some steps you could follow regarding the INF file. For instance, in one of the comments, they say they had a similar issue with another device and they found some work arounds. 

Best Regards,

Alina M