==== AFT Fathom 7.0 (Version Date 2012.01.06) Release Notes ===== This file contains last minute information not included in the version 7.0 manua l. Topics. 1. Information about to ens. 2. Errors in and updates to the AFT Fathom 7.0 manual 3. Example and verification files included 4. Notes for networ installations 5. Setting up User Log trac ing 6. Graphic Server conflicts 7. Changes and bug fixes

============================================================== 1. Information about to ens ============================================================== Information on issues related to protection to ens is given in two places. The T OKEN.HLP file located on setup CD has basic information about managing to ens. T he Fathom.HLP file has additional information about setting up pointers to to en s located on LAN's or WAN's. Loo for the CONTROL.AFT topic.

============================================================== 2. Errors in and updates to the manual ============================================================== USER GUIDE Page 291 -- Discussion of Hazen Williams says: "Users who want their results to match the NFPA version in Equation 8.24 can do so by one of the following two options:" The reference to Equation 8.24 should reference Equation 8.21. Page 296 -- The formula for the Bingham Plastic laminar friction factor did not show the fL term on both sides of the equation. Also, the equation used incorrectly converted the Fanning friction factor calcul ated by the Darby equations into the Darcy friction factor used by Fathom. The formulas have been modified to reflect the correct calculations. The equation for the turbulent friction factor was modified to reflect the prope r conversion from Fanning friction factor to Darcy friction factor. The constant in the formula for the "a" exponent in the t urbulent friction factor was corrected to 1.47 rather than the incorrect value or 5.88. MODULE USER GUIDE Page 95 Valve Cv for Valves J4 and J6 should be 100 not 10, for both SI and English vers ions.

============================================================== 3. Example and verification files included ============================================================== When you install AFT Fathom, a folder named EXAMPLES is created in your AFT Fath om folder. Several input files are provided for your review. See the help file F athomExamples.hlp for additional information. In addition, a directory called VERIFICATION is created. Here there are numerous files that give information on calculation verification. See the help file F5Ve rify.hlp for additional information.

============================================================== 4. Notes for networ installations ============================================================== See the FATHOM.HLP "Information on Software Installation" topic for important in formation about networ installation. There are two parts which need to be installed for AFT Fathom to function: 1) th e application, and 2) the copy protection. Note that these installation steps ne ed to be performed as an administrator and with elevated permissions as required by the operating system. The full application can be installed on each user's computer or on a networ ed server. In either case the copy protection needs to be installed on the server. Below are the steps to ta e in these two situations. *** Application AND copy protection BOTH on the SERVER*** 1) Install the full application on the server using the "Networ Installation" o ption. 2) If the installation was downloaded from AFT's website then also download the Client Setup and save it in a folder called Networ Client Setup that is located below the application folder from step 1. You may need to create this folder. 3) Install the copy protection by running the AFTCopyProtectionSetup. If a USB ey or Cryp ey has already installed for another application it usually does not need to be reinstalled but may need to be updated to run the new application. 4) On each client, run the Networ Client Setup which should be located in the N etwor Client Setup folder (see step 2 above) on the server. This will create th e shortcuts on the client to the application on the server as well as install/re gister DLLs, OCXs and example model files. 5) If Cryp ey is used for the copy protection, then each client must run the AFT CopyProtection setup to install the client portion of the Cryp ey files. *** Application on the CLIENT with the copy protection on the SERVER*** 1) Install the copy protection on the server by running the AFTCopyProtectionSet up. If a USB ey or Cryp ey has already installed for another application it usu ally does not need to be reinstalled but may need to be updated to run the new a pplication. 2) Install the full application on EACH client using the "Client Installation" o ption. 3) If a Networ USB ey (red) is used then the Nethasp.ini file may need to be m odified with the IP address of the server. See the HASPKeyGuide.pdf located in t

he AFT Products folder on the server for more information. 4) If Cryp ey is used for the copy protection, then each client must run the AFT CopyProtection setup to install the client portion of the Cryp ey files.

============================================================== 5. Setting up User Log trac ing ============================================================== Summary of User Logs Each time a user starts AFT Fathom, information about the user s computer log-on n ame, computer name and time AFT Fathom was started is automatically logged in a file called FathomUser.log. This file is located in a folder called Logs. The log can be viewed using the AFT User Log Viewer that is installed in the App lication folder. This will show all people currently using AFT Fathom. Chempa d ata to en usage is logged in to a separate file that can be viewed using the Use r Log Viewer. Note: This log file is only created when software to ens are used. No log file i s created if a hardware ey is used. Using the AFT User Log Viewer When AFT User Log Viewer is started, it will automatically determine where the a pplication to en is located and try to open the user log file. The User Log View er can be run independently and does not need to have AFT Fathom running to wor . A table at the bottom will show the current people using AFT Fathom. It will s how the log-on name of the user, the computer they are using and the time they s tarted AFT Fathom. If there is contact information available (see Requiring Cont act Information below) it is also shown. Choosing Refresh from the File menu can refresh the list. Other information about the log file and to en is also shown above the user tabl e. This includes the location of the log file, the date and time the log was cre ated and last modified, the location of the to en, the to en serial number and t he maximum number of current users. You can switch to view the user log for the Chempa data by choosing Chempa Log from the File menu. This will show the people who are accessing the data files from any application. For example, if one person is using the Chempa data in AF T Arrow, another in AFT Fathom and a third in Chempa Viewer; all three users wi ll be listed in the table of users. You can switch bac to the application user log by choosing Application Log from the File menu. Control.aft and Remote To ens The AFT User Log Viewer relies on the Control.aft file located in the applicatio n folder to determine which application log file is to be viewed and where the a pplication and Chempa to ens are located. If this file is not found an error oc curs because the User Log Viewer cannot get the required information to run. The default location for the application to en is the application folder. Howeve r, the to ens can be deployed at a different location for various reasons. The C ontrol.aft file describes where the to en is found. The User Log Viewer will use this information to determine where the log file is located. The log file is al

ways placed in a folder called Logs, which is a sub-folder of the location set i n the Control.aft file.

Requiring Contact Information It can be helpful to have more information about the person using AFT Fathom (or Chempa data) than is standard. In this case contact information can be require d. To enable this feature, open the log file (located in the Logs folder) and fi nd the heading [FILE CONTROL] and set Require Contact Info = TRUE If contact information is required but not available, the user that launches AFT Fathom will be as ed to provide his/her name, location and telephone number. Th is information is saved in the user s Fathom7.ini file, located in \Documents and Settings\[username]\Application Data\Applied Flow Technology\AFT Fathom\7.0. Thi s information can be changed by the local user by editing the Fathom7.ini file w ith a standard text editor such as Notepad. Disabling the User Log Feature The feature of logging users can be disabled by editing the log file (located in the Logs folder). Find the heading [FILE CONTROL] and set Enable Log = FALSE Multiple Entries and Other Problems Occasionally a user may be entered in the log file even though he has closed the application. This can occur for a number of reasons, including not exiting the application normally. If this happens, the next time the user launches the appli cation he will be as ed if he wants to overwrite the entry in the file with this new log-on information. Typically the answer is "Yes, overwrite the information ". If the user is actually running two incidences of the application then answer "No" to this question and both incidences will be logged.

============================================================== 6. Graphic Server conflicts ============================================================== AFT Fathom uses a third party tool for graphing called the Graphics Server. Ther e are four files that are used to load and run the Graphics Server: GRAPHS32CX GSW32.EXE GSWDLL32.DLL GSWAG32.DLL Because of how the Graphics Server is written, multiple copies of GSW32.EXE or G SWDLL32.DLL in your Path will cause problems when your try to load AFT Fathom. In practice, the most common problem is a networ installation where all AFT Fat hom files have been installed into the networ folder along with AFT Fathom. Thu

The Control.aft file also describes where the Chempa data files and the Chempa data to en are located. If no license or to en is found for the data, an error occurs and no information will be given.

s, GSW32.EXE and GSWDLL32.DLL will exist in the AFT Fathom networ folder. A cli ent PC which happens to have copies of either or both of these files on the loca l hard drive (usually in the WINDOWS\SYSTEM folder on Windows 9x and WINNT\SYSTE M32 on Windows NT/2000) will fail to load properly. The most li ely reason copie s exist on the local hard drive is another application installed locally uses th em. A complete list of your options is given below, along with an explanation of the impact of each option. The recommended option is number 5. In the following exp lanations, the term conflicting files means the GSW32.EXE and GSWDLL32.DLL files . Your WINDOWS\SYSTEM folder is just called your SYSTEM folder. 1. Delete the conflicting files on your hard drive. This will solve the problem for AFT Fathom, but may cause other software you use to stop wor ing. This is no t a permanent solution in that if you install other software in the future that installs copies of the conflicting files into your SYSTEM folder, the current pr oblem with AFT Fathom will occur again. 2. Change the names of the conflicting files on your hard drive. This will solve the problem for AFT Fathom, but may cause other software you use to stop wor in g. However, when you try to run the other software and it fails to load because of these missing files, you can change the names bac to the original names. Thi s will then cause AFT Fathom to stop wor ing until you rename them once again, b ut will allow you to run your other software that needs these files. This will a lso require you to remember which files you renamed. This is not a permanent sol ution in that if you install other software in the future that installs copies o f the conflicting files into your SYSTEM folder, the current problem with AFT Fa thom will occur again. 3. Move the conflicting files on your hard drive into the application folder tha t uses them. This will solve the problem for AFT Fathom and still allow the othe r software you use to run properly. However, you will need to now which softwar e uses the conflicting files so you can copy the files into their folder. If you remember what you do, you can move the files out of the SYSTEM folder (or where ver conflicting files exist) and into a temporary folder. When a software applic ation that used to wor fails because these files are missing, you can copy the files into its folder at that time. This is not a permanent solution in that if you install other software in the future that installs copies of the conflicting files into your SYSTEM folder, the current problem with AFT Fathom will occur a gain. 4. Allow AFT Fathom to automatically rename the files for you. This is not a per fect solution, but it does have advantages. This option enables a feature whereb y AFT Fathom searches for the conflicting files in both your SYSTEM folder and W INDOWS folder before the full AFT Fathom application is launched. If it finds th em, it automatically renames them and thus only the copies in the AFT Fathom net wor folder are found. When you exit AFT Fathom, the files will be renamed bac to their original names. The advantages are, 1) you can continue to run your oth er software that uses these files and AFT Fathom with no conflicts (as long as t hey are not run at the same time) and, 2) even if you install other software in the future, this option will continue to wor for you. The disadvantages are, 1) you are permitting AFT Fathom to change files on your local hard drive every ti me it is run, which understandably ma es some users uncomfortable and, 2) you ca nnot run AFT Fathom at the same time as the other software which needs these fil es. 5. Reinstall AFT Fathom with the option to run auxiliary files on commended). This option is the best long-term option. To do this, l AFT Fathom from the networ and reinstall it with the option to files on the client. See Information on Software Installation for the client (re first uninstal use auxiliary more help.

============================================================== 7. Changes and bug fixes ============================================================== *** Changes for Version Date 2008.02.22 *** None: Initial Release

*** Changes for Version Date 2008.04.18 *** >> Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results > Changes to computation logic that could impact results > Changes to data management that could impact results > Changes that do not impact results