Agilent RfSigGen IVI-COM Driver Read Me

***********************
**** Read Me First ****
***********************

May 2, 2006
Version 1.1.4.33



Introducing the Agilent IVI-COM Driver for ESG/PSG and Synthetic Up Converter
-----------------------------------------------------------------------------
The instrument driver provides access to the functionality of
ESG/PSG through a COM server which also complies with the IVI
specifications. This driver works in any development environment which
supports COM programming including Microsoft® Visual Basic, Microsoft
Visual C++, Microsoft .NET, Agilent VEE, National Instruments LabView,
National Instruments LabWindows, and others.


Supported Instruments
---------------------

E4428C, E4438C, E8241A, E8244A, E8251A, E8254A, E8247C, E8257C, E8267C,
E8257D, E8267D, E8663B, N8211A, N8212A


Installation
-------------
System Requirements: The driver installation will check for the
following requirements. If not found, the installer will either
abort, warn, or install the required component as appropriate.

Supported Operating Systems:
Windows® 98
Windows Me
Windows NT 4.0 (SP6 or later)
Windows 2000
Windows XP

Disc Space:
Shared Components: 4,843 KB
Driver: 606 KB
The shared components are installed with the first driver
installed.

Shared Components
Before this driver can be installed, your computer must already
have several components already installed. The easiest way to
to install these other components is by running the Ivi Shared
Components installation package available from the IVI Foundation
as noted below. It installs all the items mentioned below.

IVI Shared Components version 1.1.3.0 or later.
The driver installer calls an installer for these components if
they are not already present on the system. The installer,
IviSharedComponents.msi, must be in the same directory as the msi
file for this driver.

The IVI Shared Components installer is available from:
http://www.ivifoundation.org

If the driver installer exhibits problems with installing the IVI
Shared Components, find the program IviSharedComponents.msi and
Run the program. It is able to install many of the required system
components, including Windows Installer 2.0.

Windows Installer
Version 2.0 or later. The IVISharedComponents.exe program will
install version 2.0 of the Windows installer.
It is also available from:
For Win98/Me:
http://www.microsoft.com/downloads/release.asp?ReleaseID=32831
For WinNt4/2000/XP:
http://www.microsoft.com/downloads/release.asp?ReleaseId=32832

Microsoft XML 4.0
The Configuration Server, an IVI Shared Component, uses Microsoft's
XML 4.0 parser. The IVI Shared Components will install the XML 4.0
parser. You can download the parser and its associated SDK from:
http://microsoft.com/downloads
Enter "xml 4.0" as keywords.

Microsoft HTML Help Viewer (Win98, WinNT) Version 1.32 or later
The driver will install without the help viewer, but you will not
be able to use the help file for the driver. You can download the
help viewer from:
http://microsoft.com/downloads
Enter "html help workshop" as keywords

MS Windows® Script
Typically wscript.exe is installed as part of the OS or with
Internet Explorer. If you see an error about wscript.exe, you need
to install the Windows Script.
Download from:
http://msdn.microsoft.com/downloads
Enter "windows script" as keywords. Use the one appropriate for
your Operating System.

VISA-COM
Any compliant implementation is acceptable. Typically VISA-COM is
installed with VISA and other I/O library modules.

If you are using Agilent Technologies' VISA-COM, use
version 2.4.0.5 or later. The latest version of Agilent's I/O
Libraries includes the required version of VISA-COM.

I/O
If you are using Agilent Technologies I/O libraries, use version
M.01.04 or later. You can download the latest version from:
http://www.agilent.com/find/iolibsforivicom

If you are using National Instruments I/O libraries, use NI-VISA
version 3.0.1 or later and NI-488.2 version 2.2 or later.


Additional Setup
----------------
.NET Framework
The .NET Framework itself is not required by this driver. If you
plan to use the driver with .NET, Service Pack 2 is required.
Download from:
http://msdn.microsoft.com/netframework/downloads/updates/sp/default.asp

The .NET Framework requires an interop assembly for a COM
server. A Primary Interop Assembly, along with an XML file for
IntelliSense is installed with the driver. The driver's PIA, along
with IVI PIAs are installed, by default, in:
:\Program Files\IVI\Bin\Primary Interop Assemblies

The PIA is also installed into the Global Assembly Cache (GAC) if
you have the .NET framework installed.

If you install the .NET framework later, you can use the file:
:\Program Files\IVI\Drivers\\DotNet.bat
to put the driver's PIA into the GAC and properly register it.


Start Menu Help File
--------------------
A shortcut to the driver help file is added to the Start Menu,
Programs, IVI, Agilent group. It contains "Getting
Started" information on using the driver in a variety of programming
environments as well as documentation on IVI and instrument specific
methods and properties.

You will also see shortcuts to the Readme file and any programming
examples for this driver.


MSI Installer
-------------
The installation package for the driver is distributed as an MSI 2.0
file. You can install the driver by double-clicking on the file.
This operation actually runs:
msiexec /i .msi

You can run msiexec from a command prompt and utilize its many
command line options. There are no public properties which can be
set from the command line. You can also install this driver from
another installation package.


Uninstall
---------
This driver can be uninstalled like any other software from the
Control Panel using "Add or Remove Programs".

To uninstall the IVI Shared Components you must use the IVI Cleanup
Utility available from the IVI Foundation at:
http://www.ivifoundation.org/

Note: All IVI-COM drivers require the IVI Shared Components to
function. To completely remove IVI components from your computer,
uninstall all drivers then run the IVI Cleanup Utility. This utility
does not remove any IVI drivers.

Issues and Notes
----------------
Digital modulation API is sequence dependent. The standard must be selected
prior to changing clock source and data source and bit files. Also, the
data source must be set to user file before selecting a bit file name.

The arb upload will use more efficient memory management when used with
firmware version from C.03.20. For earlier versions of firmware, the entire
arb file must be accumulated in PC memory before sending, which may cause
out of memory problems for big arb files.

This driver's primary interop assembly references the VISA-COM primary
interop assembly version 3.0.0.0. You may, however, have version
1.0.0.0 on your computer. At the time this driver was released, the
IVI Foundation was in the process of approving version 3.0.0.0, so an
official PIA might not yet be available. Also, your installed version
of IVI-COM may not include this latest PIA. In either case, you can
configure your .NET application to use version 1.0.0.0 of the VISA-COM
PIA. This is usually only necessary if your .NET application program
uses the driver's System.IO property. In this case you may also have to
add a reference to the 1.0.0.0 PIA file Ivi.Visa.Interop.dll found in:
\VISA\VisaCom\Primary Interop Assemblies\

The common language runtime checks the application configuration file
for information that overrides the version information stored in the
calling assembly's manifest. The application configuration file can be
deployed with an application, but is not required for application
execution.

An application configuration file resides in the same directory as the
application's executable and has the same base name as the executable
with a .config extension. For example, the configuration file for
C:\Program Files\Myapp\Myapp.exe is C:\Program
Files\Myapp\Myapp.exe.config. To make your application use the version
1.0.0.0 PIA, you would put:

  <configuration>

   <runtime>
 
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <dependentAssembly>

         <assemblyIdentity name="Ivi.Visa.Interop"

                   publicKeyToken="a128c98f1d7717c1"

                   culture="Neutral" />

         <bindingRedirect oldVersion="3.0.0.0"

                   newVersion="1.0.0.0"/>

      </dependentAssembly>

    </assemblyBinding>

   </runtime>

</configuration>