Atomic Absorption Spectroscopy

Installing AA W inLab
Version 3.2

Software Installation Instructions

 Page 2

TABLE OF CONTENTS
Page

1. Update Policy 4

2. Changes Implemented in Version 3.2 4

3. AA WinLab and Computer Resources 4

4. What You Need 4

4.1 Computer Requirements 4

4.11 General Recommendations 4

4.12 Computer Requirements for Windows 95 5

4.13 Computer Requirements for Windows NT 4.0 Service Pack 3 6

4.2 Printers 6

4.3 Firmware Requirements 7

4.4 Configurations Supported in AA WinLab Version 3.2 8

5. Installing a New PC (Windows 95) 8

5.1 Power Management of the PC 8

5.2 Modifying Decimal Point Settings 8

5.3 Checking the Printer Settings 10

5.4 Installing the PCI-Card (Windows 95) 11

5.5 Installing the GPIB Software 11

5.6 Installing the PCI-GPIB Card into the PC 13

5.7 Configure the GPIB Driver 14

5.8 Verifying the GPIB Installation 16

5.9 GPIB Troubleshooting 16

6. Installing a New PC (Windows NT 4.0) 17

6.1 Administrator Rights 17

6.2 Windows NT Service Pack 17

6.3 Power Management of the PC 18

6.4 Modifying the Decimal Point 18

 Page 3

6.5 Changing and Modifying the Printer Settings 18

6.6 Installing the PCI-GPIB Card and Software on a New Computer 20

6.7 Installing the PCI-GPIB card into the PC 20

6.8 Installing the GPIB Software 21

6.9 Configuring the GPIB Driver Settings 24

6.10 Verify the GPIB Installation 26

6.11 GPIB Troubleshooting 27

7. Installing and Configuring AA WinLab Software 28

7.1 AA WinLab and the IntelliMouse 28

7.2 AA WinLab and the IntelliMouse 28

7.3 Installation Procedure 28

7.4 AA WinLab Installation Routine 29

7.5 Modifying the Database Engine Configuration 34

7.6 Multiple Versions of AA WinLab (Windows NT) 35

8. Modifying the Windows Taskbar (Win 95/NT) 36

9. Adding an AA WinLab Icon to the Windows Desktop 38

10. Windows NT Service Pack Re-Installation 39

12. Customizing AS-90X Tray Files 40

13. Upgrading From an Earlier Version of AA WinLab to Version 3.2 42

14. Possible Install/Upgrade Scenarios 43

15. Upgrade from a Previous AA WinLab Version 45

15.1 Conversion of Method and Results Databases Using AA WinLab 45

15.2 Conversion of Method and Results Databases Using Library Manager 45

15.3 Keeping Unit Files 45

16. Appendix 46
 Page 4

Please read the following instructions carefully

before attempting to install AA WinLab version
3.2.
If you have any questions, please contact your
local PerkinElmer representative before
Caution proceeding with the installation.

1. UPDATE POLICY:
• The software is free of charge, however any service costs are not covered by Perkin Elmer.

2. Changes Implemented in Version 3.2

The most significant improvement in version 3.2 versus version 3.0 is the support of the HGA-
850 furnace for the AAnalyst 100/300. Version 3.2 also contains an updated PerkinElmer
Xpress consumables catalog.

In addition a number of bugs have been addressed. A listing is provided in the Appendix.

3. AA WinLab and Computer Resources

When using AA WinLab (or other Windows based program), repeated printing or opening and
closing of a window may result in a slow reduction of computer resources. If the resources
become too low AA WinLab will generate an error and fail to operate. To avoid this problem, it
is strongly recommended that the computer be rebooted at the start of the day.

4. What You Need

4.1 Computer Requirements
4.11 General Recommendations:
 Page 5

• AA WinLab is certified to operate on DELL Pentium II GX1, GXa and GXi

computers (as well as models of DEC computers previously sold by Perkin
Elmer) with a maximum processor speed of 450 MHz (Win 95) or 500 MHz (Win
NT). Faster CPU speeds have not been evaluated as of January 2000 and are
not guaranteed to work properly.

• AA WinLab is not certified to work on brands and models of computers other

than those listed above. Computer brands or models that have historically been
reported to cause problems with AA WinLab include:

Compaq
Hewlett Packard
Gateway
DELL Gn

• We STRONGLY recommend that you upgrade to the recommended PC

configuration rather than the minimum configuration.

4.12 Computer Requirements for Windows 95

Computer: DELL
CPU 486DX, 33 MHz min., Pentium 100 MHz (or
faster) recommended. PII 450 MHz max.
RAM: 8 MB minimum required, 16 MB (or more)
highly recommended
Hard Disk: 200 MB minimum total; 25 MB minimum free
for WinLab applications and data
CD ROM Highly recommended
Disk Drive: 1.44MB, 3.5-inch disk drive
Graphics: VGA color graphics and suitable monitor;
Windows graphics accelerator recommended,
for example, the S3 chip or the Diamond
Stealth accelerator card.
Mouse: Microsoft PS/2, Microsoft serial mouse or
Windows-compatible
 Page 6

4.13 Computer Requirements Windows NT 4.0 with Service Pack 3

Computer: DELL
CPU Intel 166 MHz min., Pentium II, 266 MHz (or
faster) recommended PII 500 MHz max.
RAM: 32 MB minimum, 64 highly recommended
Hard Disk: 1 GB minimum; 30 MB minimum free
for WinLab applications and data
CD ROM Required
Disk Drive: 1.44MB, 3.5-inch disk drive
Graphics: At least SVGA (800 x 600 pixels x 256 colors)
color graphics board and compatible monitor
Mouse: Microsoft PS/2, Microsoft serial mouse or
Windows-compatible

4.2 Printers
For data and peak plot printing, a Windows compatible professional printer is
required. When using a printer with Windows NT 4.0, an NT 4.0 printer driver is
required. Listed below are printers that have been tested and have been found to
work with AA WinLab as well as some that have shown problems:

Successfully Tested Printers Printers That Have Shown Problems

HP DeskJet 870 Cxi HP DeskJet 970Cxi

HP DeskJet 890 Cxi HP LaserJet 5L
HP DeskJet 895 Cxi HP LaserJet 6L
HP DeskJet 692C/694C/695C/880C All GDI printers
HP LaserJet 6P
HP LaserJet 4000/1100

Note: For correct operation of AA WinLab, it is imperative to choose the correct printer
driver for the printer installed. Failure to do so will result in General Protection
Faults

Printer Printer Driver

HP LaserJet 4 Plus or LaserJet 5 HP LaserJet 4 Plus
HP LaserJet 4000 HP LaserJet 4000
HP DeskJet HP DeskJet
560/660/680/690/692/694/695C
HP DeskJet 870/880/890/895 Cxi and Printer Specific Driver
LaserJet 1100
 Page 7

4.3 Firmware Requirements

NOTE: The following firmware must be installed.

Hardware Serial Number Firmware Revision Required

Spectrometer: R or higher
ZL Module w/ AS-70, uncoated furnace
5100 All Version 1.3

ZL Module w/ AS-70, coated furnace

Version 1.4

ZL Module w/ AS-71, uncoated furnace

Version 2.1

ZL Module w/ AS-71, coated furnace

Version 2.2

FIAS-100 1275 or lower 1.1

1276 or higher 2.2

FIAS-200 All 6.1

FIAS-400 4575 or lower 1.1

4576 or higher 2.2

3100 All E or higher

3110 All A or higher

3300 All D or higher

HGA-600 All 10 or higher (10s if equipped with a USS-

100)

AAnalyst 100/300 All Spectrometer 1.1 or higher

HGA-800 1.0 or higher

Gasbox 1.01 or higher

AutoPrep-50 1280 or lower 1.05

1281 or higher 2.23 or higher

AS-93plus ALL 1.61

AS-90plus ALL 1.2

AS-90/AS-90 Controller II 8806 or lower 1.1

8807 or higher 2.2

AS-91/AS-91 Controller II 3085 or lower 1.1

3086 or higher 2.2

 Page 8

4.4 Configurations Supported in AA WinLab Version 3.2

With the increasing number of combinations of spectrometers, accessories, Operating

Systems and IEEE cards, it has become necessary to restrict the number of configurations
that are supported with AA WinLab version 3.2. The table below lists the configurations that
are supported by version 3.2. All other configurations are not supported. This includes
systems utilizing Win 3.1 and 3.11. Compatibilty of AA WinLab version 3.2 with PCIIA
cards has not been determined at this time. It is recommended that the PCIIA card be
replaced with a TNT or PCI card if problems are encountered.

Spectrometer Operating Systems IEEE Cards Supported

Supported
Win 95 Win NT
AAnalyst
100/300 9 9 Windows 95: TNT or PCI
Windows NT: PCI
5100 ZL
9 9 Windows 95: TNT or PCI
Windows NT: PCI
Z/5100
9 Windows 95: TNT or PCI

5100 PC
9 Windows 95: TNT or PCI

3100/3110
9 Windows 95: TNT or PCI

3300
9 Windows 95: TNT or PCI

* NOTE: As PerkinElmer does not offer Windows 98 computers, WinLab version 3.2
has not been evaluated using Windows ’98, however, preliminary evaluation of previous
versions of WinLab have not shown any problems except for the Intellimouse problem
listed in section 7.2.

5. Installing a New PC (Windows 95)

5.1 Power Management of the PC
 Page 9

Switch off any Power Management of the PC.

Please refer to the PC Manual for instructions. Typically the
Power Management must be switched off in the BIOS and
Windows environment.
Using Power Management could result in the loss of data!

Caution
5.2 Modifying Decimal Point Setting
To make sure, that the software handles the data correctly, you must set the decimal point and number formats correctly.
Decimal point: period (.), not comma (,)
Thousand (1000) separator or
Digit Group Symbol: comma (,) or space ( )
Date format: month or day first

To check and change the settings:

• In the Control Panel, double-click on the Regional Settings icon.

• Click on the Number tab.

 Page 10

• Check that the Decimal Symbol is set to a period (.) not a comma (,).

• Check that the Digit Group Symbol is set to a comma (,) or is blank. Do not use a period
(.).

• To check the date format click on the Date tab.

• Check both the Short Date Format and the Long Date Format. Check that the format has
either the day or the month first. You cannot use the format with the year first.

• Click on OK to save the changes.

5.3 Checking the Printer Settings:

 Page 11

• Click on Start in the Windows task bar, then click on Settings.

• Select Settings Î Printers.

• Select Properties from the Printer pull down menu to check the printer configuration (where
applicable) that high speed (rather than for high quality printing) is selected.

• Make sure, that the spooler is activated for printing.

• Close all printer windows.

 Page 12

5.4 Installing the PCI-GPIB Card (Windows 95)

The following diagram outlines the PCI-GPIB card installation for Windows 95:
Prepare GPIB
Driver Disks and the
PCI-GPIB Card

Install the GPIB

Driver Software

Install the
PCI-GPIB Card

Configure the GPIB

Driver

Verify the GPIB

Installation

GPIB
Passes No
Troubleshooting

Yes

Finished

5.5 Installing the GPIB Software

Version 1.30 of the GPIB driver for Windows 95 is included on the AA WinLab CD and is installed when choosing the
selection “Install IEEE for 95.

Complete the following steps to install the GPIB software for Windows 95:
1. Insert the AA WinLab CD into the CD-ROM drive.

2. Usually the AA WinLab Installation Menu comes up automatically. If not, use the
Explorer and double-click on the AUTORUN.EXE file in the \AUTORUN directory
of the CD.
 Page 13

3. Click on Install IEEE for 95. The software installation wizard begins with the
dialog box below. Click on Next.
 Page 14

The setup wizard guides you through the necessary steps to install the GPIB
software. You may go back and change values where appropriate by clicking on
the Back button. You can exit the setup where appropriate by clicking on the
Cancel button.

Only install the diver and applications as shown in the dialog box below:

4. Ignore the disclaimer for non plug&play hardware, as the PCI-GPIB card is fully plug&play
compatible.

5. If there was already a GPIB driver version installed on the PC, it will be detected by the
installation routine. Allow the uninstall procedure to be started to remove the old driver.

6. When the setup is complete, shut down the computer.

5.6 Installing the PCI-GPIB Card into the PC

To install the PCI-GPIB card:
1. Turn off the computer. Keep the computer plugged in so that it remains grounded
while you install the PCI-GPIB board.

2. Remove the top cover and an expansion slot cover on the back panel of the
computer.

3. Insert the PCI-GPIB board into any unused 32-bit PCI slot with the GPIB
connector sticking out of the opening on the back panel. It might be a tight fit, but
do not force the board into place. Make sure that the GPIB plug fits.

4. Screw the mounting bracket of the PCI-GPIB board to the back panel rail of the
computer.
 Page 15

5. Check the installation.

6. Reassemble the top cover of the PC.

7. Turn on the computer and start Windows 95. Windows 95 should automatically
detect the PCI-GPIB hardware and briefly display a New Hardware Found dialog
box

After you have installed your board, you must configure the driver (see next section) and verify the hardware installation. For
verification instructions, refer to section 6.10.

5.7 Configure the GPIB Driver

The GPIB configuration utility is fully integrated with the Windows 95 Device Manager. You can use it to examine or modify
the configuration of the GPIB software. The context-sensitive online help, available by right-clicking on any of the controls
on the configuration utility tabs, includes all of the information that you need to configure the GPIB software properly.
To configure the GPIB software, double-click on the System icon under Start > Settings > Control Panel. In the System
Properties dialog box that appears, select the Device Manager tab, click on the View devices by type button at the top of the
tab, and double-click on the National Instruments GPIB Interfaces icon.
If there is no National Instruments GPIB Interfaces item or if a circled X or exclamation point (!) appears through the eagle
icon, the GPIB interface is not working properly. The first figure below shows an example of an PCI-GPIB card that is
working properly, and the second figure shows an example of an PCI-GPIB card that is not working properly.

1. To configure the interface, double-click on the PCI-GPIB entry immediately below

National Instruments GPIB Interfaces line.
 Page 16

2. Click on the GPIB Settings tab and then click on the Advanced... button.
 Page 17

3 De-activate Automatic Serial Polling.

4. Click on OK to confirm selection.

5. Close the Device Manager.

When you have finished configuring the GPIB software, proceed to the next section, Verify the Installation.

5.8 Verify the GPIB Installation

You can use the Diagnostic utility, installed with your GPIB software, to test the hardware and software installation. The
utility verifies that your hardware and software are functioning properly and that the configuration of your GPIB interfaces
does not conflict with anything else in your system.
To run the utility, select the Diagnostic item under Start > Programs > GPIB Software. When you have started the
Diagnostic utility, test your GPIB interfaces by clicking on the Test All button. If the diagnostic is successful, it puts a check
mark next to the interface and changes its status from untested to passed. If the Diagnostic fails, it puts an X next to the
interface, and changes its status from untested to failed.

You can get details on any tested GPIB interface by selecting the interface and clicking on the Details button.
Troubleshooting information is also available in the online help for the Diagnostic utility, which you can access by clicking on
the Help button.

5.9 GPIB Troubleshooting

The following sections explain common error messages generated by the Diagnostic utility.

Missing Software Components

This error occurs if the software components that are necessary for the GPIB software for Windows 95 to function correctly
are not present in the system. If you encounter this problem, reinstall the GPIB software for Windows 95 and run the
Diagnostic utility again.

No Properly Configured GPIB Interfaces Found

This error occurs if no GPIB interfaces are physically present in the system, if the Device Manager detected problems with
the GPIB interfaces, or if you have not assigned logical board names to your GPIB interfaces using the Device Manager. If
you encounter this problem, use the Device Manager to examine the installed GPIB interfaces, resolve any problems reported
 Page 18

by the Device Manager, and ensure that logical board names are assigned to each interface. Then, run the Diagnostic utility
again.

GPIB Cables Need To Be Disconnected

This error occurs if you have any GPIB cables connected to the GPIB interface. Disconnect all GPIB cables and run the
Diagnostic utility again.

Address Resource Conflict

This error occurs if the address resources assigned to a GPIB interface conflict with the address resources being used by
other devices in the system. Resource conflicts typically occur when your system contains legacy boards that use resources
that have not been reserved properly with the Device Manager. If a resource conflict exists, write down the resource that
caused the conflict and refer to the Microsoft Windows 95 Online Help for instructions on how to use the Device Manager to
reserve I/O resources for legacy boards. After the conflict has been resolved, run the Diagnostic utility again.

Interrupt Resource Conflict

This error occurs if the interrupt resources assigned to a GPIB interface conflict with the interrupt resources being used by
other devices in the system. Resource conflicts typically occur when your system contains legacy boards that use resources
that have not been reserved properly with the Device Manager. If a resource conflict exists, write down the resource that
caused the conflict and refer to the Microsoft Windows 95 Online Help for instructions on how to use the Device Manager to
reserve IRQ resources for legacy boards. After the conflict has been resolved, run the Diagnostic utility again.

GPIB Software Problem Encountered

This error occurs if the Diagnostic utility detects that it is unable to communicate correctly with the GPIB hardware using the
installed GPIB software. If you get this error, shut down your computer, restart it, and run the Diagnostic utility again. If the
problem persists, try reinstalling the GPIB software for Windows 95.

Unknown Problem Encountered

This error occurs if an unknown problem is encountered while trying to execute the Diagnostic utility. If you encounter this
problem, shut down your computer, restart it, and run the Diagnostic utility again. If the problem persists, try reinstalling the
GPIB software for Windows 95.

This completes the PC installation under Windows 95. Skip the section 6 and proceed with section 7.

6. Installing a New PC (Windows NT 4.0)

6.1 Administrator Rights
To install any driver under Windows NT you must log onto your Windows NT system using the
Administrator account. The driver installation program must have Administrator privileges
because the program modifies the configuration registry of your computer.

6.2 Windows NT Service Pack

Verify, that the Windows NT 4.0 Service Pack 3 is installed. If necessary install now.
 Page 19

Make sure, that you install the correct Service Pack. For DELL computers use the
Service Pack provided by DELL (usually in the SPX directory on the hard drive) rather
than the original Microsoft Service Pack.

6.3 Power Management of the PC

Switch off any Power Management of the PC.
Please refer to the PC Manual for instructions.
Typically the Power Management must be
switched off in the BIOS and Windows
environment.
Caution Using Power Management could result in the
loss of data!

6.4 Modifying Decimal Point Setting

To make sure, that the software handles the data correctly, you must set the decimal point and number formats correctly.

Decimal point: period (.), not comma (,)

Thousand (1000) separator or
Digit Group Symbol: comma (,) or space ( )
Date format: month or day first
To check and change the settings:
Follow the instructions in section 5.2. The procedure is identical to that one of
Windows 95.

6.5 Checking and Modifying the Printer Settings

To check and modify the printer settings:
1. Log onto your Windows NT system using the Administrator account.

2. Click on Start in the Windows task bar, then click on Settings.

3. Select Settings Î Printers.

4. Right click on the icon of the printer used to print under AA WinLab, then select
Properties from the Printer pull down menu to check the printer configuration

5. Click on the Scheduling tab. Modify the setting for Priority from 1 to at least 50.
 Page 20

6. Close all printer windows.

 Page 21

6.6 Installing the PCI-GPIB Card and Software on a New Computer

The following diagram outlines the installation of the PCI- GPIB card under Windows NT 4.0:
Prepare Disks and
the PCI-GPIB Card

Install the
PCI-GPIB card

Install the
Software

Configure the Driver

Settings

Verify Installation

Passes No Troubleshooting

Yes

Finished

6.7 Installing the PCI-GPIB card into the PC

To install the PCI-GPIB card:
1. Turn off the computer. Keep the computer plugged in so that it remains grounded
while you install the PCI-GPIB board.

2. Remove the top cover and the expansion slot cover on the back panel of the
computer.

3. Insert the PCI-GPIB board into any unused 32-bit PCI slot with the GPIB
connector sticking out of the opening on the back panel. It might be a tight fit, but
do not force the board into place. Make sure that the GPIB plug fits.

4. Screw the mounting bracket of the PCI-GPIB board to the back panel rail of the
computer.

5. Check the installation.

6. Reassemble the top cover of the PC.

 Page 22

After you have installed your board, you must install and configure the driver (see next sections) and verify the hardware
installation. For verification instructions, refer to section 6.10.

6.8 Installing the GPIB Software

Version 1.40 of the GPIB driver for Windows NT 4.0 is included on the AA WinLab CD and is
installed when choosing the selection “Install IEEE for NT”.

1. Power on the computer and log onto your Windows NT system using the
Administrator account. The GPIB installation program must have Administrator
privileges because the program modifies the configuration registry of your
computer.

2. Insert the AA WinLab CD into the CD-ROM drive.

3. Usually the AA WinLab Installation Menu comes up automatically. If not, use the
Explorer and double-click on the AUTORUN.EXE file in the \AUTORUN directory
of the CD.

4. Click on Install IEEE for NT. The software installation wizard begins with the
below. Click on Next.
 Page 23

In some Windows NT installations the file

CTL3D32.DLL is missing in the
\winnt\system32 directory. In this case the
GPIB software installation will start with an
Caution error message. Install the missing file from the
Windows NT installation CD.

5. The software installation wizard begins with the dialog box below.

The setup wizard guides you through the necessary steps to install the GPIB
software. You may go back and change values where appropriate by clicking on
the Back button. You can exit the setup where appropriate by clicking on the
Cancel button. You can use the default values for Destination Directory,
Only install the driver and applications as shown in the dialog box below:
 Page 24

If there was already a GPIB driver version installed on the PC, it will be detected
by the installation routine. Allow the uninstall procedure to be started to remove
the old driver.

Do not install the ISA Plug&Play support.

7. When the setup program has finished copying the software onto your computer,
it attempts to start the GPIB driver. If the setup program cannot start the driver, it
instructs you to run the GPIB Configuration utility in order to check your system
configuration and then to reload the GPIB driver. Sometimes it is necessary to
restart the PC.
 Page 25

If you click on the Configure button the GPIB configuration utility starts
automatically and there is no need start the utility from the Control Panel.

6.9 Configuring the GPIB Driver Settings

You must run the GPIB Configuration utility before you can use the GPIB software for
Windows NT. Follow these steps to run the utility:
1. If not already in the configuration utility, select Start»Settings»Control Panel.

2. Double-click on the GPIB icon in the Control Panel. The following window
appears.

The GPIB Configuration utility displays a list of all the GPIB boards and device
names.

3. Use the Board Type button to specify the type of GPIB.

 Page 26

4. Highlight the PCI-GPIB line and click on OK.

5. Click on the Configure button, then following windows appears:

6. After clicking on the Software button the next windows appears:

 Page 27

7. Remove the check mark from the Enable Auto Polling check box (disable serial
polling).

8. Click on the OK button to save your changes.

9. Windows NT prompts to reload the GPIB driver with the modified settings. Click
on Yes to enable the changes made.

After you have installed and configured the software, you should verify the installation. Continue to the next chapter.

6.10 Verifying the GPIB Installation

You can use the Diagnostic utility, installed with your GPIB software, to test the hardware and
software installation. The utility verifies that your hardware and software are functioning properly
and that the configuration of your GPIB interfaces does not conflict with anything else in your
system.
To run the utility, disconnect the IEEE cables from the back of the computer and select the
Diagnostic item under Start > Programs > NI-488.2M Software for Windows NT. When you have
started the Diagnostic utility, test your GPIB interface by clicking on the Test All button. If the
diagnostic is successful, it puts a check mark next to the interface and changes its status from
untested to passed. If the Diagnostic fails, it puts an X next to the interface, and changes its status
from untested to failed.

You can get details on any tested GPIB interface by selecting the interface and clicking on the Details button.
Troubleshooting information is also available in the online help for the Diagnostic utility, which you can access by clicking on
the Help button.
 Page 28

6.11 GPIB Troubleshooting

Missing Software Components
This error occurs if the software components that are necessary for the GPIB Software for Windows NT to function correctly
are not present in the system. If you encounter this problem, reinstall the GPIB Software for Windows NT and run the
Diagnostic utility again.

No GPIB Interfaces Present

This error occurs if there are no GPIB interfaces physically present in the system or there is a resource conflict with the
interfaces that are installed. If you encounter this problem, use the GPIB Configuration utility to examine the installed GPIB
interfaces and the resources assigned to each. Then, run the Diagnostic utility again. To access this information in the GPIB
Configuration utility, complete the following steps:
1. Start»Settings»Control Panel.

2. Click on the Board Type button and verify that the type of GPIB interface listed is
correct. Click on the OK button to return to the main dialog box.

3. Double-click on the board name and verify that the hardware settings displayed
in the dialog box match your actual hardware settings.

GPIB Cables Need To Be Disconnected

This error occurs if you have any GPIB cables connected to the GPIB interface. Disconnect all GPIB cables and run the
Diagnostic utility again.

Address Resource Conflict

This error occurs if the address resources assigned to a GPIB interface conflict with the address resources that other devices
in the system are using.

To resolve an address resource conflict, refer to the Resolving Resource Conflicts section, later in this appendix. After you
have resolved the conflict, run the Diagnostic utility again.

Interrupt Resource Conflict

This error occurs if the interrupt resources assigned to a GPIB interface conflict with the interrupt resources that other devices
in the system are using. To resolve an interrupt resource conflict, refer to the Resolving Resource Conflicts, later in this
section. After you have resolved the conflict, run the Diagnostic utility again.

GPIB Software Problem Encountered

This error occurs if the Diagnostic utility detects that it is unable to communicate correctly with the GPIB hardware using the
installed GPIB software. If you encounter this error, shut down your computer, restart it, and run the Diagnostic utility again.
If the problem persists, try reinstalling the GPIB software for Windows NT.

Unknown Problem Encountered

This error occurs if an unknown problem is encountered when you try to execute the Diagnostic utility. If this error occurs,
shut down your computer, restart it, and run the Diagnostic utility again. If the problem persists, try reinstalling the GPIB
software for Windows NT.

Resolving Resource Conflicts

Resource conflicts occur when your system contains hardware that is configured to use the same resources as your GPIB
interface. The NI-488.2M driver detects some resource conflicts when it loads. When the driver detects conflicts as it loads, it
records an error message describing the conflict. You can use the Event Viewer, to see which resource is in conflict. Once you
have identified the resource that caused the conflict, use the GPIB Configuration utility to reconfigure your GPIB interface so
that it uses conflict-free resources. To help in the selection of conflict-free resources, Microsoft has provided a utility called
Windows NT Diagnostics. This utility displays a list of the I/O port addresses, interrupt levels, and DMA channels that are
 Page 29

currently being used in your system. Assign resources this utility does not list to your GPIB interface. Follow these
instructions to run the Windows NT Diagnostics:
Select Start»Programs»Administrative Tools»Windows NT Diagnostics.

7. Installing and Configuring AA WinLab Software

7.1 Before you Install AA WinLab

• Make sure, that you have a printer driver installed even if you do not have a printer
attached to the computer.
• If updating from a previous version, the software will not overwrite the \AAUSER
directory, therefore, all methods and results data will not be lost. However, all *.UNT
files in the \AAWINLAB directory will be deleted and replaced by default files. If custom
units have been previously created (e.g. meq/L), backup the *.UNT files prior to
installation of version 3.2 and then recopy the *.unt files into the \AAWINLAB directory
after installation

7.2 AA WinLab and IntelliMouse

AA WinLab does not support the IntelliMouse (and its IntelliPoint Driver). Some of the known
problems with AA WinLab and the IntelliMouse include:

1) A fatal error when installing AA WinLab using Windows 98 (occurs after selecting the
instrument hardware and clicking on the NEXT button). This is a conflict with the Install
Shield from Sterling that is used to install AA WinLab.
2) Loss of AA and BG bar graph colors in Align Lamps.

If AA WinLab is to be installed on a computer with an IntelliMouse, the IntelliPoint driver

should first be deleted (use Start»Settings»Control Panel»Add/Remove Programs) and the
mouse should be reinstalled as a standard mouse.

Note: Some computers (including DELL computers shipped from the US) have the
IntelliPoint driver installed even though a standard mouse is shipped with the
computer. It is recommended that the IntelliPoint driver be deleted.

7.3 Installation Procedure

During the installation, to close one dialog box and go to the next, either click on Next > or
press [ENTER].
To stop the installation at any time click on Cancel.
If you want to use the keyboard rather than the mouse, press the key that corresponds to the
underlined character on the command button in the dialog box.

1. Start Windows (if using Windows NT, you must log in as Administrator in order to
be able to install AA WinLab).
 Page 30

2. After the Windows initialization has been completed, insert the AA WinLab
Compact Disk in the CD-ROM drive of the PC and close the drive. Typical drive
character is D, the following instructions assume this.

3. Usually the AA WinLab Installation Menu comes up automatically. If not, use the
Explorer and double-click on the AUTORUN.EXE file in the \AUTORUN directory
of the CD.

4. Click on Install AA WinLab. Follow the instructions on the screen and the
instructions given in section 7.3.

7.3 AA WinLab Installation Routine

The first dialog box that appears during the AA WinLab installation program is shown below.
Normally all components of the software are installed (by default). Options are de-
selected by clicking on the corresponding check box.

In this dialog box, you also may specify the directory where the installation routine
copies the files. The default destination is the boot drive of the PC (typically C:) and
\AAWINLAB for the program path.

NOTE: If you intend to install more than one AA WinLab package on the PC (e.g. AA
WinLab for an AAnalyst 300 and AA WinLab for the FIMS), you must specify a
"parent" directory for the software package as shown in the dialog box below. In
this example, the parent directory is C:\AANALYST. You may also select a hard
disk drive (if for example, you wish to install AA WinLab on a “D” drive instead of
the default “C:” drive). . Do not use Long File Names > 8 characters! Close the
dialog box by clicking on OK.
 Page 31

2. Click on Next >.

If the specified directory does not exist, the following dialog box is displayed:

3. Click on Yes to create the directory.

In the next dialog box you may specify the directory which the installation routine is
assigning for the user files. The default destination is the boot drive of the PC (typically C:)
and the \AAUSER directory. If you intend to install more than one AA WinLab package on
the PC (e.g. AA WinLab for an AAnalyst 300 and AA WinLab for the AAnalyst
600/700/800), you must specify a "parent" directory for the user files. You may also select
a hard disk drive (if for example, you wish to install AA WinLab on a “D” drive instead of the
default “C:” drive). . Do not use Long File Names! Close the dialog box by clicking on OK
>.
 Page 32

NOTE: If the directory does not exist, it will be created—see steps 2-3 above.

4. Specify your spectrometer and whether or not a background corrector is installed by

clicking on the radio button in the next dialog box. Close the dialog box by clicking on
Next >.
 Page 33

5. If you are operating additional accessories, you must specify your accessories by clicking
on the corresponding radio button in the next dialog box.

6. Specify your paper size for printouts with the AA WinLab Quick Reporter utility by
clicking on the corresponding radio button. Close the dialog box by clicking on Next >.

7. Answer the next message box with Yes.

If the installation program detects a previous version of AA WinLab in the selected

directory, the following dialog box is displayed:
 Page 34

Click on Yes to allow the installation program to delete the old revision prior of
the installation of the new revision.

8. The content of the installation compact disk will be decompressed and copied onto the
hard disk.

9. When this section of the installation is finished, a dialog box allows you to view the
README file.

To see the most recent information about AA WinLab click on the check box. This is
highly recommended. Close the AA WinLab installation program by clicking on Finish.

10. Then the second part of the installation appears.

 Page 35

The IDAPI files are provided by BORLAND and ensure proper access to the
various databases used to store methods and results. You must answer with
Yes, if you are installing the AA WinLab software for the first time.

Accept the default path for IDAPI files installation or specify your own and click on
Continue. Later on you must change the IDAPI configuration as described in
section 7.5.

11. The installation is now complete. To activate the several changes made to the
Windows configuration you must exit Windows and reboot your PC.

7.5 Modifying the Database Engine Configuration

After completing the IDAPI installation you must set the IDAPI parameters of the database engine. Use the procedure
described below to make sure that the IDAPI Parameters are correct:
1. In the Explorer, open the directory (default: C:\IDAPI) where the IDAPI files are
installed.

2. Double click on BDECFG.EXE. The BDE configuration utility window appears.

3. In the Driver Name listbox click on PARADOX

4. Check the NET DIR parameter.

For a standard not-networked AA WinLab environment:

The entry for the NET DIR parameter should be c:\ . If this is not the
case, type c:\ in the entry field.

If you are using a network:

You must have the network connected or WinLab will not function.
In order to put the results and/or methods database on the network in a
multi-user environment, you must do the following:
The NET DIR must point to the same location for all users on the
database, for example: N:\aausers. This will also be the location for the
network control file called "pdoxusrs.net."
Make sure that you have full access (read and write access) to the
network directory and the directories where the databases reside.

5. Click on the System tab at the bottom of the screen. The following window
appears:
 Page 36

5. In the MINBUFSIZE entry field type 128.

6. In the MAXBUFSIZE entry field type 256.

7. In the MAXFILEHANDLES entry field type 20.

8. Click on Save in the File pull down menu to save the changes

9. Close the BDE configuration utility window.

7.6 Multiple Versions of AA WinLab (Windows NT)

If you are installing multiple versions of AA WinLab on a Windows NT system you must make
sure, that each version is using its own memory space. This is necessary to prevent Windows
NT from caching different (and most likely incompatible) versions of a file (e.g. *.DLL file).

1. On the Taskbar click on Start, then select Settings -> Taskbar.

2. Click on the Start Menu Programs tab, then click on Advanced.

3. Double-click on the Profiles – All Users – Start Menu – Programs folder on the
left side of the Explorer window.

4. Click with the right mouse button on the AA WinLab Analyst entry.

5. Select Properties from the context menu coming up, then click on the Shortcut
tab.

6. Activate the check box Run in Separate Memory Space, then click on Apply
followed by a click on Close.
 Page 37

7. Repeat steps 4 to 6 for the following entries: AA WinLab Library Manager, AA

WinLab Quick Reporter, AA WinLab Reformat, Reconfigure

8. Close the Explorer window.

7. In the Taskbar Properties window click on OK.

8. Modifying the Windows Taskbar (Win 95/NT)

We recommend that you add AA WinLab to the main section of the Windows taskbar. This way, you can always get to the
program easily by just clicking on the Start button. For Windows NT you must have Administrator privileges.
To add AA WinLab icons to the main Windows taskbar:
All the WinLab icons (AA WinLab, Reporter, Reformat, and Library Manager) require
specific “target” properties, so you will need to copy the icon to the taskbar as follows:

1. Click on the Start button on the Windows desktop.

9. Select: Settings Taskbar.

10. Click on the Start Menu Programs tab.

 Page 38

11. Click on Advanced.

12. Windows 95: Double-click on the Programs folder on the left side of the window
to see the programs available.
Windows NT 4.0:
Double-click on the Profiles – All Users – Start Menu – Programs folder on the
left side of the window to see the programs available.

13. Then double-click on the AAnalyst X00 folder.

14. Click on the AA WinLab Analyst icon on the right side of the window.

15. Drag the AA WinLab Analyst icon to directly over the Start button in the left hand
lower corner of the screen, then release the mouse button.

16. The AA WinLab Analyst line has been added to the Start menu. Click on the
Start button to check.
 Page 39

9. Adding an AA WinLab Icon to the Windows Desktop

If you would like to have the AA WinLab Analyst icon or the entire AAnalyst X00 folder as
shortcut on the desktop, follow the instructions below: For Windows NT you must have
Administrator privileges.
1. Follow steps 1 through 5 of instructions in 8

2. To install the AAnalyst X00 folder icon as a shortcut:

a. Click with the right mouse button on the AAnalyst X00 folder icon on the
left side of the window and hold down the button.

b. Drag the AAnalyst X00 folder icon over the Desktop, then release the
right mouse button.
c. In the pop-up menu select Create Shortcut(s) Here
d. The AAnalyst X00 folder icon shortcut has been added to the Desktop.

3. To install the AA WinLab Analyst icon as a shortcut:

a. Double-click on the AAnalyst X00 folder.

 Page 40

b. Click with the right mouse button on the AA WinLab Analyst icon on the
right side of the window and hold down the button.

c. Drag the AA WinLab Analyst icon over the DESKTOP, then release the
right mouse button.
d. In the pop-up menu select Create Shortcut(s) Here
e. The AA WinLab Analyst icon shortcut has been added to the Desktop.

10. Windows NT Service Pack Re-Installation

After installing AA WinLab software it is typically not necessary to re-install Windows NT 4.0
Service Pack 3. If you must reinstall the Service Pack make sure, that you install the
correct Service Pack. For DELL computers use the Service Pack provided by DELL
(usually in the SPx directory on the hard drive) rather than the Dell CD or the original
Microsoft Service Pack.
 Page 41

11. Customizing AS-90x Tray Files

With AA WinLab version 3.0 or 3.2 it is possible to define custom autosampler tray files for
use with the AS-90/90plus/91 and 93 plus. To create a custom tray file,

1. Open one of the existing *.tra files in the \aawinlab directory. If you are using an AS-90 or
90plus open a file beginning with AS90. If you are using an AS-91 or AS-93, open a file
beginning with AS91 or AS93 respectively.

Note: In AA WinLab 3.0 or 3.2, the trays (and associated *.tra files) have been renamed to
include the number of locations and the autosampler on which the tray is used as is
shown in the table below:

Old Tray Name New Tray File Name

TrayA AS90A152
TrayB AS90B106
TrayC AS90C44
TrayE AS91E199
TrayF AS91F160
TrayG AS91G63

2. Set the MaxLocations at the top of the file to the maximum number of locations in the
custom tray.
 Page 42

3. Modify the X and Y values (in mm) for the new tray. The range of X,Y and Z values for
each size tray is listed at the top of the existing *.tra file.
4. Use Save As to save the modified *.tra file (using a new name) in the \aawinlab directory
that contains the other tray files.
5. In WinLab version 3.2, custom tray files may be selected from the drop down menu in the
Method Editor.
 Page 43

Note:AA WinLab uses the first 4 letters in the *.tra file in a convention to determine which tray
files should be displayed in the drop down menu with each configured autosampler. If an
AS-91 is configured, tray files that begin with “AS91” will appear in the menu. Tray files
beginning with “AS90” will appear when an AS-90 or AS-90plus is configured. When
any other name (such as custom.tra as shown above) is used, the tray will appear in the
drop down menu regardless of the autosampler configured. This is normally not a
problem as most AA WinLab users do not have both an AS-90 or AS-90plus AND an AS-
91 (or AS-93).

12. Upgrading From an Earlier Version of AA WinLab to

Version 3.2
Previous versions of AA WinLab for the AAnalyst
100/300 etc. (version 2.61 or earlier ) installed a
16-bit IEEE driver. If you are upgrading from an
older version of WinLab on a Win 95 system and
are using a TNT card, do not click on the Install
IEEE for 95 button in the AutoRun menu as this
Caution will install a 32-bit IEEE driver (version 1.3) and
you will have to reconfigure the driver software
base I/O and ensure that there are no conflicts.
 Page 44

13. Possible Install/Upgrade Scenarios

Listed below are some of the scenarios under which AA WinLab version 3.2 could be installed
as an upgrade on a computer as well as a brief listing of the steps required to complete the
upgrade.

Scenario A: Update from Version 3.0 (or earlier) to 3.2 on a Win 95 computer that has
currently installed 16-bit IEEE driver

Procedure using AutoRun on CD ROM:

1) Review install instructions

2) Install WinLab (see section 7)

It is not necessary to reinstall the 16-bit IEEE driver. Do not click on Install IEEE
for 95 as this will install a 32-bit driver which must then be configured correctly.

Procedure using floppy disks:

1) Install WinLab

It is not necessary to install the 16-bit IEEE drivers again. Do not install the IEEE
driver from the floppy disks as this is a 32-bit driver which must then be
reconfigured.
 Page 45

Scenario B: Install AA WinLab version 3.2 on a Win 95 computer that has no currently
installed 16-bit IEEE driver (eg. new or reformatted HD)

Option 1

1) Reinstall WinLab version 2.61 (the 16-bit driver IEEE driver will be installed)
2) Follow Scenario A above

This is the easiest option as it will result in version 3.2 installed with the 16-bit drivers
and it will be necessary to reconfigure the driver configuration for the Base I/O.

Option 2

Procedure using AutoRun on CD ROM

1) View Install instructions

2) Install IEEE driver for Win 95 and configure driver software for Base I/O
3) Install WinLab/Borland
4) Configure Borland

This will result in the 32-bit driver being installed.

Scenario C: Upgrade from AA WinLab version 3.0 (or earlier) to version 3.2 on a
computer using Win 3.1 or 3.11.

1) Upgrade to Win 95 or 98
2) Follow Scenario A above
 Page 46

14. Upgrading from a Previous AA WinLab Version

If you are installing an upgrade in the same directories as the old AA WinLab software, the
system will delete all files from the \AAWINLAB directory prior to installing the new files, but
will not delete any files from the \AAUSER directory. Thus you will be still able to use (after
conversion, see below) your existing methods, results, sample information files and other data
with the new version.

14.1 Conversion of Method and Results Databases using AA WinLab

In AA WinLab version 3.0 some changes were made to the method and results
databases.

If version 3.2 is installed into an existing \aauser directory created with version 2.61 or
earlier, when WinLab is started a dialog will come up indicating that the method and
results databases need to be converted as is shown below.

Click on OK to convert the databases.

Also, whenever the user uses “Browse” to pick a new method or result library, the same
check is done.

14.2 Converting Method and Results Databases using Library Manger

Library Manager included with AA WinLab version 3.2 can also be used to convert old
method and results databases (created with version 2.61 or earlier). To convert these
databases:
 Page 47

1) Start Library Manager

2) Select the Methods Library Category and \aauser directory Library Location

3) The Library Manager will show an error message "Library is out of date”.

4) Convert the database using the Convert command from the File pull down menu.

5) Use the same technqiue to convert the Results library.

14.3 Keeping Unit Files:

AA WinLab stores information about weight/volume and weight/weight units and the relevant
conversion factors in the *.UNT ASCII files in the \AAWINLAB directory. If you have
customized versions of the *.UNT ASCII files from your previous version, make backup copies
in a different directory so that the system does not overwrite them with the new versions. After
installation of the new version, copy the customized versions of the *.UNT ASCII files into the
new \AAWINLAB directory and continue using them with the new version of AA WinLab.

15. Appendix
The following bugs present in version 3.0 have been addressed in version 3.2:

• Communication problems on the 3100 with fast (>400 MHz) computers have been fixed.
• A communication problem when interrupting the FIAS during an autosampler wash has
been fixed.
• The “Print Log” setting is now remembered between instances of WinLab; so if the user
turns it on, it stays on until he turns it off, and vice-versa.
• In the Recall Calibration function, only the calibrations which correspond to the element in
the selected method are now listed.
• The installation will remove the NIVGPIB driver from the SYSTEM.INI file. This was added
by older versions of WinLab, and could result in an error at system reboot time.
• The text prompts on the Align Autosampler dialog for the AS-800 have been modified to be
clearer.
• When the Library Manager copies methods from an “old” database (from version 2.61 and
before) to a “new” database (from version 3.0 and after), the method would be copied
incorrectly in some cases depending on whether the source method index already existed
in the target database. This is now fixed.
• When an automated analysis was cancelled and resumed, and the Continue dialog was
exited with the CANCEL button, the analysis was reset to the beginning and could not be
continued again. This is now fixed.
• Two new methods have been added to the “Service Methods” database for use with the
HGA-850.
 Page 48

• An “HGA-850 Manual” icon is now added to the program group, if the installed furnace is
the HGA-850. This icon will display the HGA-850 hardware manual using Acrobat, if
Acrobat is installed on the computer.
• Extra blank lines in the QC method printout have been eliminated.
• The results dataset name can no longer appear in the results printout if data storage is
turned off.
• Some incorrect coordinates for locations 21-41 in AS-93plus Tray G have been fixed.
• The correct diluent and modifier locations are now always used while pipetting additions.
• The “E” tray file for the AS-91 was incorrect and would not allow samples higher than 199.