README.TOO MULTIMED Multimedia Exposure Assessment Model Version 1.01 PREMED Interactive Data Preprocessor Program for MULTIMED Version 1.01 POSTMED Interactive Graphics Postprocessor Program for MULTIMED Version 1.01 June 1991 Center for Exposure Assessment Modeling (CEAM) U.S. Environmental Protection Agency Office of Research and Development Environmental Research Laboratory College Station Road Athens, Georgia 30613-0801 404/546-3549 or (FTS) 250-3549 __________________________________________________________________ CONTENTS Introduction Overview of MULTIMED Model Capabilities Documentation Distribution Diskettes File Name and Content Files Not Compressed Compressed Files Decompressed Files from PREMDRUN.ZIP Decompressed Files from MULTMRUN.ZIP Decompressed Files from POSTMRUN.ZIP Decompressed Files from MULTMFOR.ZIP Special Run Time File Development System Graphics Support Detailed Installation Instructions Routine Execution Run Time and Performance Minimum File Configuration Modification Technical Help Contact Disclaimer Bibliography __________________________________________________________________ INTRODUCTION ** Overview of MULTIMED ** MULTIMED simulates the transport and transformation of contaminants released from a waste disposal facility into the multimedia environment. Release to either air or soil, including the unsaturated and the saturated zones, and possible interception of the subsurface contaminant plume by a surface stream are included in the model. Thus, the model can be used as a technical and quantitative management tool to address the problem of the land disposal of chemicals in the multimedia environment. At this time, the air modules of the model are not linked to the other model modules. As a result, the estimated release of contaminants to the air is independent of the estimated contaminant release to the subsurface and surface water. MULTIMED utilizes analytical and semi-analytical solution techniques to solve the mathematical equations describing flow and transport. The simplifying assumptions required to obtain the analytical solutions limit the complexity of the systems that can be represented by MULTIMED. The model does not account for site- specific spatial variability, the shape of the land disposal facility, site-specific boundary conditions, or multiple aquifers and pumping wells. MULTIMED can not simulate processes, such as flow in fractures and chemical reactions between contaminants, which can have a significant effect on the concentration of contaminants at a site. In more complex systems, it may be beneficial to use MULTIMED as a "screening level" model to allow the user to gain an understanding of the system. A numerical model could then be used if there are sufficient data and necessity to justify the use of a more complex model. ** Model Capabilities ** During the development of this model, emphasis was placed on the creation of a unified, user-friendly, software framework, with the capability to perform uncertainty analysis, that can be easily enhanced by adding modules and/or modifying existing modules. To enhance the user-friendly nature of the model, separate interactive preprocessing and postprocessing software has been developed for use in creating and editing input and in plotting model output. The pre- and postprocessors, PREMED and POSTMED, have not been integrated with MULTIMED because of the size limitations of PC computers. Therefore, after using the preprocessor to create or modify input, the model is run in batch mode. Afterwards, the postprocessor can be used to produce plots of the Monte Carlo output or plots of concentration versus time for transient output. The fate of contaminants critically depends on a number of media- specific parameters. Typically many of these parameters exhibit spatial and temporal variability as well as variability due to measurement errors. MULTIMED has the capability to analyze the impact of uncertainty and variability in the model inputs on the model outputs (concentrations at specified points in the multimedia environment), using the Monte Carlo simulation technique. The major functions currently performed by this model include: o Allocation of default values to some input parameters/variables. o Reading of the input data files. o Echo of input data to output files. o Derivation of some parameters, if specified by the user. o Depending on user-selected options: - simulation of leachate flux emanating from the source - simulation of unsaturated zone flow and transport - simulation of saturated zone transport only - computation of in-stream concentrations due to contaminant loading assuming complete interception of a plume in the saturated zone - computation of the rate of contaminant emission from the waste disposal unit into the atmosphere - simulation of dispersion of the contaminants in the atmosphere o Generation of random input values for Monte Carlo simulations. o Performance of statistical analyses of Monte Carlo simulations. o Writing the concentrations at specified receptors to output files for deterministic runs. In the Monte Carlo mode, writing the cumulative frequency distribution and selected percentiles of concentrations at receptors to output files. o Printing the values of randomly generated input parameters and the computed concentration values for each Monte Carlo run. The pre- and postprocessor for MULTIMED have been developed using the ANNIE Interaction Development Environment (ANNIE-IDE) (Kittle et al., 1989). Consequently, the construction of input and the analysis of output is standardized in terms of screen formats, movement within and between screens, methods of entering data, seeking on-line assistance, and invoking commands. [(Salhotra et al., 1990) and (Sharp-Hansen et al., 1990)] __________________________________________________________________ DOCUMENTATION Copies of the following documents are included on the distribution diskette set (See FILE NAME AND CONTENT and MINIMUM FILE CONFIGURATION sections): Document Name File Name _____________ _________ MULTIMED System Installation Quick README.1ST Reference MULTIMED System Detailed Installation README.TOO and Execution ANNIE-IDE System Specification File TERM_DAT.TXT (TERM.DAT) Quick Reference Guide These ASCII text files can be displayed on the monitor screen by using the DOS TYPE command (e.g., TYPE README.1ST) or printed using the DOS PRINT command (e.g., PRINT README.1ST). __________________________________________________________________ DISTRIBUTION DISKETTES Included are five, 5.25 inch (360k, DS/DD), or two, 3.5 inch (1.44Mb, DS/HD) PC DOS (Disk Operating System) formatted diskettes containing version 1.01 of the Multimedia Exposure Assessment Model (MULTIMED). Also contained on the diskette set are version 1.01 of the Interactive Data Preprocessor Program for MULTIMED (PREMED) and the Interactive Graphics Postprocessor Program for MULTIMED (POSTMED, version 1.01). This model and programs are designed for the IBM PC family of microcomputers or compatible systems running under version 3.30 of the PC Disk Operating System (PC DOS--see DEVELOPMENT SYSTEM section). Properly configured, this model and programs and their support files and programs can be executed under DOS or MS-DOS 2.12 and later versions, DOS 3.xx, or DOS 4.0x. All files on the distribution diskettes were placed on each diskette with the DOS COPY command and are stored in COPY format. In order to begin the installation of the MULTIMED model and the PREMED and POSTMED programs and related files to a hard disk, use the DOS COPY command to transfer the files. See the DETAILED INSTALLATION INSTRUCTIONS section for further details. NOTE: The contents of the distribution diskettes can be copied to another set of "backup" diskettes using the DOS DISKCOPY command (see DOS Reference Manual for command application and use). The "backup" diskettes must be the same size and storage density as the original source diskettes. The following FILE NAME AND CONTENT section provides a brief functional description of each file by name or file name extension type. Other sections in this document contain information about o system development tools used to build the microcomputer release of the MULTIMED model and the PREMED and POSTMED programs o the recommended hardware and software configuration for the execution of the model and all support programs o graphics support o detailed installation o program execution o minimum file configuration o sample run times o program modification o technical support __________________________________________________________________ FILE NAME AND CONTENT The files on the distribution diskettes (that the user will copy to the hard disk) exist in both a decompressed and compressed format to save diskette space and file transfer time. This section contains descriptions of compressed and decompressed files. The DETAILED INSTALLATION INSTRUCTIONS section explains the procedure and commands used to decompress (extract) and restore each file to its original name and size in order to place the MULTIMED model and the PREMED and POSTMED programs and all related files in a useable format on the hard disk. For comparison purposes, the original date and time of creation are also restored with each file. ** Files Not Compressed ** The following files are not in a compressed storage format. These files are stored in DOS COPY format. Except where noted, these files are ASCII text files that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. README.1ST - Installation and execution quick reference guide. This document is an ASCII text file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. README.TOO - Installation, execution, and general support guide. This document is an ASCII text file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. INSTALL.BAT - A DOS batch command file used to decompress and install the MULTIMED model and the PREMED and POSTMED programs and all related files and support DOS batch command files on the hard disk. During execution, this program prompts the user to determine if Graphical Kernel System (henceforth referred to as "GKS") graphics capability is available to support the POSTMED program. See GRAPHICS SUPPORT section for further detail. INSTALLC.BAT - A DOS batch command file that can be used to decompress and install on the hard disk 1) the MULTIMED, PREMED, and POSTMED FORTRAN source code files and 2) the compile and link edit command files for MULTIMED, PREMED, and POSTMED (see DETAILED INSTALLATION INSTRUCTIONS section). These files are not required to execute the MULTIMED model or the PREMED or POSTMED programs as received on the distribution diskette set. HELP.BAT - A DOS batch command file that can be used to provide assistance with the execution and application of DOS batch command files that support the MULTIMED model system and/or the PREMED/POSTMED program system specification file, TERM.DAT. This command displays selected program documentation on the monitor screen. To execute, type HELP cmdname or HELP TERM.DAT at the DOS system prompt, then press the key. The parameter cmdname must be a valid DOS batch command file name. Examples: C:\MULTIMED> HELP INSTALL ------------ C:\MULTIMED> HELP CLPREMED ------------- C:\MULTIMED> HELP COMPLINK ------------- C:\MULTIMED> HELP TERM.DAT ------------- TERM_DAT.TXT - ANNIE-IDE System Specification File (TERM.DAT) Quick Reference Guide. ANSWER.COM - Executable code file used by the INSTALL DOS batch command file to write screen prompts and read the user response entered from the keyboard. Do NOT attempt to type or print this file using the DOS TYPE or PRINT commands. ** Compressed Files ** PKZ110.EXE - A self-extracting executable program containing the programs and documentation for the PKZIP, PKUNZIP, and PKSFX (copyright 1989 by PKware, Inc.) compression programs used to build the microcomputer distribution version of the MULTIMED model system. This file can be used, copied, and distributed for NONCOMMERCIAL use if o no fee is charged for use, copying, or distribution o it is not modified in any way Consult the file ORDER.DOC within the file PKZ110.EXE for more information -- or write or call PKware, Inc. If the user finds these compression programs fast, easy and convenient to use, register the copy with: PKware, Inc. 7545 North Port Washington Road Suite 205 Glendale, WI 53217-3422 414/352-3670 NOTE: The execution of the PKZ110.EXE program is not required in order for the user to be able to use the MULTIMED model system. WARNING: The DOS batch command files INSTALL.BAT and INSTALLC.BAT are the only files that should be executed to decompress and extract the contents of the files PREMDRUN.ZIP, MULTMRUN.ZIP, POSTMRUN.ZIP and MULTMFOR.ZIP. Do NOT decompress these files with any other command file. Do NOT attempt to display on the monitor screen or print these files using the DOS TYPE or PRINT commands. See the DETAILED INSTALLATION INSTRUCTIONS section for instructions on decompressing the contents of these files. PREMDRUN.ZIP - A compressed storage file containing the PREMED program and run time support files. See the subsection below entitled "Decompressed Files from PREMDRUN.ZIP" for a detailed listing of files by name. See the DETAILED INSTALLATION INSTRUCTIONS section for instructions on decompressing the contents of this file. WARNING: The DOS batch command file INSTALL.BAT is the only file that should be executed to decompress and extract the contents of the PREMDRUN.ZIP file. Do NOT decompress this file with any other command file. Do NOT attempt to display on the monitor screen or print the PREMDRUN.ZIP file using the DOS TYPE or PRINT commands. This file is in a compressed format and contains the following files: o PREMED.BAT - DOS batch command used to execute the PREMED program (see ROUTINE EXECUTION section). o PREMEDPC.EXE - Executable task image file for the PREMED program. WARNING: The PREMEDPC.EXE task image should only be executed using the DOS batch command file provided (PREMED.BAT). o MESSAGE.WDM - Screen definition file read by the PREMED and POSTMED programs and used to produce and display on the monitor screen the text, application program menus, and data entry screens. This is an unformatted, direct access file with a logical record length of 2,048 bytes. o TERM.DAT - ANNIE-IDE system specification (terminal definition) file used by the PREMED and POSTMED programs. See the file TERM_DAT.TXT for further information on the modification and/or use of the TERM.DAT file. o SUBD.DEF - Default settings initialization file for PREMED Subtitle D application. o DETER.LOG - Interactive tutorial session command file for producing a deterministic MULTIMED input sequence (see ROUTINE EXECUTION section). o MONTE.LOG - Interactive tutorial session command file for producing a Monte Carlo MULTIMED input sequence (see ROUTINE EXECUTION section). o TESTD.INP - MULTIMED input data file used by the DETER.LOG interactive tutorial session. o TESTM.INP - MULTIMED input data file used by the MONTE.LOG interactive tutorial session. MULTMRUN.ZIP - A compressed storage file containing the executable task image file and associated run time files for the MULTIMED model. See the subsection below entitled "Decompressed Files from MULTMRUN.ZIP" for a detailed listing of files by name. See the DETAILED INSTALLATION INSTRUCTIONS section for instructions on decompressing the contents of this file. WARNING: The DOS batch command file INSTALL.BAT is the only file that should be executed to decompress and extract the contents of the MULTMRUN.ZIP file. Do NOT decompress this file with any other command file. Do NOT attempt to display on the monitor screen or print the MULTMRUN.ZIP file using the DOS TYPE or PRINT commands. This file is in a compressed format and contains the following files: o MULTIMED.EXE - Executable task image file for the MULTIMED model. o RMFORT.ERR - Run time error message library file for Ryan-McFarland FORTRAN (RMFORT) (see DEVELOPMENT SYSTEM section). o *.IN - Test input data files to test the installation of the MULTIMED model (see DETAILED INSTALLATION INSTRUCTIONS section). o *.OUT - Test output listing files produced by the MULTIMED model using a corresponding test input data file (*.IN--see ROUTINE EXECUTION section). POSTMRUN.ZIP - A compressed storage file containing the POSTMED program and associated run time files. See the subsection below entitled "Decompressed Files from POSTMRUN.ZIP" for a detailed listing of files by name. See the DETAILED INSTALLATION INSTRUCTIONS section for instructions on decompressing the contents of this file. WARNING: The DOS batch command file INSTALL.BAT is the only file that should be executed to decompress and extract the contents of the POSTMRUN.ZIP file. Do NOT decompress this file with any other command file. Do NOT attempt to display on the monitor screen or print the POSTMRUN.ZIP file using the DOS TYPE or PRINT commands. This file is in a compressed format and contains the following files: o POSTMED.BAT - DOS batch command used to execute the POSTMED program (see ROUTINE EXECUTION section). o POSTMEDC.EXE - Executable task image file for the POSTMED program. WARNING: The POSTMEDC.EXE task image should only be executed using the DOS batch command file provided (POSTMED.BAT). o FONT101.TBL - A GKS font definition file used by the POSTMED program to generate screen graphics. o GKSCGI.CFG - GKS CGI device driver configuration file used by the INSTALL DOS batch command file to build the C:\GKS\CGI.CFG configuration file for the POSTMED program. o DRIVERS.EXE - The GKS CGI terminate and stay resident (TSR) initialization program (executable task image file). o TERM_GKS.DAT, TERMNGKS.DAT - ANNIE-IDE system specification (terminal definition) files used by the INSTALL DOS batch command file to modify the TERM.DAT terminal definition file used by the PREMED and POSTMED programs. o POSTTEST.DAT - Sample input data file to test the installation of the POSTMED program. MULTMFOR.ZIP - A compressed storage file that contains the FORTRAN source code files and compile and link DOS batch command files for the MULTIMED model and the PREMED and POSTMED programs. These files are NOT needed to execute and apply the MULTIMED model (see MINIMUM FILE CONFIGURATION section). Note that these files are not required in order for the user to be able to use the MULTIMED model. This file can be deleted with the DOS delete command (DEL MULTMFOR.ZIP) if the user does not wish to store these files on the hard disk along with the run time files needed by the MULTIMED model. WARNING: The DOS batch command file INSTALLC.BAT is the only file that should be executed to decompress and extract the contents of the MULTMFOR.ZIP file. Do NOT decompress this file with any other command file. Do NOT attempt to display on the monitor screen or print the MULTMFOR.ZIP file using the DOS TYPE or PRINT commands. This file is in a compressed format and contains the following files: o COMPLINK.BAT - DOS batch command file that can be used to compile and link edit the MULTIMED FORTRAN source code files (*.CMN and *.FOR) in the MULTIMED\MULTMFOR sub-directory. o MULTIMED.LNK - Link edit command file called and executed by the compile and link DOS batch command file COMPLINK.BAT. o CLPREMED.BAT - DOS batch command file that can be used to compile and link edit the PREMED FORTRAN source code files (*.CMN, *.INC, and *.FOR) in the MULTIMED\MULTMFOR\PREMDFOR sub- directory. o PREMED.LNK - Link edit command file called and executed by the compile and link DOS batch command file CLPREMED.BAT. o CLPOSTM.BAT - DOS batch command file that can be used to compile and link edit the POSTMED FORTRAN source code files (*.F77) in the MULTIMED\MULTMFOR\POSTMFOR sub-directory. o POSTMED.LNK - Link edit command file called and executed by the compile and link DOS batch command file CLPOSTM.BAT. NOTE: The following files are installed in sub- directories created by the INSTALLC.BAT DOS batch command file. See the subsection below entitled "Decompressed Files from MULTMFOR.ZIP" for a detailed description of the sub-directories and files. o *.FOR and *.F77 - FORTRAN source code files for the MULTIMED model and the PREMED and POSTMED programs. o *.CMN and *.INC - FORTRAN source code include files for the MULTIMED model and the PREMED and POSTMED programs. o *.SEQ - ANNIE-IDE screen definition files for the PREMED and POSTMED programs. ** Decompressed Files from PREMDRUN.ZIP ** PREMED.BAT - DOS batch command file used to execute the PREMED program (see ROUTINE EXECUTION section). To execute, type PREMED at the DOS system prompt, press the key, then select from and follow the menus and data entry field prompts displayed on the monitor screen. PREMEDPC.EXE - Executable task image file for the PREMED program. WARNING: The PREMEDPC.EXE task image should only be executed using the DOS batch command file provided (PREMED.BAT). MESSAGE.WDM - Screen definition file read by the PREMED and POSTMED programs and used to produce and display on the monitor screen the text, application program menus, and data entry screens. This is an unformatted, direct access file with a logical record length of 2,048 bytes. TERM.DAT - ANNIE-IDE system specification (terminal definition) file used by the PREMED and POSTMED programs. The ANNIE-IDE library files used to build the PREMED program contain parameters that can be system dependent. These parameters have a default value for a given system. The defaults are in the primary message file, MESSAGE.WDM. However, default values can be overridden by the user by using a TERM.DAT file in the \MULTIMED sub- directory (see DETAILED INSTALLATION INSTRUCTIONS section). See the file TERM_DAT.TXT for further information on the modification and/or use of the TERM.DAT file. SUBD.DEF - Default settings initialization file for PREMED Subtitle D application. DETER.LOG - Interactive tutorial session command file for producing a deterministic MULTIMED input sequence (see ROUTINE EXECUTION section). MONTE.LOG - Interactive tutorial session command file for producing a Monte Carlo MULTIMED input sequence (see ROUTINE EXECUTION section). TESTD.INP - MULTIMED input data file used by the DETER.LOG interactive tutorial session. TESTM.INP - MULTIMED input data file used by the MONTE.LOG interactive tutorial session. ** Decompressed Files from MULTMRUN.ZIP ** NOTE: The symbol "" represents pressing the or carriage return key. Responses and key strokes that can be typed by the user are underlined. MULTIMED.EXE - Executable task image file for the MULTIMED model. RMFORT.ERR - Run time error message library file for Ryan-McFarland FORTRAN (RMFORT) (see DEVELOPMENT SYSTEM section). TEST1.IN - Sample input data files to test the installation of TEST2.IN the MULTIMED model. To test the installation, TEST3.IN execute the MULTIMED model using each file as the TEST6.IN name of the input file (see DETAILED INSTALLATION INSTRUCTIONS section). The model interactively prompts the user for the names of the output and input files. NOTE: An input file name entered by the user during the execution of the MULTIMED or model must be a unique and valid DOS file name. The input file name must also be a valid MULTIMED input data file name -- either furnished with the distribution package (see FILE NAME AND CONTENT section) or designated by the user. The data will be processed and executed in the run of the model. Remember, a DOS file name can be from 1 to 8 characters and can have an optional 1 to 3 character file name extension. NOTE: See the explanation of the *.OUT files for a procedure to compare the contents of an output file produced on the users system to an output file provided on the distribution diskette set (*.OUT). The MULTIMED model interactively prompts the user for the output file name. TEST1.OUT - Output listing files produced by the MULTIMED model TEST2.OUT using the test input data files. After executing TEST3.OUT the MULTIMED model with each test data file, compare TEST6.OUT the contents of the output file produced (example: TEST1.RUN) with the corresponding *.OUT output file provided (example: TEST1.OUT). To compare file contents, use the DOS (COMP) or MS DOS (FC) file compare command. Example MULTIMED interactive execution sequence: CUE USER RESPONSE ___ _____________ - Run the model - MULTIMED -------- - Select input file at prompt - TEST1.IN -------- - Select output file name at prompt - TEST1.RUN --------- - Compare the output file produced to one supplied - COMP TEST1.RUN TEST1.OUT ------------------------ ** Decompressed Files from POSTMRUN.ZIP ** POSTMED.BAT - DOS batch command file used to execute the POSTMED program (see ROUTINE EXECUTION section). To execute, type POSTMED at the DOS system prompt, press the key, then select from and follow the menus and data entry field prompts displayed on the monitor screen. POSTMEDC.EXE - Executable task image file for the POSTMED program. WARNING: The POSTMEDC.EXE task image should only be executed using the DOS batch command file provided (POSTMED.BAT). FONT101.TBL - A GKS font definition file for generating screen graphics in the POSTMED program. GKSCGI.CFG - GKS CGI device driver configuration file used by the INSTALL DOS batch command file to build the C:\GKS\CGI.CFG configuration file. The file C:\GKS\CGI.CFG is used by the POSTMED program if graphics capabilities are available (see INSTALL.BAT file, DETAILED INSTALLATION INSTRUCTIONS section, and GRAPHICS SUPPORT section). DRIVERS.EXE - The GKS CGI terminate and stay resident (TSR) initialization program (executable task image file). TERM_GKS.DAT - ANNIE-IDE system specification (terminal TERMNGKS.DAT definition) files used by the INSTALL DOS batch command file to modify the TERM.DAT terminal definition file used by the PREMED and POSTMED programs. The ANNIE-IDE library files used to build the POSTMED program contain parameters that can be system dependent. These parameters have a default value for a given system. The defaults are in the primary message file, MESSAGE.WDM. However, default values can be overridden by the user by using a TERM.DAT file in the sub-directory (see DETAILED INSTALLATION INSTRUCTIONS section). POSTTEST.DAT - Sample input data file to test the installation of the POSTMED program. To test the installation, execute the POSTMED program using this file as the name of the input file (see DETAILED INSTALLATION INSTRUCTIONS section). ** Decompressed Files from MULTMFOR.ZIP ** In addition to decompressing a number of files into the \MULTIMED sub-directory, the INSTALLC.BAT DOS batch command file creates three sub-directories within the \MULTIMED sub-directory. These sub-directories are for the FORTRAN source code. The three sub- directories are: 1. \MULTIMED\MULTMFOR - MULTIMED model FORTRAN source code 2. \MULTIMED\MULTMFOR\PREMDFOR - PREMED program FORTRAN source code 3. \MULTIMED\MULTMFOR\POSTMFOR - POSTMED program FORTRAN source code Files from MULTMFOR.ZIP placed in \MULTIMED COMPLINK.BAT - DOS batch command file that can be used to compile and link edit the MULTIMED model FORTRAN source code files (*.CMN and *.FOR) in the MULTMFOR sub- directory to incorporate changes made in the source code files by the user. See the program listing for complete in-code documentation. The execution of this command produces a new executable task image file (MULTIMED.EXE) for the MULTIMED model. This command file only needs to be executed if changes have been made in the FORTRAN source code, not input data files. To execute, type COMPLINK at the DOS system prompt, then press the key. MULTIMED.LNK - PLINK86 Plus link edit command file called and executed automatically by the compile and link edit DOS batch command file COMPLINK.BAT. CLPREMED.BAT - DOS batch command file that can be used to compile and link edit the PREMED program FORTRAN source code files (*.CMN, *.INC, and *.FOR) in the MULTMFOR\PREMDFOR sub-directory to incorporate changes made in the source code files by the user. See the program listing for complete in-code documentation. The execution of this command produces a new executable task image file (PREMEDPC.EXE) for the PREMED program. This command file only needs to be executed if changes have been made in the FORTRAN source code, not input data files. To execute, type CLPREMED at the DOS system prompt, then press the key. NOTE: This command file assumes that the ANNIE Interactive Development Environment (ANNIE-IDE) tool kit libraries are installed on the users microcomputer hard disk drive. For further information on the ANNIE-IDE package, call or write the CEAM at the address at the beginning of this document. PREMED.LNK - PLINK86 Plus link edit command file called and executed automatically by the compile and link edit DOS batch command file CLPREMED.BAT. CLPOSTM.BAT - DOS batch command file that can be used to compile and link edit the POSTMED program FORTRAN source code files (*.F77) in the MULTMFOR\POSTMFOR sub- directory to incorporate changes made in the source code files by the user. See the program listing for complete in-code documentation. The execution of this command produces a new executable task image file (POSTMEDC.EXE) for the POSTMED program. This command file only needs to be executed if changes have been made in the FORTRAN source code, not input data files. To execute, type CLPOSTM at the DOS system prompt, then press the key. NOTE: This command file assumes that the ANNIE Interactive Development Environment (ANNIE-IDE) tool kit libraries are installed on the users microcomputer hard disk drive. For further information on the ANNIE-IDE package, call or write the CEAM at the address at the beginning of this document. POSTMED.LNK - PLINK86 Plus link edit command file called and executed automatically by the compile and link edit DOS batch command file CLPOSTM.BAT. Files from MULTMFOR.ZIP placed in \MULTIMED\MULTMFOR *.CMN - FORTRAN source code "include" files containing FORTRAN COMMON block declarations for the MULTIMED model. These files are automatically included or "copied" into the appropriate FORTRAN source code file (*.FOR) during compilation. *.FOR - The FORTRAN source code files for the MULTIMED model, version 1.01. Files from MULTMFOR.ZIP placed in \MULTIMED\MULTMFOR\PREMDFOR *.CMN - FORTRAN source code "include" files containing *.INC FORTRAN COMMON block declarations for the PREMED program. These files are automatically included or "copied" into the appropriate FORTRAN source code file (*.FOR) during compilation. *.FOR - The FORTRAN source code files for the PREMED program, version 1.01. *.SEQ - Screen definition files containing PREMED and POSTMED run time message text, application program menus, and data entry screens. These formatted files are sequential versions of the messages contained in the direct access screen definition file (MESSAGE.WDM) used by the PREMED and POSTMED programs. Files from MULTMFOR.ZIP placed in \MULTIMED\MULTMFOR\POSTMFOR *.F77 - The FORTRAN source code files for the POSTMED program, version 1.01. ** Files Created by Installation Batch Command File ** KERNEL.SYS - A GKS device definition file used by the POSTMED program to determine the available device drivers. ** Special Run Time File NOTE: The following type of file is not distributed on the distribution diskette set. It is created automatically when the user executes either the MULTIMED or model. __________________________________________________________________ DEVELOPMENT SYSTEM The following list describes the language and program development tools used by the Center for Exposure Assessment Modeling to build version 1.01 of the microcomputer implementation of the MULTIMED model and version 1.01 of PREMED and version 1.01 of the POSTMED program. Also shown are the recommended minimum hardware and software configuration and the recommended \CONFIG.SYS configuration/environment file statements for the implementation and execution of this model and programs and all related support files and programs. Make sure that the IBM PC or compatible system has these statements in the \CONFIG.SYS file, and re-boot the system to implement these changes in the root directory before attempting to install or use the model and programs. Development System: Language: FORTRAN 77 and Assembler Operating System: DOS version 4.01. The MULTIMED model and PREMED and POSTMED programs also work with 2.12 and later versions and PC DOS or MS-DOS 3.2x and 3.3x. Compiler: Ryan-McFarland FORTRAN RMFORT, version 2.45 Link Editor: POLYTRON Corporation (SAGE Software) PLINK86 Plus, version 2.24 Graphics: GSS*GKS, version 2.14 Overlay Structure: Yes. See the files MULTIMED.LNK, PREMED.LNK, and POSTMED.LNK included with source code files for up and down FORTRAN subprogram calling sequences and structures. Storage Requirements: (k=1,024; M=1,048,576) Random Access Memory: (approximate minimum free bytes needed to execute each program) MULTIMED - 502k PREMED - 502k POSTMED - 505k (includes GKS graphics) Use DOS CHKDSK command to verify bytes free in RAM memory. See paper entitled "PROGRAM EXECUTION AND THE DOS OPERATING ENVIRONMENT" by David Disney (October 1990) for further information on RAM requirements. Diskette Drive: Required for installation only. Hard Disk Drive: 20M byte drive (minimum) Installation Size: Run Time: Approx. 5.10M bytes max. FOR Code: Approx. 1.10M bytes max. ----- Total 6.20M bytes (Total does not include *.OBJ and ANNIE-IDE programmer tool kit files if all programs are compiled and linked.) Run time size: Up to approximately 2.80M bytes (without *.ZIP files) plus space for user input data files, output, and temporary files produced by the model and programs (see MINIMUM FILE CONFIGURATION section). Numerical Coprocessor: Optional for MULTIMED model and PREMED program. These executable task image files contain coprocessor emulation code. However, coprocessor will greatly improve model and program execution speed. Coprocessor required for POSTMED program. \CONFIG.SYS Statements: For a detailed explanation of the following configuration file statements, see paper entitled "PROGRAM EXECUTION AND THE DOS OPERATING ENVIRONMENT" by David Disney (October 1990) that is distributed with the MULTIMED system package. BREAK=ON BUFFERS=20 FILES=20 DEVICE=C:\ANSI.SYS - and - SHELL=C:\COMMAND.COM C:\ /E:1024 /P - for DOS 3.2x, 3.3x, and 4.01 - - or - SHELL=C:\COMMAND.COM C:\ /E:50 /P - for DOS 3.1x and earlier versions - (Use DOS VER command to determine DOS version number.) __________________________________________________________________ GRAPHICS SUPPORT The Graphical Kernel System (GKS) is an internationally accepted standard for computer graphics programming. GKS is a hardware- independent, language-independent, device-independent, application interface for two-dimensional graphics output and interactive graphics input, providing maximum portability of applications. GKS contains all basic functions for interactive and non-interactive graphics on a wide range of graphics equipment. GKS is implemented through a subroutine package that can be called from a high-level application written in FORTRAN, such as the POSTMED program. The POSTMED program is capable of displaying graphics output using the Graphic Software Systems' GSS*GKS and GSS-CGI device driver and graphics software system. These items are licensed software products that must be licensed (i.e., purchased) by the user--see the End User License Agreement below. NOTE: The POSTMED program cannot plot graphs WITHOUT GKS display graphics capability. The INSTALL DOS batch command file prompts the user to indicate if GKS graphics is installed and supported on the users microcomputer as follows: Is GKS graphics installed and supported on this PC (Y/N) (Enter=N)? If the user responds with "Y" or "y" (yes) to this prompt, the INSTALL DOS batch command file allows the user to support the POSTMED program with monitor (display) output graphics capability. Otherwise, if the user responds with "N" or "n" (no) to this prompt, the POSTMED program can only produce summary plot data in an ASCII (text) file. Installing the POSTMED program to support graphics output assumes that the user has the appropriate hardware device and that the user has licensed the appropriate GKS support software. See the End User License Agreement below for purchasing the appropriate GKS support software. ***** Beginning of End User License Agreement ***** ################################################################# # NOTICE TO USER: READ THIS AGREEMENT CAREFULLY! # ################################################################# # # # Graphic Software Systems' GSS*GKS and GSS-CGI device # # drivers and graphics software system product, as needed # # to support POSTMED program graphics capability, is licensed # # (not sold). Opening the GKS package implies acceptance # # of the terms and conditions of this license. # # # # If the user does not accept the terms of this license, # # the unopened GKS product package can be returned to the # # Seller from which it was purchased, along with all # # associated materials, for a monetary refund. # # # ################################################################# $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ $ GSS GKS/CGI INSTALLATION NOTICE TO USER: $ $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ $ $ $ To install and use GKS/CGI support in the POSTMED program, $ $ the user must first license the proper graphics controller $ $ and device driver from Graphic Software Systems, Inc. $ $ $ $ When ordering, the user must specify the name of the manu- $ $ facturer and the model number of the monitor (display) the $ $ user selects to support the POSTMED program. This includes $ $ the following device: $ $ o Display Controller - this is the board that $ $ controls the monitor (screen), NOT the monitor $ $ itself $ $ $ $ Prices begin at $75.00. $ $ $ $ Write or call GSS' Telemarketing Department for further $ $ information. $ $ $ $ Graphic Software Systems, Inc. $ $ 9590 SW Gemini Drive $ $ Beaverton, Oregon 97005 $ $ 503/641-2200 $ $ $ $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1. DEFINITIONS A. "GSS" -- Graphic Software Systems, Inc. P.O. Box 4900 Beaverton, Oregon 97005 the author and owner of the copyright of the GSS GKS/CGI computer program product. B. "COMPUTER" -- the single computer on which the GKS/CGI program is used. C. "SOFTWARE" -- the set of computer programs in the GKS/CGI package, regardless of the form in which it is applied by the user. D. "LICENSE" -- this Agreement and the rights and obligations that it creates under the United States Copyright Act and the laws of the State of Oregon. 2. LICENSE GSS grants the user the right to use a purchase copy of the SOFTWARE as long as the user complies with the terms of this LICENSE. The user can use the SOFTWARE and the associated documentation only in connection with a single COMPUTER. The user can physically move the SOFTWARE from one COMPUTER to another, provided that the SOFTWARE is used in connection with only one COMPUTER at a time. If the user no longer has the right to use the SOFTWARE, the user must either destroy the SOFTWARE or return it to GSS. GSS shall have the right to terminate this LICENSE if the user violates any of its provisions. 3. TRANSFER OR REPRODUCTION If obtained (i.e., licensed), the user can make up to two copies of the SOFTWARE for backup purposes only, as long as a label is placed on the outside of each backup diskette showing the GSS copyright and trademark notices in the same form as the original copy. When using a COMPUTER with a hard disk, one copy of the SOFTWARE can be installed on the hard disk as long as that copy is removed when the SOFTWARE is being used on another COMPUTER. The user can not: o make or authorize any other copies of the SOFTWARE o sublicense, rent, assign, or transfer the LICENSE or the SOFTWARE to anyone else o provide use of the SOFTWARE through a time sharing service or network of computers to users who are not individually licensed to use the SOFTWARE The user must understand that unauthorized reproduction or unauthorized transfer of copies of the SOFTWARE can be a crime, as well as subjecting the user to damages and attorney's fees. 4. ADAPTATIONS Any part of the SOFTWARE that the user merges with other software is still the property of GSS. In the event this is terminated, the user cannot use any part of the SOFTWARE even if it has been merged with other software. The user agrees to take reasonable steps to protect GSS' SOFTWARE from theft or use contrary to this LICENSE. The user cannot modify, disassemble, or reverse-engineer the SOFTWARE. 5. LIMITED WARRANTY The SOFTWARE, associated manuals, and reference materials will be provided "as is", without warranty as to their performance, merchantability, or fitness for any particular purpose. The entire risk as to the results and performance of the GKS/CGI SOFTWARE is assumed by the user. GSS shall not be liable for indirect, special, or consequential damages resulting from the use of GKS/CGI SOFTWARE product(s). Some states do not allow the exclusion or limitation of implied warranties or incidental or consequential damages, so the foregoing limitations might not apply to the user. This warranty gives the user specific legal rights. The user may also have other rights that vary from state to state. 6. GENERAL This is the complete and exclusive Agreement between the user and GSS. If the SOFTWARE is purchased by the user, this Agreement supersedes any proposal or prior agreement, oral or written, and any other communications between GSS and the user relating to the subject matter of this Agreement. ***** End of End User License Agreement ***** __________________________________________________________________ DETAILED INSTALLATION INSTRUCTIONS NOTE: The symbol "" represents pressing the or carriage return key. Responses and key strokes that can be typed by the user are underlined with the hyphen character (-). This section provides a detailed step-by-step listing of the installation commands and procedures, and a text description of each step. Included in this procedure are: o a detailed description of required and optional DOS commands o installation steps for users capable of utilizing GKS o optional installation steps to decompress all MULTIMED model FORTRAN source code files and DOS compile and link command files from a compressed transfer and storage file. To install the MULTIMED model and the PREMED and POSTMED programs on an IBM PC or compatible microcomputer system, execute the following step-by-step instructions to transfer the contents of all CEAM distribution diskettes to a hard disk drive and decompress the model and programs and all support files and programs. NOTE: It is important to notice that the installation instructions refer to the floppy diskette drive as "A:" and the hard disk drive as "C:". Since it is possible for machines to be configured differently, the user can make the appropriate substitution(s) when reference is made to drive(s) A: and/or C:. However, if the user has GKS, the MULTIMED installation procedure and command file assume that the GKS software is on drive C: in the \GKS sub-directory (i.e., C:\GKS). Remember, "" represents pressing the Enter or carriage return key and is not to be typed by the user. Character and/or numeric responses that can be typed by the user are underlined with the hyphen character (-). First, create and/or edit the configuration/environment system file \CONFIG.SYS on the "boot" or start-up disk drive to contain the statements suggested in the DEVELOPMENT SYSTEM section. Remember, these changes will not be in effect until the system is re-booted (i.e. power off/power on or use the warm boot procedure by holding down the keys at the same time and pressing the key). Step Number and Description Command at DOS Prompt ___________________________ _____________________ 1 - Set the default drive to the C: hard disk: -- 2 - Create a MULTIMED sub-directory MKDIR \MULTIMED from the root directory: --------------- NOTE: The DOS Make Directory command MKDIR can be abbreviated with MD. 3 - Change default directory to the CHDIR \MULTIMED MULTIMED sub-directory: --------------- NOTE: The DOS Change Directory command CHDIR can be abbreviated with CD. 4 - Request verification of VERIFY ON disk-to-disk copy (optional): --------- 5 - Transfer files from the COPY A:\*.* C:*.* supplied distribution diskettes in ----------------- drive "A:" to the hard disk (drive "C:"). Make sure that there are at least 5.1M bytes of free space on drive C: for the run time files: NOTE: Repeat step 5 for each distribution diskette. 6 - Remove verification of copy VERIFY OFF (optional): ---------- 7 - Install run time support files INSTALL and decompress all essential ------- MULTIMED, PREMED, and POSTMED run time files and selected FORTRAN source code and support files from the compressed files: 8 - Refer to GRAPHICS SUPPORT section before continuing. - If user has GKS, go to step 9. - If user does NOT have GKS, go to step 10. 9 - Edit the GKS device driver C: configuration file C:\GKS\CGI.CFG -- where "edit" is the name of a text CD \GKS or file editor that saves files in ------- ASCII (text) format (optional): edit CGI.CFG ------------ C: -- CD \MULTIMED ------------ 10- Decompress all MULTIMED, INSTALLC PREMED, and POSTMED FORTRAN source -------- code files and compile and link command files from the compressed file (optional): 11- Execute the PREMED program and PREMED follow the menu and data entry ------ screen prompts and instructions. NOTE: To execute an interactive tutorial session a) press the <@> key (e.g., <2>) immediately after starting the PREMED program. A prompt box will be displayed at the top right-hand corner of the screen. b) at the prompt "Enter macro name," type the file name DETER.LOG or MONTE.LOG c) press the key d) follow the tutorial instructions (inserted/overlayed) on the monitor screen. 12- Execute the MULTIMED MULTIMED model using the test input data -------- files provided. The RUN TIME AND PERFORMANCE section contains a table that shows the file names for each of these input data files. 13- Compare test output file produced COMP TEST1.RUN TEST1.OUT (example: TEST1.RUN - as selected ------------------------ by the user) with the one supplied (TEST1.OUT). See the FILE NAME AND CONTENT and ROUTINE EXECUTION sections. NOTE: For MS DOS, the file compare command is "FC". 14- To continue the installation and testing of the MULTIMED model, execute steps 12 and 13 above for each test data file provided on the distribution diskettes. The RUN TIME AND PERFORMANCE section contains a table that shows the model name, file names, and options that are appropriate to use with each data file. 15- Refer to GRAPHICS SUPPORT section before continuing. - If user has GKS, go to step 16. - If user does NOT have GKS, skip step 16. 16- Execute the POSTMED program and POSTMED follow the menu and data entry ------- screen prompts and instructions. A valid plot data file is included as POSTTEST.DAT. __________________________________________________________________ ROUTINE EXECUTION NOTE: The symbol "" represents pressing the or carriage return key. Responses and key strokes that can be typed by the user are underlined with the hyphen character (-). 1) Complete the installation instructions shown in the DETAILED INSTALLATION INSTRUCTIONS section to make all models, programs, and related files resident on the hard disk drive (usually designated as "C:") and modify the \CONFIG.SYS system environment file. This step needs to be completed only once for a given installation. 2) Set the default drive to the hard disk containing the MULTIMED sub-directory: (i.e., hard disk "C:") A:\> C: -- 3) Change the DOS default sub-directory to the MULTIMED sub-directory by using the DOS CD (change directory) command at the DOS system prompt: C:\> CD \MULTIMED ------------ 4) To execute the PREMED program, type: C:\MULTIMED> PREMED ------ Follow the menu and parameter options presented on the display screen. Execution of this program is optional. However, prior to execution, the MULTIMED model will require input data files that have been built either with PREMED or manually using a word processor or text editor that can save a file in ASCII (text) format. NOTE: To link the Ryan-McFarland RMFORT FORTRAN run time error message library to the MULTIMED model, type the following command at the DOS system prompt prior to executing either model: SET \RMFORT.ERR=C:\MULTIMED\RMFORT.ERR where "C:" is the disk drive designation where the MULTIMED model is installed. For example: C:\MULTIMED> SET \RMFORT.ERR=C:\MULTIMED\RMFORT.ERR -------------------------------------- 5) To execute the MULTIMED model, type: C:\MULTIMED> MULTIMED -------- The model will begin prompting the user for information needed to execute the model. The model will prompt the user one line at a time for the information that follows: Type name of input file: TEST1.IN -------- Type name of output file: TEST1.RUN --------- 7) To execute the POSTMED program, type: C:\MULTIMED> POSTMED ------- Follow the menu and parameter options presented on the display screen. Execution of this program is optional. However, prior to execution, this program requires a plot data file. A valid plot data file, POSTTEST.DAT, is included. This file can be used or a new one can be generated by executing the MULTIMED model. 8) The response entered by the user for any file name must be a unique and valid DOS file name. A MULTIMED model input file name must be a valid file name either 1) as furnished with the distribution package (see FILE NAME AND CONTENT section) or 2) as designated and/or generated by the user using the PREMED program. This data file will be processed during the execution of the MULTIMED model. File names used for the input data and/or output listing files (except for the test input and output cases provided) are arbitrary, but must follow the rules for DOS file names. A file name should assist the user in identifying the contents or purpose of a file (e.g., INPUT.DAT, OUTPUT.LST). Any MULTIMED, PREMED, or POSTMED file name can be from 1 to 8 characters and can have an optional 1 to 3 character file name extension. Any characters beyond 8 in the file name or beyond 3 in the file name extension will be truncated by the DOS operating system. See the DOS Reference Manual for further information on file names and disk file input/output procedures, rules, and commands. This implementation of the PREMED and POSTMED programs and the MULTIMED model have the same function and will follow the same execution sequence as the current VAX/VMS implementation for the same release versions. _________________________________________________________________ RUN TIME AND PERFORMANCE NOTE: The symbol "" represents pressing the or carriage return key. Responses and key strokes that can be typed by the user are underlined with the hyphen character (-). The following run times (approximate) were observed using the test data files furnished with the distribution version of the MULTIMED model. Remember that these times were obtained using test data files that may not be representative of a "real world" problem and/or data. The test data files have been furnished for testing the installation of the MULTIMED model. In general, these input test data files are not intended to be representative of full scale model simulations. They were developed to test the installation of significant sections of model code. The following run times were produced on an IBM PC/AT 80286 microcomputer running under DOS 3.30 and using 640k bytes of random access memory, a 338 megabyte hard disk, an 8 megahertz clock, and an 80287 math coprocessor chip. ** Test Data Files for MULTIMED Test Runs Approx. Input Output Run Time File Name File Name hr:min:sec _________ _________ __________ a) TEST1.IN TEST1.OUT 00:22:16 b) TEST2.IN TEST2.OUT 00:04:26 c) TEST3.IN TEST3.OUT 00:18:16 d) TEST6.IN TEST6.OUT 00:11:15 Note that program run time and performance can be affected by many microcomputer system and program parameters such as o available disk space o available memory o application program overlay structure o CONFIG.SYS file options and parameter values o disk storage fragmentation o use of a math coprocessor chip __________________________________________________________________ MINIMUM FILE CONFIGURATION The following list describes the absolute minimum file configuration needed to execute the MULTIMED model and the PREMED and POSTMED programs and all support DOS batch command files. This list assumes that o all models and programs have been successfully installed (see DETAILED INSTALLATION INSTRUCTIONS section) from the distribution diskettes o the user has defined and stored all application specific run time files Other files can be deleted if the user needs to recover disk space. - README.1ST - Detailed installation and execution Quick Reference Guide. - README.TOO - Installation, execution, and general support documentation. - TERM_DAT.TXT - ANNIE-IDE System Specification File (TERM.DAT) Quick Reference Guide. - PREMED.BAT - DOS batch command file to execute PREMED program. - PREMEDPC.EXE - Executable code for PREMED program for microcomputer. WARNING: The PREMEDPC.EXE task image should only be executed using the DOS batch command file provided (PREMED.BAT). - MESSAGE.WDM - Direct access screen definition file for PREMED and POSTMED programs. - SUBD.DEF - Default settings initialization file for PREMED Subtitle D application. - TERM.DAT - User system specification (terminal definition) file for PREMED and POSTMED programs. - MULTIMED.EXE - Executable code for MULTIMED model for microcomputer. - RMFORT.ERR - Ryan-McFarland FORTRAN run time error message library file. - POSTMED.BAT - DOS batch command file to execute POSTMED program. - POSTMEDC.EXE - Executable code for POSTMED program for microcomputer. WARNING: The POSTMEDC.EXE task image should only be executed using the DOS batch command file provided (POSTMED.BAT). __________________________________________________________________ MODIFICATION Included in the diskette set are o executable task image files for the MULTIMED model and PREMED and POSTMED programs o FORTRAN source code files for IBM PC and compatible microcomputer systems o batch command files to compile, link, and run task image files Note that the RMFORT FORTRAN compiler and the PLINK86 Plus link editor are NOT required to execute any portion of any model and/or program. If the user wishes to modify a model or program, it will be up to the user to supply and/or obtain o an appropriate text editor that saves files in ASCII (text) format o FORTRAN program development tools to recompile and link edit any portion of either model and/or program o the ANNIE Interactive Development Environment (ANNIE-IDE) tool kit for programmers (also available from the CEAM) The CEAM cannot support, maintain, and/or be responsible for modifications that change the function of any executable task image file (*.EXE) or DOS batch command files (*.BAT) supplied with this model package. __________________________________________________________________ TECHNICAL HELP CONTACT For questions and/or information concerning o the installation of the MULTIMED model, or the PREMED and POSTMED programs, contact Mr. Shawn Turk in the Athens ERL Computer Support Section o MULTIMED model, or PREMED and POSTMED program content, application, and/or theory, contact Mr. Terry Allison (Senior Science Specialist) o the use of the CEAM electronic bulletin board system (BBS), contact Mr. Shawn Turk (BBS system operator) o other environmental software and documentation distributed through CEAM, contact Ms. Catherine Green (Information Specialist) o CEAM software and distribution Quality Assurance and Control, contact Mrs. Marsha LeCroy o other support available through CEAM, contact Mr. Robert B. Ambrose (CEAM Manager) - by mail at the address at the beginning of this document - by telephone at (404) 546-3549 or (FTS) 250-3549 - by fax at (404) 546-2018 or (FTS) 250-2018 - through the CEAM BBS message menu and commands. The CEAM BBS communication parameters and telephone number are listed below. To help technical staff provide better assistance, write down a response to the following topics before calling or writing. If calling, be at the computer, with the computer on, and in the proper sub-directory (e.g., \MULTIMED) when the call is placed. o program information: - describe the problem, including the exact wording of any error and/or warning message(s) - list the exact steps, command(s), and/or keyboard key sequence that will reproduce the problem o machine information: - list computer brand and model - list available RAM (as reported by the DOS CHKDSK command) - list the brand and version of DOS (use VER command) - list the name of any memory resident program(s) installed - printer brand and model - monitor brand and model NOTE: If contacting CEAM by mail, fax, or BBS, include responses to the above information in your correspondence. To check the status of the latest release of this model system or any other CEAM software, call the CEAM BBS 24 hours a day, 7 days a week. To access the BBS, a computer with a modem and communication software are needed. The phone number for the BBS is 404/546-3402 or (FTS) 250-3402. Communication parameters for the BBS are o 300/1200/2400/9600 baud rate o 8 data bits o no parity o 1 stop bit In order to access the BBS at 9600 baud, a US Robotics Courier HST modem must be used. __________________________________________________________________ DISCLAIMER Mention of trade names or use of commercial products does not constitute endorsement or recommendation for use by the United States Environmental Protection Agency. The MULTIMED model, the PREMED and POSTMED programs, and modifications to the DOS system configuration files (i.e., \CONFIG.SYS and \AUTOEXEC.BAT) must be used and/or made at the user's own risk. Neither the U.S. EPA nor the program authors can assume responsibility for model and/or program modification, content, output, interpretation, or usage. IBM, Personal Computer/XT (PC/XT), Personal Computer/AT (PC/AT), and Personal System/2 (PS/2) are registered trademarks of International Business Machines Corporation. PKZIP, PKUNZIP, and PKSFX are registered trademarks and/or trademarks of PKWARE, Incorporated. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation. RM/FORTRAN is a trademark of Language Processors, Incorporated. PLINK86 is a trademark of Sage Software. GSS, GSS-DRIVERS, GSS*CGI, GSS*GKS, GKS*GPS, and GSS*CGM are registered trademarks and/or trademarks of Graphic Software Systems, Incorporated. DEC, VAX, VMS, and DCL are trademarks of Digital Equipment Corporation. __________________________________________________________________ BIBLIOGRAPHY 1. Salhotra, A. M., P. Mineart, S. Sharp-Hansen, and T. Allison (1990), "Multimedia Exposure Assessment Model (MULTIMED) for Evaluating the Land Disposal of Wastes - Model Theory", USEPA, Env. Res. Lab., Athens, GA. 2. S. Sharp-Hansen, C. Travers, P. Hummel, and T. Allison (1990), "A Subtitle D Landfill Application Manual for the Multimedia Exposure Assessment Model (MULTIMED)", USEPA, Env. Res. Lab., Athens, GA. ######################### SHT/sht - June 1991 - C:\MULTIMED\README.TOO