NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
NI-488.2 3.1.2
This release fixed several issues affecting MAX stability.
| ID | Description |
| 379939 | An exception could be reported by the System Configuration API when initializing the ni4882 plugin if the NI Configuration Manager service is not running. This could result in a crash of any application using the System Configuration API or be reported as unhandled exceptions in niGPIBsys.dll when using MAX. |
| 373644 | Several issues have been resolved when scanning for instruments in MAX. These issues may have caused MAX to crash or the discovered GPIB instruments to be displayed incorrectly. |
NI-488.2 3.1.1
This release included improved support for Windows 8.
NI-488.2 3.1
This release added support for Windows 8 and fixed the following issues.
| ID | Description |
| 351266 | NI-488.2 for Windows, Version 3.1, adds support for direct entry into ni4882.dll. Previously there was only support for gpib-32.dll. |
| 311091 | In certain PXI Express chassis, the performance of GPIB writes through PXI-GPIB interfaces is very slow. This has been fixed. |
| 370676 | When disconnecting a USB hub with GPIB hardware connected, the GPIB hardware will not be properly removed from the system. This will prevent the use of the device until the system is rebooted. During the following reboot or shutdown, a blue screen error may occur. This has been fixed. |
| 371371 | When disconnecting a USB hub shortly after connecting a GPIB-USB-HS to the hub, a blue screen error may occur immediately. This has been fixed. |
| 144103 | Removing PCMCIA-GPIB interfaces while Windows is hibernated or suspended causes blue screen error during resume. This has been fixed. |
| 122048 | GPIB interface remains in locked state after the locking process is terminated unexpectedly. This generates an ELCK error on subsequent attempts to open the interface. This problem impacted all USB based GPIB interfaces. This has been fixed. |