start LabVIEW without mouse and keyboard

[DeWit]

I have a PXI chassis with an embedded controller and some A/D boards etc. I would like to remote control the chassis with the aid of a pocket pc. A connection is made via TCP/IP with a server running on the chassis, this server communicates with LabVIEW through ActiveX. Works perfect.
However, I don't want to connect a keyboard and a mouse to the controller. That's no problem for Windows, but LabVIEW generates an error if I disconnect the mouse, or keyboard or both. The error is:

Error -1073807246 occured at Property Node (arg 1) in VISA Configure Serial Port

Possible reasons:
VISA: (Hex 0xBFFF0072) The resource is valid, but VISA cannot currently access it.

Is there anyway to run LabVIEW without keyboard and mouse plug
ged in?

Thanks

[ebarker]

I am able to run VIs without the keyboard and mouse plugged in. I found some documents that might help you out. What controller are you using?

http://digital.ni.com/public.nsf/websearch/CD2D71AE164494BB86256B480052F661?OpenDocument

http://digital.ni.com/public.nsf/websearch/5E8A683303DCA70286256903005B8309?OpenDocument

[DeWit]

I have a PXI-8176 controller running BIOS v1.6. I found out that it is a bit more complicated. I use the vi to read GPS data via the COM1 serial port.

If I turn on the GPS receiver before I start up Windows, LabVIEW generates this error as COM1 is configured.

If I start up Windows with the GPS receiver turned on and use, for example, Hyper Terminal I can read data from COM1. If I subsequently start LabVIEW, I can also read data from COM1 with LabVIEW.

If I turn on the GPS receiver after I have started Windows and after LabVIEW has configured the COM1 port, the error does not arise. I can use this work around, it would however still be nice to really solve this.

Thanks!

[DeWit]

It has nothing to do with the keyboard or mouse. Even if the mouse and the keyboard are plugged in, the serial port can not be configured if the GPS receiver is turned on during the start up of Windows.

[DeWit]

With the help of the NI helpdesk the problem has been solved. If I call the VISA Close VI first before initializing the COM1 port, I do not get the error anymore.