open/close keyboard error

[AstroMed_Glen]

Hi, I was wondering if anybody had any experience with an error like this. I have a Labview made Application that is experiencing some conflicts after installation on a Windows 2000 machine. Bare in mind that it has been successfully installed on 2000 machines in the past. The problem is that when the application is run, the user receives a message that reads,"Select sub.vi to open keyboard". I don't believe this refers to a sub vi called "sub.vi" but a sub vi in general. Could there be a conflict with the keyboard drivers? I unfortunately am not a first hand witness, so this is all the info I have. Could a USB keyboard cause errors like this or something?

Glen D

[Evan]

Glen,
I have never heard of this issue, and can not imagine how a keyboard driver would conflict with a generic VI or exe.

What I am wondering is does the application do any keyboard filtering, or have any VI srelated to the keyboard?

Does the error occur at load, like it is searching for a VI, or is it after the exe is run that the error pops up?

Does the error happen for any exe? Can you send the customer a real simple random number to a chart exe and see if the issue still occurs?

Lastly, you could also suggest that the customer upgrade their keyboard dirver I guess? Or ask them to try boot their computer with a different keyboard and see if that solves it?

[AstroMed_Glen]

Evan,

Thank you for all your suggestions. The exact error messages our customer is receiving are 'Select sub.vi to open keyboard' and 'Select sub.vi to close keyboard'. These errors occur when the exe is tried to run. By no coincidence, two of the vi's in this exe are called "open keyboard.vi" and "close keyboard.vi". This sounds strange to me because I would think the error message would read something more like, " Vi not found. Select 'Open Keyboard.vi'" The actual message implies that LabView knows what the missing vi's do, unless it is some other kind of error.
It also does not make sense to me that these two vi's would go missing on 1 out of who knows how many installations. Is there any possible explaination for that?
Lastly, an
d somewhat unrelated, at the heart of these vi's is a CIN. How do I review the code of the CIN?

Thanks again
Glen D

[Tom_Hawkins]

Is it remotely possible these are some kind of debugging or error-trapping dialogues left in the code by the original programmer, and which are only showing up in this particular installation for some reason? You might be able to locate this by searching the VI hierarchy for a piece of the text in the error, e.g. "select" or "keyboard"...