Virtual Serial Port is present with HyperTerminal, but not with MAX

[Chris_12345]

I am using a third-party application that generates a virtual serial port.  Under Windows 2000, both HyperTerminal and MAX can see this port, and both function properly.  However, under Windows XP, only HyperTerminal can see and use the port.  MAX does not list it.  I have tried using a LabVIEW "VISA Resource Name", setting its property to Allow Undefined Names, typing in the name, and using it with VISA Write, but it reports error -1073807343.

Does anyone know why MAX would not see the port, but that HyperTerminal does?

Thank you for your help.

[unclebump]

Serial ports in XP work a bit different. You may need a new driver explictly for XP. What program and version are you using??

[Chris_12345]

I am using

Windows XP Home SP2

NI-MAX 3.1.0

NI-Serial 1.6

Is this the info you were asking about?

[unclebump]

All of that info helps, but what is the third party program??

[Chris_12345]

The third-party program is something obscure that you probably haven't heard of - its 2D optical code reader software from Micronic/Steribar.  In their software, I can set the name of the Virtual Serial Port.

Anyway, I have been trying different things here.  I tried upgrading to MAX 3.1.1 and Serial 1.7, to no avail.   However, I had another idea.  MAX shows "COM3", which does not correspond to any physical port, so I tried naming the Virtual Serial Port to be "COM3".  This works!  I can read the 2D optical codes in LabVIEW by simply selecting COM3.  Going back to HyperTerminal, that also works, but it shows "COM3" twice in its port selector list, and both selections communicate with the 2D optical code reader.  MAX only shows one listing for COM3, and using it to try to communicate with the code reader is unsuccessful.

Well, it works now with LabVIEW, so I won't touch it anymore.