Includes the latest and most frequently asked questions regarding protocol products covering Bluetooth, DDR3 & DDR4, Ethernet, Fibre Channel, IEEE1394, Infiniband, PCI Express, PCI/PCI-X, SAS, SATA, USB, and others.
In general it should work, however XP is funny about exactly when you connect a device relative to installing the drivers (same for most HW on XP). As a rule you must install the drivers first on XP and THEN connect the HW. If you don’t it tends to make the device a generic USB device and it is really difficult to undo (uninstall this) - if this is the case you can (as administrator) use device manager to view hidden devices and then un-install every generic USB device (this Microsoft driver just enumerates a device and does nothing else and often prevents the right driver from finding it). Once you have uninstalled all generic USB reboot (no HW attached) and install the Chief SW, then connect the HW. Alternatively if you are connecting to a USB hub in the monitor or keyboard this may also be the cause of the problem (XP Power management is the culprit). To verify this first connect the Chief directly to a PC root port where it should work, then you can sort out the hub once the XP system knows how to identify the Chief.
(All support files listed here have been scanned and are virus free)