Empower Software Release Notes Appendix Changes Implemented through Service Packs

Empower Software Release Notes Appendix Changes Implemented through Service Packs Problems Fixed with Empower Service Pack A PCS #: 28564 In certain circumstances, the Server is unable to access data files that have been buffered and the message, unable to write to the server error is returned. The data files are transferred to the server after the buffering but do not add to the total number of files in the appropriate raw data drive. The Empower message center displays data file checksum errors for data files. Any of the data files that showed in the raw data drive of the server but did not add to the total item count were not accessible anymore through the Empower application. The normal recovery procedure of running instrvx, to force buffered files to the server, does not correct the problem in this case. Service Pack A does not address this issue with the Waters ZQ running in Workgroup or Enterprise (client server) configurations. This will be addressed in a separate Service Pack. PCS #: 28317 When running a system, consisting of a 717 autosampler running on IEEE, 515 standalone pump, and a 2475 detector on RS-232, the runtime clock continues past the programmed end time for 10 minutes. The message, instrument fails then appears in the status bar. The problem does not occur if the system does not contain a 717 autosampler running on IEEE or if a SAT/in channel is added to the system. PCS #: 28612 A problem recovering data can occur when extracting an MS derived channel and using an MS processing method to create a result in Review. The following sequence will cause the error: 1) Extract an MS derived channel and use an MS processing method to create a result in Review. 2) Save the Result in Review. 3) Delete the 3D MS datafile that was used to create the result. 4) Take the result back into review and review crashes. PCS #: 28638 MassLynx tune configuration file TUNEPRM.IPR fails Verify Files after a new MS tune is saved. The tunes file (.ipr) is updated/changed each time a user saves any of the values in the tune page. For this reason, the.ipr file should not be part of the verify file routine. Problems Fixed with Empower Service Pack B PCS #: 28784 As more methods were created or copied to a project, access to that project would become slower. This would also affect access to software tools such as the Sample Set Editor. This issue has been resolved in Service Pack B. Problems Fixed with Empower Service Pack C PCS #: 28448 Page 1 of 26

If BCD values from an autosampler were being read into Empower using a SAT/IN module, it was possible for incorrect values to be reported, namely values of 126 or 127. Valid BCD values range from 00 to 99. This behavior has been resolved in Service Pack C. PCS #: 28440 If a toolkit application required the user to select data from Empower, it would assume the use of the Pro interface was appropriate for all data selection, This behavior has been corrected in Service Pack C, now whichever interface the user has open (Pro or QuickStart) will be used for data selection. PCS #: 28574 When using the AutoArchive option for Empower, sample archive entries are created for any samples acquired into a monitored project. However, if acquisition through an acquisition server was done first to one database, and then to a second database where fewer custom field were being tracked, no sample archives would be created in the second database. This behavior has been corrected in Service Pack C, and sample archive entries will be created correctly when sequentially acquiring to multiple database from a single acquisition server. PCS #: 28667 After buffering data on a network installation from a Waters ZQ mass spectrometer, data files could be seen as missing when reviewing the data in Empower. All appropriate information was stored in/with the database but the message Data file checksum error would be seen in the Empower Message Center. This behavior has been corrected in Service Pack C, and checksum errors due to this buffering defect no longer occur. PCS #: 28690 It was possible to see very slow performance on a system acquiring data from a Waters ZQ mass spectrometer. This behavior has been corrected in Service Pack C, and checksum errors due to this buffering defect no longer occur. PCS #: 28690 It was possible to see very slow performance on a system acquiring data from a Waters ZQ mass spectrometer and displaying a large number of SIR channels in the real time view of QuickStart. This behavior has been corrected in Service Pack C, and up to four SIR channels may be displayed at one time. PCS #: 28738 When intersample calculations were used in projects, processing sample sets could take significantly longer than expected. The time taken would increase as the number of vials and/or results in the project increased This behavior has been corrected in Service Pack C, and the time taken for reprocessing when using intersample calculations has been significantly reduced. PCS #: 28934 Under the following circumstances it was possible to use the wrong version of a processing method when reviewing/manually reprocessing data: If a result had a version of the processing method associated with it that was not the most current in the project and this result was taken into the Review application, then a different method were loaded, and then the menu option to Reset Processing Method were selected; the most current version of the method was retrieved from the database instead of the original, older method version associated with the result. This behavior has been corrected in Service Pack C, and correct method version will be retrieved when the Reset Processing Method option is selected. Features Implemented with Empower Service Pack ApexTrack Gaussian skimming is available as a timed event. Page 2 of 26

Valley-to-Valley integration is available as a timed event. When System Suitability is used in an ApexTrack method to calculate USP Resolution or USP Plate Count, the Width @ Tangent field is determined as the width at baseline between two lines drawn tangent to the peak s inflection points. An S29 processing code is added to the peak s results to indicate that this is how the peak s Width @ Tangent is calculated. (When using Traditional integration, Width @ Tangent is determined as the width at baseline between two tangent lines drawn at the Tangent Percent specified in the processing method.) The Start and End time parameters (located in an ApexTrack processing method) are graphically displayed in the chromatogram plot in Review when the Show Events tool is used. When these markers are dragged, the appropriate time in the method is automatically updated. The ApexTrack Width field has been eliminated. Important ApexTrack Integration Information Because of improvements made to ApexTrack integration, you may find slightly different results with some peaks, as compared to the same peak processed using the same ApexTrack processing method in the released version of Empower without the Service Pack ApexTrack. These changes occur due to a modification in the ApexTrack algorithm that prevents piercing of the data signal with the baseline and results in a one data point shift in the start time or the end time of some peaks, hence changing the peak area. After installation of the Empower Service Pack ApexTrack, requalification is required. Features Implemented with Empower Service Pack Light Scattering Light Scattering (GPCLS) is a new processing option that can be enabled after the GPC and/or GPCV options have been enabled. The Light Scattering option allows a user who has collected light scattering data and concentration data in the same injection to perform GPCLS processing of Narrow or Broad Unknown samples and calculate molecular weights without having to create GPC calibration curves. If the GPCV option is enabled, users can also perform GPCVLS (triple detection) processing with or without GPC Universal calibration curves. The menu choice Process > Calibrate Light Scattering System initiates a LS Calibration wizard to lead the user through the process of calibrating the light scattering detector. Three new menu choices: Process > GPC-LS Data, Process > GPCV Data, and Process > GPCV-LS Data have been added to a GPC processing. You then need to either (1) apply the current method set to the current injection (if the method set is capable of producing the appropriate type of result) or (2) create and apply a new method set based on the injection's instrument method. Important Information for GPC and GPCV Users For GPC and/or GPCV users who do not need the new Light Scattering functionality, it is important to note that several GPC and GPCV problems that are listed below have been fixed. Also listed are several new features and improvements to the GPCV software. GPCV Features Implemented with Empower Service Pack Light Scattering PCS #: 27908 When the Fitting Model is set to Calibration, there are 2 new Intrinsic Viscosity Fit choices in the Slicing Table: 1st Order Step and 2nd Order Step. PCS #: 28171 Page 3 of 26

The Viscometer channels attached to GPCV results are marked visible by default in the 2D channel table of Review (as in V3.20 Millennium32). PCS #: 28715 When the alpha LCB in the slicing table is set either too high or too low so that there is a problem calculating g', you now get a V45 processing code (The alpha LCB is too high or too low for the fitted viscosity curve.) instead of a V04 processing code (There is a problem calculating g'.). PCS #: 29325 K LCB was added to the slicing table to go with the already existing alpha LCB value. PCS #: 29333 In Review, the Autoscale button and plot menu entry now set the Normalize X checkbox to false instead of true in the Plot properties for the 2d chromatogram plot. Setting the Normalize X checkbox to false allows the chromatograms to overlay each other using the same X-axis. PCS #: 29337 The processing method wizard in Review now allows you to edit the integration parameters for all the channels in a GPCV result. PCS #: 29416 There is a new item in the Process menu in Review, GPCV Data. The Process > GPCV Data menu item creates new Universal GPC processing method using the processing method wizard if needed and then either (1) applies the current method set to the current injection if the method set is capable of producing a GPCV result or (2) creates and applies a new method set based on the injection's instrument method. If a new GPCV processing method is created via the Process > GPCV Data menu item, the flow rate is copied from the instrument method into the new processing method. GPC Problems Fixed with Empower Service Pack Light Scattering PCS #: 28476 You can now take Broad GPC results in to Review, Preview, and Reporting and view the distribution plots and/or tables. PCS #: 28521 You can now take GPC distributions into Compare and view the distribution plots and/or tables. PCS #: 29110 A narrow standard peak quantitated against a GPC Universal calibration curve is now given the correct MP because the K and alpha in the sample are no longer ignored. GPC and GPCV Problem Fixed with Empower Service Pack Light Scattering PCS #: 29506 When processing in the Review windows of QuickStart with a GPC processing method containing more than 1 row in the slicing table, the broad peak is now identified correctly. GPCV Problems Fixed with Empower Service Pack Light Scattering PCS #: 28398 GPCV Narrow Standard processing will now skip and not assign molecular weights to any peak that does not have a corresponding viscometer peak. PCS #: 28605 Page 4 of 26

In the Method Set tree of the method set window of Review (or the method set editor) when the method set lists an instrument method containing a GPCV instrument, you can now view the Properties of one of the Imported data channels via the right mouse menu. PCS #: 28675 If alpha LCB is entered in the slicing table, the overall peak g' is used to calculate Slice lambda instead of the Slice g'. PCS #: 29162 The overall peak g' is now calculated when the fitting model is Structural, the intrinsic viscosity fit is 1st Order, and there are user-entered K and alpha values for the sample. PCS #: 29207 If the fitting model is Structural, the intrinsic viscosity fit is 1st Order, and the Branching Model is Star, the overall Peak g' and g values are now calculated. PCS #: 29265 GPCV Broad Standard calibration now adds points to the curve because the calculation of fitted viscosity has been fixed when the intrinsic viscosity fit is 1st Order and the fitting model is Calibration. PCS #: 29553 In the default GPCV project for Empower, the instrument method containing the GPCV instrument needs to be recreated using the View Instrument Method menu item in Review after the imported data's injection(s) have been brought in to Review. Known Problems in Service Pack Light Scattering PCS #: 28560 The overall value peak g' is not calculated for broad GPC-LS peaks when there is a user-entered epsilon. This cannot be fixed in a service pack because the fix requires a change to the database, but a user can create a custom field to calculate peak g' either from peak g and epsilon or by summing the slice g' values. PCS #: 29138 There is a new selection in the report method wizard to create a Light Scattering report method, but the report that is currently generated by this method is a basic GPC report which does not include Light Scattering (LS) fields and plots. PCS #: 29346 The peak [n]w value is not calculated for GPC-LS peaks when there is a Universal calibration curve. This cannot be fixed in a service pack because the fix requires a change to the database. PCS #: 29442 The default precision of the RI Sensitivity field in Sample Loading or alter Sample needs to be increased from 0 to at least 2. The help states the following "For example, suppose a 2410 RI Detector is calibrated at a sensitivity setting of 4. If a row in the Samples table specifies an instrument method with the 2410 sensitivity set to 16, enter 0.25 in the RI Sensitivity column of the Samples table. If a row in the Samples table specifies an instrument method with the 2410 sensitivity set to 1, enter 4 in the RI Sensitivity column of the Samples table." A user is not currently able to enter a value of 0.25. This defect was observed in Millennium32 v4.00 and Empower. Problems Fixed with Empower Service Pack D PCS #28812 (User Access To Acquisition Server Properties) A user who has access to a system on an acquisition server but does not have access to the acquisition server properties can access those properties by right clicking on the system itself. While the OK box is grayed out, the owner of the acquisition server is changed to SYSTEM from a non system user. Users who do not have access to an acquisition server will not be allowed to view the acquisition server properties and be presented with a warning dialog box. Page 5 of 26

PCS #28777 (Project Access) Via the Project Properties Access tab, a System Administrator sets project access to a specific group in the system. A user logs into the system with custom field access only, accesses the Project Properties Access tab and notes that the Group User Type is changed to "Users Own Group". The user selects OK and resets the Group User Type to Users Own Group from the specific system group previous entered by the System Administrator. PCS #29854 (Raw Data Files) In conditions where network performance is extremely high and the LACE 32 has been up and active for an extended period of time buffering over 1000 files, it is possible to observe a database entry where no D- files have been created. PCS #29984 (RPC Server Errors) During recent internal evaluation for Empower it was discovered that a situation could develop on a LAC/E 32 such that the Microsoft Remote Procedure Call (RPC) server becomes unavailable, placing the LAC/E 32 into a constant state of buffering. The Microsoft RPC programming functions are used to forward application function calls to a remote system across the network. While this Waters Corporation service pack corrects these particular RPC errors, Microsoft Corporation Windows 2000 Service Pack 3 also corrects other RPC errors. If you are experiencing other specific RPC errors, Waters recommends installing Windows 2000 Service Pack 3. PCS #28443 (Needle Was Time) When trying to modify the needle wash time in the 2695 s Default Separation Method, the time remained unaffected at Normal. In Millennium 32 V4.0 the needle wash time is taken from the default Alliance method but in Empower this is not occurring, forcing the Normal needle wash time. PCS #28502 (Margin Issue In Reports) Customers upgrading from Millennium 32 V3.2 to version 4.0/or Empower Software reported their reports were cut off along the left edge. PCS #30142 (Background Processing) When processing Agilent 1100 data you may see slight differences in peak area counts depending on the application used to process the data ( Review or the Process and Report tool). To determine if a difference exists you would need to expand the precision of the area and height columns (in the Project window or in a report) to at least three decimal places. Features Implemented with Instrument Support Service Pack 1 Empower Instrument Support Service Pack 1 lays the groundwork for implementation of laboratory instrument control using a private Ethernet network. The Service Pack provides additional support for COM (Component Object Model) instruments and support for Ethernet control that will be introduced shortly for a number of instruments. Operation of any instrument via Ethernet will require the installation of Instrument Support Service Pack 1 as a prerequisite. Instruments that will be supported on Ethernet include: Waters 2420 Evaporative Light Scattering Detector, and the Waters EMD 1000 Mass Detector. The Service Pack also provides an updated XML schema for COM instruments that use an HTML Instrument Method editor (A1100 modules, for example). Page 6 of 26

Supporting instruments in a private Ethernet environment requires that IP addresses be assigned. This task is handled by the Waters DHCP Server, which is greatly enhanced in this Service Pack. The Waters DHCP Server utility operates only on the network card that the user identifies as the card that is attached to a private network of laboratory instruments. The Waters DHCP Server will only assign IP addresses to Waters instruments or to Ethernet instruments that have been specifically identified. Problems Fixed with Instrument Support Service Pack 1 30326 When the Light Scattering Service Pack installed, a derived channel cannot be created for a GPC project. After installation of Instrument Support Service Pack, derived channels can be created in GPC projects. 30285 An audit trail comment is required after canceling an operation within the users properties page. After installation of the Service Pack, audit trail comments are not required if the action is cancelled. 30037 Under certain circumstances, audit trail comments for one action could be used for another action without asking the user for another comment. After installation of the Service Pack, the user will be asked for audit trail comments and the comments will be assigned properly. 29481 The Waters DHCP Server does not have a user interface and remote (client/server) capabilities. After installation of the Service Pack, Waters DHCP Server has a user interface accessible from a Tab in Acquisition Server Properties. 29398 COM instruments are not uniquely identified within the software. After installation of the Service Pack, COM instruments are uniquely identified within the software. 28662 Pressing the Scan for Instruments button does not cause the CapLC pump to be recognized. After installation of the Service Pack, the CapLC pump is recognized. 28660 The Condition Column special control function causes a COM instrument to return a negative value for datastart. After installation of the Service Pack, the correct value is returned. 28423 Instrument Method editors for COM instruments do not function properly when two or more COM instruments are in a chromatographic system. After installation of the Service Pack, the Instrument Method editor functions properly. Known Issues with Instrument Support Service Pack 1 30439 When more than one type of Ethernet instrument is in use, scanning for instruments may intermittently fail to detect all instruments. 30481 The Project MFC Application message pops up when the Project Window closes after buffering has occurred. Click OK to exit the application and then click Don t Send. 30722 After reinstalling Windows XP, Empower, and Instrument Support Service Pack 1, the message Waters DHCP Server Chinese Resource.DLL has encountered a problem and needs to close If this message appears, please continue with the installation and reboot the computer. If the message appears after rebooting, contact Waters customer support. Features Implemented with Instrument Support Service Pack 2 Empower Instrument Support Service Pack 2 fixes several defects in Empower. These defects are listed on page 4 of this document. Additionally, Instrument Support Service Pack 2 provides support for the Agilent A1100 DA detector (DAD models G1315A or G1315B) in 3D mode using Ethernet connectivity. In addition to this service pack, an A1100 Plus License (key disk) is required in order to use an A1100 system containing an A1100 DAD to acquire 3D spectral data. The A1100 Plus License (key disk) is not required in order to install the defect fixes contained in this service pack. Problems Fixed with Empower Instrument Support Service Pack 2 PCS #: 30602: Abort and Change Vial Number not Documented Properly Page 7 of 26

When you abort a sample set (using the Abort Now option) and then change a vial number and resume acquisition, the injection occurs from the correct vial, but the original vial is displayed in the software (Project Window, Review, Reports, etc.) Additionally, when you resume acquisition, the row you were running when the abort occurred should be displayed in red but is not. This problem is fixed in Empower Instrument Support Service Pack 2. When this service pack is applied, the vials are documented correctly in the software and the lines in Run Samples highlight in red appropriately. PCS #: 30828: Instrument Method Problems for A1100 Using VWD. When a locked instrument method (containing a variable wavelength detector (VWD)) is specified in Run Samples and the user edits the instrument method when Run Samples is not in an Idle state (i.e. Run Samples is Setting up ), the original instrument method parameters are executed during acquisition, not the modified parameters. This problem is fixed in Empower Instrument Support Service Pack 2. When this service pack is applied, the correct A1100 instrument method parameters are used. PCS #: 28995: Legend does not Print when Printing from Review. When printing a chromatogram from Review, the legend (specified in the Plot Properties) does not print. This problem is fixed in Empower Instrument Support Service Pack 2. When this service pack is applied, chromatogram legends print from Review. PCS #: 31059: Create Project OK to All Copies Previous Comments into Audit Trail. After installing Empower Instrument Support Service Pack 1, which fixes an Audit Trail issue in full audit trail projects (PCS # 30037), one symptom of the original problem still remains. During project creation, two audit trail entries are added to the System Audit Trail. If the user selects OK to All after entering the audit trail comment during project creation, only one of the project creation audit trail entries contains the correct comment. The other project creation audit trail entry contains a comment from a previous, irrelevant audit trail entry. This problem is fixed in Empower Instrument Support Service Pack 2. When this service pack is applied, the audit trail comments are correct for project creation audit trail entries. Known Issues with Empower Instrument Support Service Pack 2 PCS # 31167: File not removed when ISSP2 is Uninstalled. When Empower ISSP2 and all previous Empower service packs are installed, and then only ISSP2 is uninstalled, the Empower\Instruments\HTML\A1100\A1100-PostRunRpt-r100.xsl file is not always removed. The A1100-PostRunRpt-r100.xsl file is a new file for ISSP2 and it is only used by the A1100.dll. If the file is not removed during uninstallation, there is no negative impact on the system. PCS # 30252: Shutdown Method Gives Instrument Failure with A1100 DAD System When a shutdown method is specified with an A1100 DAD system, an instrument failure may occur at the end of the sample set. To avoid this problem, add a zero volume injection line to the end of your sample set. This line should contain a method set with an instrument method to shutdown the system. The method on this line will run for the specified run time. The run time should therefore be set long enough to allow the shutdown changes to occur. Do not incorporate your shutdown parameters directly in the instrument method that you are routinely using on each injection line because when using an A1100 system, the instrument method stops running at the end of the run time and the system reverts back to initial conditions. (Conversely, when using a system containing Waters equipment, the instrument method continues to execute after the specified run time, until another injection occurs.) PCS # 29881: Condition Column Function Not Supported with A1100 Systems When a Condition Column function is present in a sample set using an A1100 system, the sample set will remain on the Condition Column line indefinitely and will not advance to the next line in the sample set. The Condition Column function is not supported with an A1100 system in Millennium32 4.0, Empower or Empower Instrument Support 2 Service Pack. PCS # 30947: Help Does Not Display Page 8 of 26

When attempting to launch Help, a message occurs stating that the help file cannot be opened or that it cannot be displayed. If this occurs, locate and delete X:\Empower\Help\Master.GID (where X is the location where Empower is installed.) PCS # 30288: External Contact Closure Event Card is Not Supported in DAD when the LAN Card is Present The external contacts are not available in the DAD when a LAN card is present. The Event card should be placed in another A1100 module; the contacts can be used from there. PCS # 29945: Must Follow Proper Sequence When Deleting A1100 Ethernet Instrument Before deleting A1100 Ethernet instruments from the Instruments tab of the Acquisition Server properties, it is necessary to remove the DHCP entry from the DHCP Configuration Page (using the Configure DHCP tab). Next, remove the A1100 instrument from the Instruments tab. PCS # 30256: Apply Button when no Changes Made During an equilibration, if the user clicks the Change Flow button but makes no changes, if the Apply button is then clicked a message indicating that the flow rate changed is posted to the Message Center. In this scenario, it is not necessary to click Apply. Click Cancel instead. PCS # 30946: Entry of Invalid Bandwidth It is possible to enter an invalid bandwidth (i.e. 0) by entering the value and then saving the method without clicking somewhere else in table. Problems Fixed with Empower Toolkit Service Pack Fix defect PCS #28591 (Toolkit Memory Leak) Fixes a Memory leak surrounding the ResultViewer object. When calling and releasing the ResultViewer and associated objects, system memory will be appropriately released. Fix defect PCS #28480 (Quick Start Interface) Allow full functionality of the Quick Start Interface via Toolkit. When a user logs in to Empower via the Toolkit Project object Login method, Toolkit should check what allowed interfaces the user has and open the appropriate interface based on their Default User Interface setting. This also caused problems when fetching result id information based on the mtkselected option of the ResultViewer. Through further investigation of this defect, changes were also made to the Project Object LaunchMilApp Method. Detail changes on this fix: A fourth optional parameter was added to the Project Object s LaunchMilApp method, mtkuserinterface ui. The Method now is: LaunchMilApp(mtkMillenniumApp milapp, mtkconnectoptions connectoption, VARIANT varargs, mtkuserinterface ui), Where mtkuserinterface is an enumeration of (mtkdefault = 0, mtkquickstart = 1, mtkpro = 2, mtkopenaccess = 3, mtkweb = 4). This allows the ToolKit user to specify which interface they wish to launch, with some caveats. - If the optional argument isn t supplied, Toolkit will look at the supplied User s default interface and use that (and if that selection is set to use the system default, it will use the System Policy Default UI setting). - If the optional argument supplied is mtkdefault, Toolkit will launch via the System Policy Default UI setting. - If the optional argument supplied is mtkpro or mtkquickstart, Toolkit will check to see if the given user has the appropriate privileges for that, if not it will return an error. - In the case where mtkopenaccess or mtkweb is specified or defaulted to, an error will be returned as these are not supported interfaces via ToolKit. Page 9 of 26

Note: There are timing issues with launching applications ( i.e. Project, Review) with the QuickStart interface, whereas the behavior is not consistent when launching with a particular view, i.e. Launching Project/QuickStart/Channels may display Find Data/Samplesets view. In these cases the user will have to make an additional selection manually to the appropriate tab view. Fix defect PCS #28474 (Apex Track) When Apex Track is enabled there are different Integration Parameters and Events in Empower. However, the Visual Basic object browser will only show fields corresponding to Traditional Integration. In Empower there are two sets of integration parameters, Apex Track and Traditional. When editing a processing method with Apex Track integration parameters the ToolKit will load the Apex Track fields for the IntegrationParameters object, when editing a processing method with Traditional integration the ToolKit will load those fields. This is seamless to the ToolKit user; you will simply see the appropriate fields based on which kind of processing method you are editing. Fix defect PCS #29096 (LaunchMillApp Method) The Project object LaunchMillApp method has an mtkcreateifnecessary connect option. If this option is used, the application is only started if it is not already running based on the Login parameters. Currently Toolkit will ignore the mtkcreateifnecessary option and create a new application window. Using this mtkcreateifnecessary connect option will now operate correctly and not create a new application window. Fix defect PCS #29563 (Enforce Unique User Account Names) If attempting to create a user through the Toolkit User object and the system policy Enforce Unique User Account Names is set, the Toolkit will not display the appropriate message box stating User name x already in use. The system creates the account by appending a number 1 to the end of the duplicate name attempting to be created. Toolkit will now return an error if that user name is already in use. Toolkit will also check to ensure the account name meet s the minimum length requirements, if not, an error will be returned. Fix defect PCS #29565 (Project Object Login) If attempting to login via the Toolkit Project object, the Toolkit will not display the appropriate errors for the different login conditions. The following list details these conditions and the revised Toolkit action: 1. A new user account is created via Empower or Toolkit and Password Required was enabled. When attempting to log into Empower via Toolkit for the first time using this new account, the Toolkit did not display a message box stating Your Password has Expired. Toolkit will now display an error that the password has expired. The user must log in through the Empower Software to correct this. By design, the Toolkit can not create or modify passwords. This must be done through the Empower Software. 2. If the System Policy Enforce Minimum Password Length of: x characters is enabled and a user logs into Empower via Toolkit with a password not meeting this policy, Toolkit did not display a message box stating, The password for this account no longer meets current system policies for length. Toolkit will now display this message box and direct the user to change their password by logging in through Empower Software. By design, the Toolkit can not create or modify passwords. This must be done through the Empower Software. 3. If the System Policy Passwords Expire every: x days is enabled and a user logs into Empower via Toolkit with a password not meeting this policy, Toolkit did not display a message box stating, Your password will expire in x day(s). Toolkit will now display an error when the password has expired. The user must log in through the Empower Software to correct this. By design, the Toolkit can not create or modify passwords. This must be done through the Empower Software. Fix defect PCS #29594 (Result and Sample Information Changes) Page 10 of 26

The New Project Policies tab for Empower System Polices has a "Result Changes" and "Sample Information Changes" check box under 'Default Full Audit Trail Settings' - 'Full Audit Trail Support'. When these are checked and Result or Sample Information changes are made via the Toolkit the user is not prompted to enter a reason for these changes as they are in the base application. If the Sample Information Changes System Policies is enabled, sample information changes made via Toolkit will now prompt the user to enter a reason for these changes. Toolkit programmers may automate this response in code using the Toolkit RevisionComment Property. Setting this Property will automatically enter the comment and not prompt the user for an entry. Note: Results cannot be changed via Toolkit therefore checking this has no effect on Toolkit. Fix defect PCS #29675 (Copy From Non-FAT to FAT Projects) When the System Policy, "Don t allow user to copy from non-fat projects into FAT projects" is checked, any Toolkit object that allows the user to copy between projects should be checked. Currently if this is enabled Toolkit users can still copy between non-fat and FAT projects. When an inappropriate copy is now performed, Toolkit displays the message Can t copy from non-fat projects into FAT projects. Fix defect PCS #28711 (User Object) When creating a user via the Toolkit User object, you are restricted from starting the name with a numeric character. This is allowed within the base Empower application and should function the same within Toolkit. Users now created via the Toolkit User object are not restricted from starting the name with a numeric character. Fix defect PCS #30959 (KPRIME) When the System Suitability and GPC/LS (Light Scattering) options are enabled, both options contain a KPRIME field which causes a conflict in Toolkit. Due to the conflict, Toolkit does not return any KPRIME value. However, Toolkit works fine when only one of the options is enabled. The following list details the Peak field name mappings from Empower Software to Toolkit when the GPC/LS Option is enabled: - Empower Software Toolkit K(LS) KLS Alpha(LS) AlphaLS Linear K(LS) LinearKLS Linear Alpha(LS) LinearAlphaLS Mz(LS) MzLS Mz+1(LS) MzPlus1LS Note: There was no change made to the System Suitability mappings. Fix defect PCS #31170 (Data Acquisition Privileges) User accounts that do not have the Data Acquisition Privilege are able to perform data acquisition via a Toolkit application. With the Data Acquisition Privilege enabled, User accounts will not be able to perform data acquisition (i.e. run a single injection or sample set). Fix defect PCS #31242 (Copy Preferences) When you create a new Project through Empower, You can 'copy preferences' from another project. In Toolkit, there is no property to set for copying preferences. A new Boolean Property was added to the DBProject Object called CopyPreferences, and works the same as other DBProject Copy Methods such as CopyMethods, CopyViewFilters, etc. If CopyPreferences is set to True when creating a new project using the DBProject.Copy method, Toolkit will copy the existing options and preferences from the specified source project. Note: Existing options includes the following options built into the base Empower Software: Photo Diode Array, Mass Spectrometry and CE/CIA. Page 11 of 26

New Features Added with Empower Toolkit Service Pack PCS #28590 (Summarize Function) The Empower feature Summarize Custom Fields was not implemented via Toolkit. The Constant information is as follows: Identifier Value Used By mtksummarizecustom 39 Static Fields Type Custom Menu Item Argument Toolkit Custom Menu Items were created to provide users access to any application from within the Empower Software. The last parameter is a space-delimited list of command line arguments that are passed to the executable upon startup. These arguments are placed in the registry key for the custom menu item and would expand during program runtime. As an example %p expands to the current project name, expand meaning the current project name is added to the command line during runtime in place of the %p parameter. A new Custom Menu command line parameter of %a has been created. This would expand to the current acquisition server node when launched from Run Samples (Pro Interface) or Quick Start Interface. Com Instrument XML Interface A new object InstSetupCom will be added to InstSetups family. This object is unlike other InstSetup objects in that it will handle multiple instrument setups defined as COM instruments. COM instruments that save their instrument setup data as XML will be handled by this new object. The InstSetupCOM object will be a general purpose object designed to expose Empower instrument setups that are stored as XML (i.e. new COM instruments) to Toolkit users. Unlike existing InstSetup objects that are tailored to the individual instrument, (InstSetup600, InstSetup2790, etc.) this object will handle multiple types of instruments via a simple set of commands. The InstSetupCOM object will allow a Toolkit user to fetch and store the XML blob that contains the instrument method parameters for a particular COM instrument. The XML data will be fetched and stored as a single entity. The Toolkit Programmer is responsible for validating any and all modifications made to the XML prior to setting the XML property. There will be little or NO error checking and/or range validation done on the XML being sent down to the database. The Toolkit Programmer should parse through the XML schema capturing each field s minimum and maximum parameter, which can then be validated in your code prior to modification. The XML schema (whose extension is.xsd) for each COM instrument is supplied by Waters and can be found in the appropriate directory for that instrument under the Empower/Instruments/HTML subdirectory. The InstSetupCOM object derives from the base class InstSetup in order to allow polymorphic handling of all types of InstSetups in any Instrument Method. The InstSetupCom object has all the properties and methods of the InstSetup object and the following additional property. NOTE: The Type property will always return mtkcom for any and all COM based instruments. XML() as String Set: Sets the XML method data for the instrument Get: Returns the XML method data for the instrument Default: N/A IEEE Instrument Setup for Waters 486, 410, 2410, 2414, 2790/5 and Agilent 5890/7673, 5890S/7673S, 6890 GC s - InstSetup486 The InstSetup486 encapsulates the setup information for the Waters Corporation 486 instrument. The InstSetup486 object has all the properties and methods as described by InstSetup. Its dynamic fields are specific to the 486 instrument setup. It also has the following additional properties. EventLines as EventLine486S Page 12 of 26

Set: Sets the value for this event lines collection. Get: Returns the current collection of event lines. Default: An EventLine486S collection containing the event line information for this InstSetup486. - InstSetup410 The InstSetup410 encapsulates the setup information for the 410 instrument. The InstSetup410 object has all the properties and methods as described by InstSetup. Its dynamic fields are specific to the 410 instrument setup. Note: The 2410 and 2414 show up as a 410 instrument in Empower. - InstSetup2790 The InstSetup2790 encapsulates the setup information for the 2790/5 instrument. The InstSetup2790 object has all the properties and methods as described by InstSetup. Its dynamic fields are specific to the 2790 instrument setup. It also has the following additional properties. EventLines as EventLine2790S Set: Sets the value for this event lines collection. Get: Returns the current collection of event lines. Default: An EventLine2790S collection containing the event line information for this InstSetup2790. GradientLines as GradientLines Set: Sets the value for this gradient lines collection. Get: Returns the current collection of gradient lines. Default: A GradientLines collection containing the gradient line information for this InstSetup2790. - InstSetup5890 The InstSetup5890 encapsulates the setup information for the HP 5890 and 5890S series instruments. The InstSetup5890 object has all the properties and methods as described by InstSetup. Its dynamic fields are specific to the 5890 and 5890S instrument setups. It also has the following additional properties and sub objects. RampLines as RampLine5890S Set: Sets the value for this ramp lines collection. Get: Returns the current collection of ramp lines. Default: An RampLine5890S collection containing the ramp line information for this InstSetup5890. Channels as Channel5890S Get: Returns the current collection of channels. Default: A Channel5890S collection containing the channels information for this InstSetup5890. RampLine5890S Dynamic collection of RampLine5890 objects. Used by InstSetup5890 object to manipulate the ramp lines of a HP 5890 series instrument setup. There are no additional properties or methods. RampLine5890 The RampLine5890 object encapsulates a HP 5890 series ramp line object. It contains the fields specific to a HP 5890 series ramp line. Fields() as Fields Get: Returns the current collection of Fields. Default: A Fields collection containing all the RampLine5890 fields, FieldType is mtkeventline. XXX([FormatData as Variant]) as Variant Dynamic property where XXX stands for the name of the field whose value is to be returned. Only the names of the fields in the Fields property can be used. All RampLine5890 dynamic properties can use both Set() and Get() functions. After a property is set, its get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). Page 13 of 26

If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Methods: Set(FieldName, Value) FieldName as string: Contains name of the dynamic field whose value is to be assigned. Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives greater programmatic flexibility. Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. Action: Returns the value of the desired dynamic field name. This provides another way to retrieve a dynamic property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives greater programmatic flexibility. Channel5890S Dynamic collection of Channel5890 objects. Used by InstSetup5890 object to manipulate the channels of a HP 5890 series instrument setup. There are no additional properties or methods. Channel5890 The Channel5890 object encapsulates a HP 5890 series channel object. It contains the fields specific to a HP 5890 series channel. Fields() as Fields Get: Returns the current collection of Fields. Default: A Fields collection containing all the Channel5890 fields, FieldType is mtkischannel. XXX([FormatData as Variant]) as Variant Dynamic property where XXX stands for the name of the field whose value is to be returned. Only the names of the fields in the Fields property can be used. All Channel5890 dynamic properties can use both Set() and Get() functions. After a property is set, its get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Methods: Set(FieldName, Value) FieldName as string: Contains name of the dynamic field whose value is to be assigned. Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives greater programmatic flexibility. Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default - False. Action: Returns the value of the desired dynamic field name. This provides another way to retrieve a dynamic property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives greater programmatic flexibility. - InstSetup6890 The InstSetup6890 encapsulates the setup information for the HP 6890 series instrument. The InstSetup6890 object has all the properties and methods as described by InstSetup. Its dynamic fields are specific to the 6890 instrument setup. It also has the following additional properties. FrontDetector as HP6890Detector Page 14 of 26

Get: Returns the current FrontDetector object. Default: A HP6890Detector object containing the front detector information for this InstSetup6890. BackDetector as HP6890Detector Get: Returns the current BackDetector object. Default: An HP6890Detector object containing the back detector information for this InstSetup6890. FrontInjector as HPInjector Get: Returns the current FrontInjector object. Default: An HPInjector object containing the front Injector information for this InstSetup6890. BackInjector as HPInjector Get: Returns the current BackInjector object. Default: An HPInjector object containing the back Injector information for this InstSetup6890. FrontInlet as HP6890Inlet Get: Returns the current FrontInlet object. Default: An HP6890Inlet object containing the front Inlet information for this InstSetup6890. BackInlet as HP6890Inlet Get: Returns the current BackInlet object. Default: An HP6890Inlet object containing the back Inlet information for this InstSetup6890. Column1 as HP6890Column Get: Returns the current Column1 object. Default: An HP6890Column object containing the column information for this InstSetup6890. Column2 as HP6890Column Get: Returns the current Column2 object. Default: An HP6890Column object containing the column information for this InstSetup6890. RampLines as RampLine6890S Set: Sets the value for this ramp lines collection. Get: Returns the current collection of ramp lines. Default: An RampLine6890S collection containing the ramp line information for this InstSetup6890. Channels as Channel6890S Get: Returns the current collection of channels. Default: A Channel6890S collection containing the channels information for this InstSetup6890. RampLine6890S Dynamic collection of RampLine6890 objects. Used by InstSetup6890 object to manipulate the ramp lines of a HP 6890 series instrument setup. There are no additional properties or methods. RampLine6890 The RampLine6890 object encapsulates a HP 6890 series ramp line object. It contains the fields specific to a HP 6890 series ramp line. Fields() as Fields Get: Returns the current collection of Fields. Default: A Fields collection containing all the RampLine6890 fields, FieldType is mtkeventline. XXX([FormatData as Variant]) as Variant Dynamic property where XXX stands for the name of the field whose value is to be returned. Only the names of the fields in the Fields property can be used. All RampLine6890 dynamic properties can use both Set() and Get() functions. Page 15 of 26

After a property is set, its get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Methods: Set(FieldName, Value) FieldName as string: Contains name of the dynamic field whose value is to be assigned. Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives greater programmatic flexibility. Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved.. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. Action: Returns the value of the desired dynamic field name. This provides another way to retrieve a dynamic property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives greater programmatic flexibility. Channel6890S Dynamic collection of Channel6890 objects. Used by InstSetup6890 object to manipulate the channels of a HP 6890 series instrument setup. There are no additional properties or methods. Channel 6890 The Channel6890 object encapsulates a HP 6890 series channel object. It contains the fields specific to a HP 6890 series channel. Fields() as Fields Get: Returns the current collection of Fields. Default: A Fields collection containing all the Channel6890 fields, FieldType is mtkischannel. XXX([FormatData as Variant]) as Variant Dynamic property where XXX stands for the name of the field whose value is to be returned. Only the names of the fields in the Fields property can be used. All Channel6890 dynamic properties can use both Set() and Get() functions. After a property is set, its get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be formatted string using the Empower width and precision specifications. Methods: Set(FieldName, Value) FieldName as string: Contains name of the dynamic field whose value is to be assigned. Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives greater programmatic flexibility. Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. Action: Returns the value of the desired dynamic field name. This provides another way to retrieve a dynamic property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives greater programmatic flexibility. HP6890Inlet The HP6890Inlet object encapsulates a HP 6890 series inlet object. It contains the fields specific to a HP 6890 series inlet. Fields() as Fields Get: Returns the current collection of Fields. Page 16 of 26