changes in citrix XP comm database???

[karmic]

I'm new to the citrix world but enjoy working with the software. I'm also new to the newsgroup world so please bear with me... I'm evaluating citrix for my company for use in the oil/gas industry.
Basically, our software is designed to accept raw data through a serial port on one of the workstations and at this point, that will not change. The com port has to be mapped and everything works like a charm under metaframe 1.8 for windows 2000 terminal server.
Citrix licencing makes XP alot cheaper to use but our software will not run properly under XP. My problem is this.
As soon as our software starts up WITH the com port mapped in XP, it will always shut down the software, but not the terminal session. When the com port isn't mapped, the software runs but no data gets through. I need this mapping in order for everything to work. I'm suspecting that the comm driver database in OUR software is too old and not compatible with XP but i would love to know what changes were made in XP that would cause this.

I would really appreciate any input or workarounds anybody could give me at this point.

Thank you...

 

[CitrixEngineer]

The two areas to check first are
1) Does it work at the console
2) Does it work in a Terminal Server Session

I'd guess that the software is trying to access the Com port at a low level and Windows 2000 is not allowing it. Maybe running Filemon would show any errors that might be occurring.

I hope this helps

 

[karmic]

Actually, as of 10 minutes ago the problem was solved. 2 lines of extra code in our software for a workaround.
I appreciate the response