_
From: owner-nmus...@globomaxnm.com [mailto:owner-nmus...@globomaxnm.com] On
Behalf Of Kevin Dykstra
Sent: Thursday, November 15, 2012 7:13 AM
To: r.bruggem...@akf.umcn.nl; nmusers@globomaxnm.com
Subject: [NMusers] RE: installation of both NONMEM 7.2 and Phoenix WinNonLin 6.2
Roger,
I had the same
th Phoenix and NONMEM.
Cheers,
Kevin
From: owner-nmus...@globomaxnm.com [mailto:owner-nmus...@globomaxnm.com] On
Behalf Of Bauer, Robert
Sent: Thursday, November 15, 2012 11:45 AM
To: nmusers@globomaxnm.com
Subject: [NMusers] RE: installation of both NONMEM 7.2 and Phoenix WinNonLin 6.2
An alterna
...@globomaxnm.com] On
Behalf Of Bauer, Robert
Sent: Thursday, November 15, 2012 11:45 AM
To: nmusers@globomaxnm.com
Subject: [NMusers] RE: installation of both NONMEM 7.2 and Phoenix WinNonLin 6.2
An alternative is to use the self-install versions of NONMEM for Windows using
gfortran that Bill and I have
: Thursday, November 15, 2012 9:55 AM
To: r.bruggem...@akf.umcn.nl; nmusers@globomaxnm.com
Subject: [NMusers] RE: installation of both NONMEM 7.2 and Phoenix WinNonLin 6.2
Yes, Pheonix install is not nice and messes up the NONMEM install. Pheonix
uses g77, I believe, which sets a global "LIBRA
Roger,
I had the same issue with trying to get Phoenix and NONMEM to coexist
peacefully (same versions as well). The solution was to put the pointers to
nonmem and fortran directories at the head of the path: e.g.
C:\nm72g\run;C:\Program Files
(x86)\gfortran\libexec\gcc\i586-pc-mingw32\4.6.0;C:
Yes, Pheonix install is not nice and messes up the NONMEM install. Pheonix
uses g77, I believe, which sets a global "LIBRARY_PATH" (which gfortran does
not need). If gfortran finds a LIBRARY_PATH, it will use it, find the g77
LIBRARY_PATH and mess up the compilation of NONMEM with gfortran.
