Software Status Bulletin
NGA/RGA NGA/RGA
Known Problem Report as of Aug 24 2026 4:00AM
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:
One-line Description:
NGA/RGA Add-on Software revision 2.7 has wrong characters in Chinese font
Problem:
The characters of Chinese font in NGA/RGA Add-on Software revision is wrong.
Temporary Solution:
None
Fix Information:
This defect is planned to be fixed when the Gas Analyzer 2.7 is run on future OpenLab CDS version.
Keyword:
One-line Description:
Installation of NGA/RGA Add-on Software on to OL 2.5 is not prevented even though it isn't supported and doesn't work.
Problem:
Installation of NGA/RGA Add-on Software on to OpenLab 2.5 is not prevented even though it isn't supported and doesn't work. It is only supported on OpenLab CDS 2.6.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Error happen when use GB/T method using English Operating system
Problem:
The use of GB/T 11062_2020 is limited to Chinese operating systems. When switched to ANSI on an English operating system, the Chinese Compound names are corrupted. On a Chinese operating system, the encoding can be changed to ANSI and the Chinese Compound names will be retained
Temporary Solution:
After installing the NGA / RGA Add-on Software on OpenLab CDS 2.6 on a Chinese operating system, the user has to modify encoding on the Constants file before using the Constants file. Modify the encoding from UTF-8 to ANSI and save. The constants file should work. The special instruction is already provided on the ISO image named as “gbt-note”
Fix Information:
This issue will be fixed in a future revision of OpenLab CDS 2.
Keyword:
One-line Description:
Error happen when process the data with method which has GB_T constant file in NGA/RGA Add-on Software
Problem:
The GB_T_11062_2020_Constant.txt file is UTF-8 encoded. This causes the error. When switched to ANSI on an English operating system, the Chinese Compound names are corrupted. On a Chinese operating system, the encoding can be changed to ANSI and the Chinese Compound names will be retained and the constants file can be used.
Temporary Solution:
After installing the NGA / RGA Add-on Software on OpenLab CDS 2.6 on a Chinese operating system, the user has to modify encoding on the Constants file before using the Constants file. Modify the encoding from UTF-8 to ANSI and save. The constants file should work. The special instruction is already provided on the ISO image named as “gbt-note”
Fix Information:
This issue will be fixed in a future revision of OpenLab CDS 2.