NONMEM_6.1.0 Installation: Getting Started These notes describe some fairly quick ways to install NONMEM.

In particular, these notes cover: I. Installation on a Windows system from a CD-ROM II. Installation on a Solaris unix system from a CD-ROM III. Installation on a Linux system from a CD-ROM IV. Compiler test for Windows systems Before installing NONMEM for the first time, please read Chapter 1 of the NONMEM Users Guide - Part V: Introductory Guide. To install NONMEM, a FORTAN compiler must already have been installed on your system. Various "SETUP" scripts are used to install NONMEM, and they include a default designation for the FORTRAN compiler. However, the "default compiler" may not be the one that has been installed. Please acquaint yourself with which FORTRAN compiler it is that has been installed, and perhaps more importantly, with the command name that designates this compiler. Then if this compiler is not the default compiler and/or its designation is not the default designation, you can override the default designation. System environmental variables associated with the compiler should be set before proceeding. Please see the documentation for your compiler. HELP Files: Please note that the nmhelp.exe utility for PCs does not work at this time. Niclas Jonsson has given us permission to include the html files produced by nmhelp2html. CDSETUP6.bat will copy this directory to the NONMEM VI installation directory. To access this help facility double click on the index.htm (not $index.htm) file. If you detect a problem in using the html files, please report this to us.

I. Installation on a Windows system from a CD-ROM. The instructions below apply to the following compilers: Compaq/Digital Visual Fortran versions 5.0 to 6.6b, GNU g77 or g95, Intel Fortran for Windows 7, 8 or 9, Open Watcom 1.3. The error message "out of environment space" is frequently encountered with Windows 95 and 98 and is discussed in NONMEM Users Guide III (Installation) Chapter VII Section 2.4.3.1. You might want to familiarize yourself with this chapter and with the material in Chapters III, IV and V in Guide III. To install NONMEM follow these steps: 1. Read all these instruction before beginning installation. 2. Open a MS-DOS window by double-clicking the MS-DOS icon or the Start=> Programs=>Command Prompt on Window-NT or the Start=>Programs=>Accessories=>Command Prompt on Windows-2000.

The menu path may be different for other versions of Windows. If system environmental variables are not set for the compiler, it will be necessary to type a command like C:\g77\g77setup.bat. This command will differ depending on the compiler being used. 3. Place the NONMEM_6.1.0 CD in the CD drive. 4. Change to the CD-ROM drive by typing x: where x is the appropriate drive letter. 5. At the command prompt, type the setup command and appropriate options. The setup command is described on the CD. If the Compaq/Digital Visual Fortran compiler is used and NONMEM is to be installed from the CD located on drive D: into the nmvi directory on the C: drive then the command is CDsetup6 d c nmvi df y link. The y selects default optimization and link is the linker command The commands for other compilers are For the GNU g77 compiler, the command is CDsetup6 d c nmvi g77 y link For the GNU g95 compiler, the command is CDsetup6 d c nmvi g95 y link For the Intel Fortran 7. compiler, the command is CDsetup6 d c nmvi ifl y link For the Intel Fortran 8. or 9. compiler, the command is CDsetup6 d c nmvi ifort y link For the Open Watcom 1.3 compiler the command is CDsetup6 d c nmvi wfl386 y link. (Later versions of the Open Watcom compiler may not work with batch files included to facilitate the running of NONMEM.) If you are using the Open Watcom 1.3 compiler you will need to replace CALL COMMITTQQ(I) in nm\FLU.for with the following code INCLUDE FSUBLIB.FI INTEGER ISTAT ISTAT=FLUSHUNIT(I) You will also need to change the con to CONOUT$ in the following line of nm/BLKDAT.for 1/'nul','con','PRDERR','INTER','nul'/. An nmfe6.bat file named nmfe6wfl386.bat is provided on the CD. It handles issues specific to the Open Watcom 1.3 compiler. Copy this file from the CD to the run subdirectory. Right click on this file, select properties and deselect the read-only option, The variable dir in this file needs to be changed to the path for the installation directory. (There has been very limited testing of NONMEM VI compiled with the Open Watcom compiler.) These changes must be made before NONMEM compilation. 6. Test the NONMEM installation: cd run nmfe6 CONTROL5 REPORT5 If successful the file "REPORT5" will contain the results of the run. The results obtained can be compared to those provided for this control stream and data set located at ftp://ftp.globomaxnm.com/Public/nonmem/output/. This directory also contains the results files for CONTROL3, CONTROL4, CONTROL6 and CONTROL7, if additional testing is desired.

II. Installation on a Solaris unix system from a CD-ROM 1. Start a C-shell if not the default shell, "csh". 2. Create the NONMEM installation directory, e.g. "mkdir nmvi". 3. Change to the NONMEM installation directory, "cd nmvi". 4. Insert the NONMEM Installation CD-ROM into your CD-ROM drive. 5. Copy the tar-formatted files from /mnt/cdrom/nonmem_6.1.0/UNIX (path for cdrom may vary) to nmvi. 6. Untar the NONMEMVI.tar file, "tar xvf NONMEMVI.tar". 7. Make a help directory, "mkdir help". 8. Move the help.tar file to the help directory, "mv help.tar help/help.tar". 9. Change to the help directory, "cd help". 10. Untar the help files, "tar xvf help.tar". 11. Change back to the install directory, "cd ..". 12. Make an html directory, "mkdir html". 13. Move the html.tar file to the html directory, "mv html.tar html/html.tar". 14. Change to the html directory, "cd html". 15. Untar the html files, "tar xvf html.tar". 16. Change back to the install directory, "cd ..". 17. Make the SETUP script executable, chmod 755 SETUP 18. Run SETUP with the appropriate command line arguments, "./SETUP /nmvi f77 '-O -fnonstd' `which ar`". The name "f77" is the file name designating the FORTRAN compiler. 19. Allow SETUP to proceed to a successful termination. 20. Change to the run directory, "cd run". 21. A C-shell script, nmfe6, that runs the NM-TRAN preprocessor, compiles and links user-specified subroutines with core NONMEM and PREDPP routines and then runs the NONMEM executable is provided in the distribution. Test the installation: cd run ./nmfe6 CONTROL5 REPORT5 If successful the file "REPORT5" will contain the results of the run. The results obtained can be compared to those provided for this control stream and data set located at ftp://ftp.globomaxnm.com/Public/nonmem/output/. This directory also contains the results files for CONTROL3, CONTROL4, CONTROL6 and CONTROL7, if additional testing is desired. . III. Installation on a Linux system from a CD-ROM The following procedure was tested on an Intel system running Red Hat Linux 7.2. 1. Open a terminal emulation window. 2. Start a C-shell if not the default shell, "csh". 3. Create the NONMEM installation directory, for example, "mkdir /opt/nmvi". (You may need to be root to do this.)

4. Change to the NONMEM installation directory, "cd /opt/nmvi". 5. Insert the NONMEM Installation CD-ROM into your CD-ROM drive. In the GNOME environment, the CD will be auto-mounted. 6. Copy the tar files from, for example, /mnt/cdrom/NONMEM_6.1.0/UNIX to /opt/nmvi. The path for the CD will differ from one OS to another, but not in any simple way. 7. Untar the NONMEMVI files, "tar xvf NONMEMVI.tar". 8. Make a help directory, "mkdir help". 9. Move the help.tar file to the help directory, "mv help.tar help/help.tar". 10. Change to the help directory, "cd help". 11. Untar the help files, "tar xvf help.tar". 12. Change back to the install directory, "cd ..". 13. Make an html directory, "mkdir html". 14. Move the html.tar file to the html directory, "mv html.tar html/html.tar". 15. Change to the html directory, "cd html". 16. Untar the html files, "tar xvf html.tar". 17. Change back to the install directory, "cd ..". 18. Make the SETUP script executable, chmod 755 SETUP 19. Run SETUP with the appropriate command line arguments, "./SETUP /opt/nmvi g77 O /usr/bin/ar Intel". 20. Allow SETUP to proceed to a successful termination. 21. Change to the run directory, "cd run". 22. A C-shell script, nmfe6, that runs the NM-TRAN preprocessor, compiles and links user-specified subroutines with core NONMEM and PREDPP routines and then runs the NONMEM executable is provided in the distribution. Test the installation: "./nmfe6 CONTROL5 REPORT5". If successful the file "REPORT5" will contain the results of the run. The results obtained can be compared to those provided for this control stream and data set located at ftp://ftp.globomaxnm.com/Public/nonmem/output/. This directory also contains the results files for CONTROL3, CONTROL4, CONTROL6 and CONTROL7, if additional testing is desired. IV. Compiler test for Windows systems Due to the fact that most installation problems are caused by incomplete compiler or linker installation, prior to installing NONMEM a test of your compiler is appropriate to assure that your compiler is properly configured. An example of Fortran source code follows. Create a file named hello.for using Notepad.exe containing the following text:

C234567 program test WRITE (6,*) "Hello, NONMEM World!" end

(The first line begins with column 1 ([this is a comment line that acts as a column number guide], lines 2,3, & 4 begin in column 7.) Save the file and compile it from a DOS command line using the compiler command for your compiler. For Intel 8 or 9, "ifort hello.for" For g95, "g95 hello.for -o hello.exe" For g77, "g77 hello.for -o hello.exe" For Digital/Compaq, "df hello.for" For Open Watcom, "wfl386 hello.for". Run the compiled program at the command line, by typing hello followed by the Enter key. If successful, the output will be as expected: C:\>g95 hello.for -o hello.exe C:\>hello Hello, NONMEM World! C:\> If not successful, you will get an error either indicating that the compiler was not found: 'g95' is not recognized as an internal or external command, operable program or batch file. or a compiler error of some other type. The most probable cause of these errors is that the environment variables for the compiler and/or the linker (Microsoft Visual Studio provides the linker for Digital/Compaq and Intel Fortran) are not set so that these programs may be run from a DOS window. This requires that the environment variables are set for the system which is usually done using the Control Panel if the installation for the compiler or MS Visual Studio has not set them. The compiler test must be successful before you can install NONMEM.

nmconsult@globomaxnm.com ICON Development Solutions 6031 University Blvd, Suite 300 Ellicott City, MD 21043 Voice: (410) 696-3098 FAX: (410) 480-0776

17 October 2006