Agilent VEE 9.2 Readme


Microsoft® Windows® 7 supportability

Agilent VEE 9.2 is a free upgrade of Agilent VEE 9.0. Agilent VEE 9.2 supports Windows 7 (Professional, Ultimate, and Enterprise with 32-bit and 64-bit supportability). Note that the 64-bit support has a 32-bit application running on WOW64 (Windows-on-Windows 64-bit) emulator.

When using Agilent VEE 9.2 in Windows 7 (both 32-bit and 64-bit), please be informed of the following limitation:

1. Configure IVI Driver Sessions

If you are using IVI-COM driver, the Configure IVI Driver Sessions feature which uses Agilent Instrument Explorer is currently unavailable.


When using Agilent VEE 9.2 in Windows 7 64-bit using WOW64 emulator, please be informed of the following limitations:

1. Error running Agilent VEE runtime programs containing Matlab scripts

If you are running Agilent VEE runtime programs (.vxe) containing Matlab scripts for the first time, the error dialog "Matlab engine could not be started" might appear. Steps to fix this:

  1. Go to Start | Run and type 'secpol.msc'.
  2. In the prompted dialog, navigate to Local Policies | Security options.
  3. Set the value of User Account Control: Run all administrators in Admin Approval Mode to Disabled.
  4. Run the Agilent VEE runtime program again and it should work fine.
  5. After that, you may re-enable Run all administrators in Admin Approval Mode and the Agilent VEE runtime program should still run well.

2. Use an Administrator role to enter product key

If you have not entered Agilent VEE product key during installation, please follow these steps to update the product key:

  1. Go to Start | All Programs and navigate to Agilent VEE 9.2.
  2. Right-click on VEE Pro 9.2.
  3. On the context menu, select Run as administrator (If not Run as administrator, the product key might not be visible to other users).
  4. If evaluation period has expired, proceed to step 5. After Agilent VEE is launched, go to Help | Product Key.
  5. Enter the product key at the prompted dialog box.

3. Declare global variable name

If an invalid name is used when declaring a global variable name, it will revert back to the old name without any error dialog.

4. Sequencer object Transaction

When adding Sequence Transaction, please use supported naming convention for Test/Exec name. If a Sequence Transaction cannot be edited due to invalid variable name, please delete that Sequence Transaction (select the incorrect transaction, right click and select Delete Trans) and replace with a new sequencer transaction.


National Instruments (NI) interface is not officially supported

Agilent VEE 9.2 no longer provides official NI supportability. However, you are still able to use the existing NI interfaces.


For answers to installation related questions, review the file InstallReadme.htm in the Autorun directory of your Agilent VEE CD.

 

What's been fixed

ID

Descriptions

Broken in

SAD00403891

VEE sometimes communicate with wrong instrument when using dynamic visa address

9.01

SAD00389124

Conflicts between UserFunction and built-in function when both having the same name

9.0



Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

© Copyright 2010 Agilent Technologies, Inc.