Log in
RegisterWinNonlin: End of support [Software]
posted by Helmut 
– Vienna, Austria, 2011-12-19 21:41 (4873 d 08:03 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.
Didn’t know that WinNonlin was programmed in Visual Basic. Must have been great fun to port Carl Metzler’s original FORTRAN code.
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
WinNonlin 3.x No longer supported No longer available
WinNonlin 4.x No longer supported December 2011
WinNonlin 5.0.1 No longer supported December 2011
WinNonlin 5.1.1 No longer supported December 2011
WinNonlin 5.2.1 June 2011 June 2012
WinNonlin 5.3 September 2012 September 2012- This point version of the software will no longer be available for download, and no further patches will be developed or released. Upgrade assistance is always available.
- Pharsight will no longer be able to process license renewal requests for the associated point version after the date listed in the ‘License Renewal End Date’ column.
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
Dif-tor heh smusma 🖖🏼 Довге життя Україна!
Helmut Schütz
The quality of responses received is directly proportional to the quality of the question asked. 🚮
Science Quotes
Complete thread:
- WinNonlin: End of supportHelmut 2011-12-19 20:41
![[Mix]](https://static.bebac.at/img/mix.png "open in Mix view")
- WinNonlin: End of support ElMaestro 2011-12-19 22:31
- WinNonlin: End of support Helmut 2011-12-20 01:48
- WinNonlin: End of support SDavis 2012-01-05 17:55
- WinNonlin: End of support Helmut 2011-12-20 01:48
- WinNonlin: End of support ElMaestro 2011-12-19 22:31
Ing. Helmut Schütz