Curios problem with TestStand and USB-Device

[Herbert Koltschik]

Hello!

This is what I've got:
- PC running Windows 98 Second Edition
- TestStand 2.0.1.f1
- USB Device with Driver

When I install and run TestStand alone, everything works fine.
When I install the Driver for the USB Device alone and connect the USB Device, everything works fine.
When I install TestStand AND the Driver for the USB Device and then connect the USB Device to the PC Win98SE dies with a BSD (blue screen of death). Even worse, after turning off the PC and turning it on again it won't even boot anymore. Only "Format C:" and reinstalling Win98SE can cure the problem.

So in first line I blamed the USB Device Driver to be the bad guy but what makes me wonder a little bit is, when I use TestStand 1.0 instead of
TestStand 2.0 everything works fine and I can use the USB Device as well as TestStand.

So, if someone experienced a similar problem please drop me a line.

Thank You!

Regards
Herbert
*********************************
Herbert Koltschik
Sagem Communication Austria
herbert.koltschik@sagem.com
*********************************

[rpfi]

Hello Herbert,

This a very weird behavior. As far as I know, TestStand does not install hardware drivers. Besides TestStand Engine it installs NI-MAX, NI-VISA, NI-IVI, LabVIEW RTE, CVI RTE, and MDAC 2.5 SP1. Your USB driver may be using a common windows component that may be updated when one of the TestStand components are installed.

What if you do a custom installation of TestStand and try removing one of this components if possible? (Remember that CVI and LabVIEW RTE are needed to execute CVI and LabVIEW code). Another idea would be testing on a different computer.

Regards,

Roberto P.
Applications Engineer
National Instruments
www.ni.com/support

[Herbert Koltschik]

Hello Roberto,

we already performed a custom install of TestStand and it turned out that the problem was related to the TestStand Engine itself (everything else disabled during custom install).

Fortunately we just received an updated version of the Driver for the USB device and the problem is gone now.

Thank you for your efforts.


Regards,
Herbert