How I fix printers problem?

[gokuzeus67]

We have identified an issue with NI-DAQmx that was introduced in version 9.1 and remained through 9.2.1.  When certain USB human interface devices (HID) such as keyboards, mice, printers, and so on are connected to the PC, some NI devices will no longer be detected by the NI-DAQmx driver.

When these USB devices, including common HP and Apple keyboards and mice, NI-DAQmx sees these devices as NI-DAQmx devices and adds them to the MAX database.  When this happens, it can cause the database to no longer be usable by DAQmx.  As a result, the main symptom of this issue is being unable to see your devices in Measurement & Automation Explorer.  

This issue will be corrected in NI-DAQmx 9.2.2.  We will also be releasing NI-DAQmx 9.1.7 that includes the fix, for those who wish to minimize upgrade risks.  Alternatively, we are making patches available that will fix the issue for NI-DAQmx versions 9.1, 9.1.1, 9.1.5, 9.1.6, 9.2, and 9.2.1.  We recommend that all users apply this fix.

[gokuzeus67]

---

@gokuzeus67 wrote:

We have identified an issue with NI-DAQmx that was introduced in version 9.1 and remained through 9.2.1.  When certain USB human interface devices (HID) such as keyboards, mice, printers, and so on are connected to the PC, some NI devices will no longer be detected by the NI-DAQmx driver.

When these USB devices, including common HP and Apple keyboards and mice, NI-DAQmx sees these devices as NI-DAQmx devices and adds them to the MAX database.  When this happens, it can cause the database to no longer be usable by DAQmx.  As a result, the main symptom of this issue is being unable to see your devices in Measurement & Automation Explorer.  

This issue will be corrected in NI-DAQmx 9.2.2.  We will also be releasing NI-DAQmx 9.1.7 that includes the fix, for those who wish to minimize upgrade risks.  Alternatively, we are making patches available that will fix the issue for NI-DAQmx versions 9.1, 9.1.1, 9.1.5, 9.1.6, 9.2, and 9.2.1.  We recommend that all users apply this fix.

---

Does anyone know the anwser?

[rolfk]

---

@gokuzeus67 wrote: Does anyone know the anwser?

I have no idea what the question is, so the answer is impossible to give. You seem to have quoted a bug release from NI for DAQmx 9.2 or thereabout and since this release is more than 10 years old it would seem pretty irrelevant nowadays. Or are you still using one of the mentioned DAQmx releases? Why?