> I have similar problems with ActiveX VB DataSocket component and > DataSocket Server. I have a dual processor XEON machine and if I > enable either the second processor, or hyper threading then the > application in the auto-read mode (answering interrupts that are sent > from the server to a subscriber) will often miss interrupts. After a > couple are missed then things seem to be all jammed up and no more > interrupts are answered. However, this is only for transfers of large > data arrays and does not seem to affect transfers without interrupts > of boolean attributes. Have not tried all other permutations of > varible types and attribute types, but I think it is clear from the > other comments (especially Elisabeths's) that hyper threading and/or > dual processors can not be relied on. >
As I mentioned in my previous post, LV itself should perform correctly on multi and hyper CPU'ed computers. Of course there could be some NI components that don't. If you suspect this, please file it as a bug report and maybe they can get you a new version of the component that is correct. I know that recently MS introduces the virtual user desktop feature, and this threw some of the components for a loop. They want to start up one server,and with this new feature, the thing they were relying on to make sure there is only one server changed from beneath them, and this could cause problems. When these things are discovered/reported, they take a pretty high priority. Greg McKaskle
