README.txt LabVIEW 6.1 Windows Nov. 27, 2001 This file contains important last minute information about the Windows LabVIEW 6.1 CD. For the latest information, please visit our web site at this web address: http://www.ni.com/cgi-bin/redirect.cgi?dest=lv61faq ---------------------------------------- -- If you are using the 3D ComponentWorks UI controls in Lookout 4.5.1 and then install LabVIEW 6.1, these 3D controls will switch to an evaluation mode. In Lookout, you can revert these controls to the 2D version that does not require the controls to be in an evaluation mode. To fix this problem, you can install Lookout 5.0, install Measurement Studio 6.0, or contact National Instruments for a patch. -- If you are installing LabVIEW 6.1 on a computer that has Lookout or LabVIEW DSC (6.0 or 6.0.2), upon reboot you will see an error message saying "The procedure entry point VDTStartFromats could not be located in the dynamic link library lkdynam.dll." You can correct this error using any of these methods: upgrade LabVIEW DSC to version 6.1 or later, upgrade Lookout to version 5.0 or later, or run the Logos installer located in the "Logos Installer" folder at the top level of the LabVIEW 6.1 CD. -- If you have earlier versions of the LabVIEW Application Builder (6.0.3 and earlier) on your computer, uninstalling LabVIEW 6.1 might break the earlier Application Builders (the VIs will load but they will be broken). To fix them, you can run "\applibs\lvdllbuilder\lvdb.exe" found in the directory of the earlier version of LabVIEW. -- If you uninstall LabVIEW 6.1 and you still have a LabVIEW 6i installation on your computer, it is possible that you may have to repair LabVIEW 6i in order to use embedded ActiveX controls within it. You can do this by copying nicont.dll and nicontdt.dll from the "ActiveX Container" folder at the top level of the LabVIEW 6.1 CD to your disk (the "shared" folder in the "National Instruments" folder is a good place). Then run the commands "regsvr32 nicont.dll" and "regsrv32 nicontdt.dll" to register these components. -- The note that appears in the Remote Panel License section in Chapter 17, Networking in LabVIEW, of the LabVIEW User Manual should read: "The server computer managing remote front panels must have the LabVIEW Full or Professional Development System or must build the front panels into a stand-alone application. Clients can use any LabVIEW development system to view and control those front panels remotely." -- The LabVIEW Help incorrectly states that the Color to RGB and RGB to Color VIs are available only in the LabVIEW Full and Professional Development Systems. Actually, these VIs also are available in the Base Package. -- The LabVIEW Help incorrectly states that the notifiers out parameter of the Wait on Notification from Multiple function returns the notifiers input unchanged. Actually, the notifiers out parameter returns a reference to the notifier that received a message. -- Missing from the LabVIEW Help: If a queue or notifier reference becomes invalid (for example, by being closed), all functions waiting on that reference stop waiting. These functions include Wait on Notification, Wait on Notification From Multiple, Dequeue Element, Enqueue Element, Enqueue Element At Opposite End, and Preview Queue Element. -- If while installing LabVIEW on Windows NT/XP you encounter a "1923. Service 'NILM License manager' could not be installed" error or a "1920. Service 'NILM License manager' failed to start" error, select the "Ignore" option and let the installation complete. After installation, place double quotation marks ("...") around the value of ImagePath in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NILM License Manager. -- If you installed LabVIEW on Windows NT/XP and you receive "Error 0193: %1 is not a valid NT application" from NT Services, place double quotation marks ("...") around the value of ImagePath in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NILM License Manager and restart the NILM License Manager service.