Low-Level Driver not loaded when CVI application runs from Autostart folder

[Ponkal]

When my CVI5.5 application runs from Autostart folder in Win XP it permanently receives 0 value from CVILowLevelSupportDriverLoaded()function. Software delay (timeout) does not help. The same application started by user (anytime) works perfectly - CVILowLevelSupportDriverLoaded() returns non-zero immediately. I tried to install XP SP1a - did not help. Any suggestion (excluding upgraidng my CVI;)?

[JuanCarlos]

Hi,

I believe that the problem is due to the order the services are being loaded. One thing to try is to set a loop around CVILowLevelSupportDriverLoaded() to keep polling until the driver is loaded. What you can add to this is that after some attempts of CVILowLevelSupportDriverLoaded() you can close the CVIRTE with CloseCVIRTE and reloaded with InitCVIRTE this way you would force the Run-Time to reload and it will catch the current state of the driver and the CVILowLevelSupportDriverLoaded() should return a valid value.

Let me know if you have any questions.

Regards,

Juan Carlos
N.I.

[bue@keba]

Hi,

i have tried the "things" Juan Carlos suggested

    - loopp around CVILowLevelSupportDriverLoaded()  until it returns 1

    - unload an reload Run-Time Engine

but nothing did work.

If i start the application normaly (for example with the windows explorer) it works fine.

Any further suggestions?

Regards,

Peter Bürsher

[vix]

I have the same problem, and I followed the suggestion that Juan Carlos gave. Unfortunately this didn't help me, because CVILowLevelSupportDriverLoaded() always return 0 if the program has been started through the shortcut in the Autostart folder.

Anyway I did some tests, and I found out something that could be useful in finding an effective solution (or a workaround):

• this problem only happens on "fast" PCs, where the boot time is short.When I tried slow old PCs, everything worked fine.
• the problem only happens if the PC is connected to another PC with an ethernet cross cable. If the fast PC isn't connected to another one during the boot, everything works fine
• the problem doesn't happen if you connect the ethernet cable only after the desktop is shown (before the program starts)
• the problem doesn't happen anymore if you close the program started from Autostart folder, and you start it again (doesn't matter if you launch the exe file, a shortcut, ...)

Is this useful?