Filter
Top Products
Chapter 1 Required Configuration, Installation, and Upgrade Information
LabVIEW 5.1 Addendum 1-16
©
National Instruments Corporation
3. At the ok prompt, type:
module-info
You then see information similar to the following lines:
CPU FMI,MB86904 Rev. 2.5 : 70.0 MHz
SBus (Divide By 3) : 23.3 MHz
4. Type go to exit the monitor and resume operation of your system.
If your CPU Revision number (2.5 in this example) is earlier than 3.2, and
your CPU clock speed (70.0 MHz in this example) is less than 110 MHz,
then your computer has this problem. Contact Sun and ask to have your
CPU firmware upgraded to swift_pg 3.2 or later. (Swift is the code name
used by Sun for the SPARCstation 5 firmware.) The Sun Bug ID number
for this problem is 1151654.
If you have a SPARCstation 5 with this bug, National Instruments strongly
recommends upgrading your firmware.
Note This problem can affect programs other than LabVIEW. Notably, the GNU C
compiler also can produce code that hangs your system in versions prior to 2.6.0.
Compatibility Issues between Versions 4.1 and 5.
x
This section describes the compatibility issues between different
LabVIEW versions.
Compatibility VIs for New Server Functionality
LabVIEW now can act as a server, so you have expanded control over VIs.
You can control VIs across a TCP/IP network and, on Windows, the
ActiveX interface. LabVIEW includes Compatibility VIs for the VI
Control VIs that exist in previous versions. For information about how to
implement the functionality from the VI Control VIs using the new server
functions, open each VI Control VI and analyze the implementation of the
VI Server feature. You can copy this code to your new LabVIEW
applications.
Compatibility VIs for ActiveX Functions
The ActiveX functionality has expanded. The functions are more generic
because LabVIEW now can act as an ActiveX server as well as a client.
Compatibility VIs are provided for the ActiveX functions that exist in