Could a change in the Windows operating system impact DAQ response?

[KelanWieloch]

I use a PCI-6013 analog DAQ card (vintage 2002) to control and acquire data with a fairly old computer running Windows 2000. I installed the card in a newer computer running Windows XP. There were no other changes to software or hardware.

The data now frequently shows a strange response in the first 0.3 seconds after starting to collect data. It reads very low (sometimes bottoming out) and comes up to the calibrated value within that first 0.3 seconds.

Could the change in operating system be the cause of this? Is there something else I can do to diagnose what is happening? 

-Kelan

[JÞB]

This sounds a bit questionable.  you are jumping from NT to XP withough changing software?

Well vintage 2002 would put you in LabVIEW 5.1 and most likely traditional DAQ.

LabVIEW 5.1 has no official support for Windows XP nor has 6.02 although it Should "Run without errors" according to prophisy-  that does not mean that there won't be issues just no errors.

What drivers and software are you trying to port from NT to XP?

[AnalogKid2DigitalMan]

Have you verified the integrity of all your signal/power connections after moving the card over to the new PC?

-AK2DM

[Dennis_Knutson]

It is windows 2k to XP and 2002 is LabVIEW 6.1 (assuming the LabVIEW was kept up to date) and the move should work but as Jeff says, need to know what drivers you are using. Seeing the code would also help as there is certainly bad ways to write DAQ code where problems may not show at first.

[KelanWieloch]

Thanks for everyone's input. I am not using LabView. The programming is all done in Visual Basic and utilizes an obsolete graphic interface package called SoftWire. (Note: SoftWire is only a series of interface tools such as graphs, power bars, buttons...)

I will verify the signal/power connections. However, the response is on target after the initial delay of 0.3 seconds.

What sort of poor programming style would lead to poor DAQ response?