CVILowLevelSupportDriverLoaded()

[fpmd]

I am using a single board computer to run a CVI application in XP embedded on boot up using registry key:
HKLM\software\Microsoft\Windows\CurrentVersion\Run\"stringvalue of my application". The application will check the low level driver with function CVILowLevelSupportDriverLoaded(). The problem is only when the ethernet is connected, the system can't detect the low level driver, and later low level functions such as inp, outp don't work well. If the computer boots up without ethernet connected, everything is fine.

Any confliction between the driver loading and the ethernet connection? Have you met this kind of problem before? Thanks very much.

fpmd.

[Scott Y]

Hello,

These is a similar issue discussed in this thread. The behavior you describe may be related to the order that Windows services are loaded.

I would suggest calling CVILowLevelSupportDriverLoaded in a loop waiting for it to return successfully. If it fails some large number of times in a row you can force the CVI runtime engine to reload the state of the driver by calling CloseCVIRTE and then InitCVIRTE.

Scott Y
NI

[bilalD]

CVI 7.1 is not supported on XP Embedded (see release notes for list of supported OS's). We have not done any CVI testing for XP Embedded on a single board PC. The low level driver was designed for use with desktop PC, so there might be some unexpected behaviors that might occur with on a PC 104. It depends really on how similar the kernels for XP and XP embedded are.