Software Status Bulletin

UV VIS ChemStation     G1117AA

Preface
-------------------------
This Software Status Bulletin (SSB) documents all known problems in the software
product designated above. The SSB is derived from Known Problem Reports (KPR)
which result from user problems that have been classified as documentation
problems or software defects. When a KPR is written, an identifying number is
assigned to it, and the KPR is added to the next edition of the SSB.

User inputs that have been classified as Enhancement Requests are not documented
in the SSB. User problems that have been submitted, but that have not been
classified by the time the SSB is generated are not included in the SSB.

How to use the SSB
-------------------------
When you experience a problem with a product, first check this SSB to see if the
problem has been reported already, and if there is a temporary workaround
available for the problem, or if the problem has already been fixed by a new
revision. If the problem is not listed in this SSB then you may wish to report
it to the Response Center or to your field support representative.

To determine if your problem is documented in this SSB, first look in the
Keyword Index section of the SSB. Under each keyword is a listing of one-line
descriptions of related KPRs. If any of these sound like yours, locate the KPR
# in the Known Problem Reports section of the SSB, and read the full KPR. The
KPRs in the Known Problem Reports section are sorted by KPR #.

There are two sections in the SSB:
Keyword Index: This index is categorized by keyword. For each KPR there is a
brief description and a KPR #. A KPR may be associated with more than one
keyword.

Known Problem Reports: This section contains KPRs, with all the available
information relevant to the problem. KPRs in this section are sorted by KPR #.

Keyword Glossary

Keyword Index

Keyword: Data Acquisition

KPR#:25 GPF during kinetics run on Windows 2000 SP2
KPR#:155 Kinetic measurement stops early
KPR#:190 Initial delay time causes cycle times to be different from the method settings
KPR#:703 Wrong information and hint

Keyword: Data Analysis

KPR#:90 Data processing speed too slow
KPR#:189 Correct unit multiplication factor is not displayed in the Result Window
KPR#:261 The rate recalculation is not performed correctly in Kinetics mode.

Keyword: Graphics/Views

KPR#:84 It is not possible to set the y-axis for the Time Trace window.

Keyword: Import/Export

KPR#:69 Data storage space on disk by far too large

Keyword: Load/Save

KPR#:63 Data storage space for time based measurements is too high.

Keyword: Measure

KPR#:79 Error "Invalid Data Points" in a kinetics measurement using a MCT

Keyword: Method

KPR#:111 Setting the Individual Calculation Range results in an error message.
KPR#:238 Irreproducible timing in kinetics runs
KPR#:262 Missing data in a kinetic measurement.

Keyword: 

One-line Description:

Raw data buffer overflow

Problem:

A raw data buffer overflow occurs when acquiring data at high rates. The bug seems to be computer system dependent. Using a Vectra VL 5/90 and a Vectra 486/66 XM this bug did not appear.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Measurement buttons on HP8453 cannot be used to start kinetics run

Problem:

The measurement buttons on the HP8453 are used for single measurements only in kinetics mode. In time-based acquisition task all buttons are deactivated.

Temporary Solution:

Use external trigger line to start acquisition.

Fix Information:

Fix under investigation

Keyword: 

One-line Description:

Minimum achievable cycle time does not meet customer exspectations

Problem:

The minimum cycle time for kinetics is in case of a blank and three samples nearly three times the cycle time which could be achieved using the Ms-DOS software 89532K. This is not accepted by some customers.

Temporary Solution:

None

Fix Information:

Fix under investigation

Keyword: 

One-line Description:

Loading of Kinetics Data file fails if not in the default data directory

Problem:

When trying to load a kinetics data file from a directory other than the configured, a red error message line "No valid file" is displayed.

Temporary Solution:

n/a

Fix Information:

Fixed in code B.04.02

Keyword: 

One-line Description:

Data/results file name not printed with the report

Problem:

When printing kinetics results data the file name does not appear on the report.

Temporary Solution:

n/a

Fix Information:

Defect no longer reproducable in B.04.02

Keyword: Data Acquisition

One-line Description:

GPF during kinetics run on Windows 2000 SP2

Problem:

On systems running Windows 2000 SP2 certain kinetic runs might
abort with a General Protection Fault (GPF) in module KRNL.exe at 0001:6382.
In particular this GPF occurs during long multicell kinetic runs on
low end PCs (e.g. PIII 450 MHz, 64MB).

Temporary Solution:

In order to avoid this problem on Windows 2000 SP2 the following temporary solution is available:

1. Start the regedit and remove/rename the following entry:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatibility\ntvdm

2. Reboot the machine in order to make the above setting effective

Fix Information:

Fix under investigation.

Keyword: Data Acquisition

One-line Description:

Kinetic measurement stops early

Problem:

If a start time is defined for a kinetic method, the kinetic run stops early.
For example if a start time of 15s and a total run time of 120s is defined
in the method, the kinetic run will stop already after 105s.

Temporary Solution:

Increase the run time by the start time in order to achieve the correct
time management.

Fix Information:

Fix under investigation.

Keyword: Data Acquisition

One-line Description:

Initial delay time causes cycle times to be different from the method settings

Problem:

The communication between the PC and the 8453 causes an initial
delay time. Hence the first measuremnt is not exactly at t=0 and the
following measurements could also be slightly shifted. However the
kinetic traces are correct, as the time table contains the exact times,
when the measurement has been performed.

Temporary Solution:

n/a

Fix Information:

No fix planned.

Keyword: Data Acquisition

One-line Description:

Wrong information and hint

Problem:

After saving the kinetics result data to ECM and starting a new acquisition, get a message box "Data have not been saved ...". However, the data had been successfully transferred to ECM.

Temporary Solution:

n/a

Fix Information:

Only Kinetics mode: After saving the result to ECM the method changed flag become set. As the method changed flag is used for the result changed flag (only in case a result was saved or loaded) the result seems to be changed. Problem fixed

Keyword: Data Analysis

One-line Description:

Data processing speed too slow

Problem:

The processing speed of a 486/66 processor is too slow to display data in real time. The monitor is several seconds behind the acquisition. Processing of data takes more time than acquiring data.

Temporary Solution:

None

Fix Information:

No fix planned.

Keyword: Data Analysis

One-line Description:

Correct unit multiplication factor is not displayed in the Result Window

Problem:

The factor for the unit conversion in the kinetics mode is displayed in the Results window. If this factor is changed in the Time & Calculation dialog box after the time based measurement, the corrected rate is calculated and displayed in the  Results window. However, the new factor is not displayed in the Results window.

Temporary Solution:

Change the factor in the Result window table and not in the Time & Calculation dialog box.

Fix Information:

Fix planned

Keyword: Data Analysis

One-line Description:

The rate recalculation is not performed correctly in Kinetics mode.

Problem:

If a single cell data file is loaded when a multicell transport is configured, the rate calculation is performed automatically and the data is inserted in the corresponding table. Now, after choosing the 'Time & Calculation Setup' dialog box and leaving it without making any changes, the Results Table shows invalid data indicated by ***.

Temporary Solution:

Make any change in the "Time and Calculation Setup" dialog box or leave it with Cancel.

Fix Information:

No fix planned.

Keyword: Graphics/Views

One-line Description:

It is not possible to set the y-axis for the Time Trace window.

Problem:

It is not possible to set the y-axis for the Time Trace window to a fixed value.

Temporary Solution:

If the Advanced Mode G1116A is installed following command can be used to generate a graphic window with a fixed x- and y-axis: draw 1,tracedata,:,: For ,,,and  appropriate values have to be entered.
In the user contributed library's macro contributions a solution is avaialble as #8. This library is available on the product CD-ROM.

Fix Information:

Fix planned.

Keyword: Import/Export

One-line Description:

Data storage space on disk by far too large

Problem:

Even if the acquisition range is reduce to the required data only the space used by the raw data on disk is enormous. This is especially worse in kinetics were a lot of data are required, but header information must not be duplicated for each data set.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Load/Save

One-line Description:

Data storage space for time based measurements is too high.

Problem:

The space on disc required to store kinetics data is too high. Acquiring kinetics data in a run of about 1000 measurements using a Wavelength Range of 544 to 548nm, a Interval of 1nm, a Cycle Time of 0.1s, and a Run Time of 100s needs about 2.1 MBytes of storage space on the harddrive.

Temporary Solution:

n/a

Fix Information:

Fix under investigation.

Keyword: Measure

One-line Description:

Error "Invalid Data Points" in a kinetics measurement using a MCT

Problem:

Using a MCT sampling system for a kinetics measurement leads to the error message "invalid data points in spectrum", if at least one cell position which passes the light beam during the measurement cycle is empty and if the shutter stays open during the whole measurement cycle (chosen cycle time close to the minimum cycle time). The error message in generated, because the measured light intensity at the empty cell position is higher than the transmitted intensity with the blank medium in the light path. This leads to negative absorbance readings. However, the error message can be ignored, because it has no impact on the measured samples and the calculated results.

Temporary Solution:

Avoid empty cells ("NotUsed") between the cells used for blank and sample measurements or choose a cycle time, which allows the shutter to close during a measurement cycle.

Fix Information:

Fix planned.

Keyword: Method

One-line Description:

Setting the Individual Calculation Range results in an error message.

Problem:

After selecting 'Set Individual Calculation Range' from the Method menu, the red error message line "EDTAB 117: Missing SOURCE value in row 1 of DDT _CONFIG[3].ResultTable!" appears for a short time, regardless of whether the temperature is changed or not. The appearance of this error message has no influence on the subsequent calculation.

Temporary Solution:

None

Fix Information:

Fix planned.

Keyword: Method

One-line Description:

Irreproducible timing in kinetics runs

Problem:

When executing a kinetics run using a single method on a single system different time scales can appear for the acquired data. Also the number of data points expected from the timing parameters is not acquired. In addition the number of data points varies from run to run.

Temporary Solution:

None

Fix Information:

No fix planned.

Keyword: Method

One-line Description:

Missing data in a kinetic measurement.

Problem:

During time-based acquisition, data are not acquired according to the set total run time because the measurement starts after a certain delay time. This causes a loss of data at the end of the acquisition. Example: If a kinetic measurement with a run time of 60 seconds, a start time of 0 seconds, and a cycle time of 10 seconds is performed, the measurement does not start at 0 seconds as expected, but after a certain delay time of about 1.5 seconds. Because the Run stops at 60 seconds, the last data point will be measured at 51.5 seconds. As a result only 6 data points will be acquired instead of 7 data points as expected.

Temporary Solution:

Set the Run Time to a higher value that takes the delay time of your instrument into account.

Fix Information:

No fix planned.