Need LV runtime engine w/o cvintdrv.sys

[InfiniteNothing]

I'm trying to get my ap validated by Microsoft. The testing company said they got the following error when trying to validate my app: "The application installed a kernel-mode driver without using the CreateServiceAPI. ImagePath was not set for service cvintdrv.sys "

I think that particular build included the LV8.0 runtime engine. Anyone familiar with this driver, why it's installing with LV, or how I can resolve this problem. 

[Burt_S]

Hello, Unfortunately I cannot find a whole lot of information on the cvintdrv.sys file.  According to this KnowledgeBase, it is a low-level support driver for CVI.  I also don't know of any way to install the runtime engine without this file.  Do you have anymore information on what goes on in the validation process?  Information on what this file is doing that is causing a problem, and why this behavior is an issue at all, might lead to a workaround.

[InfiniteNothing]

I am curious why the LV RTE is installing a driver for CVI.

I will look into the pass criteria. The tester mentioned something about the driver not being Microsoft WHQL certified but the test document itself mentions running the installer (and msiexec.exe) under Application Verifier and testing the driver with Driver Verifier

[rolfk]

---

InfiniteNothing wrote:

I'm trying to get my ap validated by Microsoft. The testing company said they got the following error when trying to validate my app: "The application installed a kernel-mode driver without using the CreateServiceAPI. ImagePath was not set for service cvintdrv.sys "

I think that particular build included the LV8.0 runtime engine. Anyone familiar with this driver, why it's installing with LV, or how I can resolve this problem. 

---

This driver is needed for the Port IO functions in LabVIEW. I'm afraid there is no way to get this driver not installed with the runtime install, unless there is an undocumented switch for the installer itself.

Rolf Kalbermatter