October 29, 2001

Overview

Release 3.4.3 of the Empack software includes Version 3.4.3 of the host libraries and Version 3.4.3 of the Embedded Firmware and FPGA configurations.

The following changes are introduced in this release:

• New environment variable to identify the installation directory.

• Serial numbers added to emdiag log files.

• The special flash conversion files have been re-introduced in the software distribution.

• New version of Empack Embedded Code.

The following changes affect Solaris users only:

• Fixed device driver for Solaris 7 and 8 on Sparc platforms.

• The Solaris device driver now supports 64-bit Solaris.

The following changes affect Windows users only:

• The HDLC support files are now included in the software distribution.

• The emflash program reports Windows 2000 Plug & Play problems.

• New Windows installer options.

• New Windows device information file.

Notes:

This release includes new embedded code. Customers should run the emflash utility after installation.

New Environment Variable to Identify the Installation Directory

The Empack API now looks for a new environment variable named EMAPI to identify the top-level installation directory. This is done to avoid possible conflicts with other CAC products that might be installed in a different location.

When looking for the top-level directory, the API first looks for the EMAPI environment variable. If this is not set, the API then looks for the old CAC environment variable.

For Solaris users, at least one of those environment variables must be set. There is no need to set the EMAPI variable if you already have the CAC variable naming the top-level directory for the Empack software.

For Windows users the API will look in the system registry if neither of those variables are set. The key is found in HKEY_LOCAL_MACHINE/SOFTWARE/CAC/emapi_path. This is new a new key as of version 3.4.3. The old key, named HKEY_LOCAL_MACHINE/SOFTWARE/CAC/Path, is no longer used. The Empack API installer for Windows will add this new key and set the new environment variable.

Serial Numbers Added to Emdiag Log Files

The emdiag diagnostic program now reports serial numbers for Empack base boards and mezzanines in its log files. The serial numbers for all units are listed when the Empack configuration is displayed in the log file and for each unit as the test programs are run.

Special Flash Conversion Files Re-introduced in the Software Distribution

The special flash files, conv1.bin and conv2.bin are once again included in the software distribution. These files are used by the emflash program to update the flash from older Empacks that still have version 2.x or earlier versions of the embedded code.

New Version of Empack Embedded Code

The new version of the embedded coded, in the flash file fld343.bin, changes the SCSI inquiry results sent from the Empack. It no longer includes the embedded code version number in the device identification. This change was implemented to avoid problems caused by the Plug and Play implementation in Windows 2000. (see below for more details).

The following changes affect Solaris users only:

Fixed Device Driver for Solaris 7 and 8 on Sparc Platforms

A problem with the Empack device driver on Sparc platforms running Solaris 7 or Solaris 8 has been solved. The problem caused the system to crash when the device driver was installed or when Empacks were first accessed.

Note: there is still an issue with backwards compatibility for Empack devicer code compiled on Solaris 8. Our experience shows that the device driver compiled on Wolaris 8 with Gnu CC version 2.95.2 will crash when installed on earlier versions of Solaris. The device driver compiled on Solaris 2.6 or 7 works on Solaris 2.6, 7 or 8.

The Solaris Device Driver Now Supports 64-bit Solaris

Modifications to the device driver code and support files provide support for 64-bit Solaris on Sparc platforms. Detailed information for installing the 64-bit device driver is in the README file location in the $CAC/empack/soldev directory.

Note that the Empack API library is still not 64-bit compatible but using the 64-bit device driver allows Empacks to be used in the 64-bit environment.

The following changes affect Windows users only:

HDLC Support Files Are Now Included in the Software Distribution

A library to support HDLC streams via the Empack E1 and T1 interfaces has been available for the Windows platform but was only distributed to users who requested it. It is now included in the software distribution for Windows.

For more information about the HDLC Support Library please read the Empack HDLC API application note.

Emflash Program Reports Windows 2000 Plug & Play Problems

The Plug & Play feature of Windows 2000 is confused when the device identification portion of a SCSI enquiry change for a device. This happens for Empacks when the embedded code is updated in the flash memory because the embedded code version is included in the inquiry results.

To avoid this problem in the future, version 3.4.3 and above of the embedded code no longer include the version number in the SCSI inquiry results. However, when updating Empacks from older versions, this problem will occur. The emflash program is modified to detect when the embedded code changes to or from version 3.4.2 or below and it is running on Windows 2000. In such cases it will display a notice to reboot the computer.

The problem occurs the next time an Empack is accessed after the embedded code is updated. It may also occur if the flash update fails and the Empack is left running from it's boot (or OEM) embedded code. The result is an error dialog from Windows 2000 complaining that the device has been unsafely removed. The best way to resolve this situation is to reboot Windows 2000 if emflash suggests doing so.

More information is provided in section 3.4.1 of the application note titled Updating Empack Flash Contents.

New Windows Installer Options

The installer application for Windows now uses "MSI" and provides some additional features and options.

Setup Types

Three installation or setup types are provided which allow some choice as to what files are installed.

The Typical setup type installs the API libraries and DLLs, support programs and diagnostic programs. No source files, demonstration or HDLC support files are included. This selection is intended for most situations.

The Complete setup type installs everything including source files, demonstration programs and HDLC support files.

The Custom setup type allows the user to choose which features are to be installed.

ASPI Support Installation

Some systems running Windows NT4 require ASPI support file and drivers to be installed and some registry keys to be set. Users were previously required to copy files and edit the registry by hand to perform this part of the installation. The new Windows installer will ask the user if this step should be performed when it is installing on Windows NT4. Note, however, that it cannot determine whether or not the system is one for which this is required. It is up to the user to choose whether or not it is to be done.

Windows 2000 does not use the ASPI interface to access SCSI devices. However, the Empack API currently requires the ASPI DLL to be present on the system even though it does not use any ASPI function calls. When installed on Windows 2000 the installer will look for the ASPI DLL (Wnaspi32.dll) in the system32 folder of the system root. If it is not found it will provide the option of copying a version of that file into the system32 folder so that the Empack API can be started. Note that systems with Adaptec's EZ SCSI software installed should already have the ASPI DLL installed the the Empack installer will not ask the user and will not replace the DLL on the system.

Updating Empack Flash

The installer provides an option to run the flash update program, emflash, at the end of the installation procedure. The program will pause when it is finished to allow the user to view any errors or other messages from the program.

If errors should occur, the emflash program should be run after the installer has completed.

New Windows Device Information File

A new version of the device information file, empack.inf, used for Windows 2000, is included in this release. The new file provides a new and unique device GUID which makes it easier to identify CAC and Empack devices in the Windows device manager.