"Device Not Found" incurred using non-NI-h/w-bound specimen code

[SimonFay]

Having built an application from the 'Labview <-> Serial.vi' supplied by NI for LV5 I find that when distributed to PCs the .exe generates "Device not found" (in 'Bytes at Serial Port' sub-vi) for any port no. I pick. Attempted verification on 2 PCs using 'loopback' (only LV4 build can be loaded by me) gives no port echo at all, nor even an error, even when shorting pins in PC's rear to take cable-config out of eqtn.

[mikeporter]

Are you including the file "serpdrv" in your build. It is necessary with the old-style serial drivers. Also make sure you are referencing a serial port that exists on the target machine and is not being used by something else. The mere fact that nothing is plugged into the port doesn't mean its not in use...

Mike...

[SimonFay]

Mike - thanks, serpdrv seems to be the crux of it, although even with serpdrv sitting by the exe (I haven't yet successfully built it in) the port number I need to select keeps changing from 0 to 1 and back session by session. Most peculiar.

[mikeporter]

When building an executable, include serpdrv in the source file list as a support file. This will cause the installer to include it.

Can't think why the port number would be switching around. As you said: "Most peculiar."

Mike...

[mikeporter]

Are you including the file "serpdrv" in your build. It is necessary with the old-style serial drivers. Also make sure you are referencing a serial port that exists on the target machine and is not being used by something else. The mere fact that nothing is plugged into the port doesn't mean its not in use...

Mike...