Log in
Register|
Helmut ★★★   Vienna, Austria, 2011-12-19 21:41 (4873 d 06:25 ago) Posting: # 7795 Views: 10,669 |
|
|
Dear all, since many people still (why?) use older versions of WinNonlin and may not visit Pharsight’s support site regularly, below a copy of the “WinNonlin end of support notice”. Audience: All Customers using a WinNonlin version earlier than 5.3 As previously announced, and consistent with Pharsight’s Maintenance and Support Policy, WinNonlin versions prior to 5.2.1 are no longer officially supported. In addition to our customary policy, the license key generator for WinNonlin versions older than 5.1 is no longer supported by the manufacturer and has been decommissioned, meaning that Pharsight will be unable to provide licenses for versions prior to WinNonlin 5.1 after the end of 2011. We are letting you know about this now, so that you can plan to upgrade to a supported product version by the end of 2011. Moving to a supported version of WinNonlin requires migration to either WinNonlin 5.3 or the Phoenix platform. An important factor driving the development of our Phoenix platform was that WinNonlin 4.x/5.x was developed with Visual Basic, which is no longer supported by Microsoft – so we developed Phoenix using the .NET framework for long-term support. Discontinuing support for Visual Basic and the license key generator was outside of our environment and could not be avoided, so moving to a new infrastructure was required. Clients will be able to run both Phoenix and non-Phoenix WinNonlin product versions (e.g., WinNonlin 5.3 when maintained on a compatible operating system) on the same machine for the foreseeable future with an active license to ease the transition to Phoenix WinNonlin. The upgrade to Phoenix WinNonlin is free for current/active WinNonlin license holders. We strongly recommend that all of our clients start thinking about their migration plans sooner rather than later. Pharsight can work with your teams to understand any challenges and help develop a Phoenix migration plan with you. Validation tools and services are available to assist along with a number of public training courses to help users make the migration to Phoenix smoother. Let us know how we can assist. Version Support End Date1 License Renewal End Date2
Didn’t know that WinNonlin was programmed in Visual Basic. Must have been great fun to port Carl Metzler’s original FORTRAN code. — Dif-tor heh smusma 🖖🏼 Довге життя Україна! ![[image]](https://static.bebac.at/pics/Blue_and_yellow_ribbon_UA.png) Helmut Schütz ![[image]](https://static.bebac.at/img/CC by.png) The quality of responses received is directly proportional to the quality of the question asked. 🚮 Science Quotes |
|
ElMaestro ★★★ Denmark, 2011-12-19 23:31 (4873 d 04:35 ago) @ Helmut Posting: # 7796 Views: 9,310 |
|
|
Hi Helmut, ❝ Didn’t know that WinNonlin was programmed in Visual Basic. Must have been great fun to port Carl Metzler’s original FORTRAN code.  It would really surprise me if the core math routines were done in VB. My best guess is that the GUI itself was VB and then all math was done by DLL's compiled from C or Fortran. The DLL's for WNL will tell. Best regards, EM. |
|
Helmut ★★★ Vienna, Austria, 2011-12-20 02:48 (4873 d 01:18 ago) @ ElMaestro Posting: # 7797 Views: 9,357 |
|
|
Hi ElMaestro!, ❝ It would really surprise me if the core math routines were done in VB. My best guess is that the GUI itself was VB and then all math was done by DLL's compiled from C or Fortran. The DLL's for WNL will tell. Right guess! WinNonlin (classical version ≤5.3) supports linking of user-models (libraries compiled from FORTRAN 90 and C). Sneeked into some DLLs: call Digital Equipment’s Visual FORTRAN Runtime Library v6.0-646 (DFORRT.dll). ![[image]](https://upload.wikimedia.org/wikipedia/commons/thumb/5/58/FortranCardPROJ039.agr.jpg/320px-FortranCardPROJ039.agr.jpg) — Dif-tor heh smusma 🖖🏼 Довге життя Україна! Helmut Schütz The quality of responses received is directly proportional to the quality of the question asked. 🚮 Science Quotes |
|
SDavis ★★ UK, 2012-01-05 18:55 (4856 d 09:11 ago) @ Helmut Posting: # 7867 Views: 9,156 |
|
|
Thanks Helmut for reminding the BE community of this, as a rule our official support period for a version is 18 months AFTER the release of the REPLACEMENT version. PS - Those of you who use Trial Simualtor and have been frustrated by Fortan compiler difficulties will be pleased to know that the current release 2.2.2 now comes with the same distributed compiler as that used by Phoenix as well as supporting Windows 7 etc.. I hope to give an indication of TS 3.0's release date in the Phoenix architecture soon. Happy New Year all, Simon — Simon Senior Scientific Trainer, Certara™ [link=https://www.youtube.com/watch?v=xX-yCO5Rzag[/link] https://www.certarauniversity.com/dashboard https://support.certara.com/forums/ |
Ing. Helmut Schütz