Threads on 2000 and 2000xp

[Blake]

I have an application with a thread(using the default thread pool and CmtScheduleThreadPoolFunction) that monitors and receives data from a RS232 port and displays the information on a uir panel. It works fine on 98 and 98SE but does not function and almost locks up the machine under 2000 and 2000xp. Help!

[Jason F.]

What do you mean by the application "does not work" on Windows 2000? Is the RS232 communications not functioning properly or does your user interface become unresponsive? What functions are you using to communicate via RS232, the functions in the RS232 library, or inp() and outp()?

If you could submit a small example that reproduces the behavior on Windows 2000/XP it would help a great deal in determining where the cause of the problem is stemming from.

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask