comp.lang.idl-pvwave archive: archive » IDL Licensing Changes

Home » Public Forums » archive » IDL Licensing Changes

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: IDL Licensing Changes [message #94143 is a reply to message #94140]

Thu, 02 February 2017 05:57

lecacheux.alain
Messages: 325
Registered: January 2008

Senior Member

Le mercredi 1 février 2017 18:50:20 UTC+1, Chris Torrence a écrit :
> Hi all,
>
> First, thanks for giving your feedback to Harris. It made a significant impact.
>
> Starting with IDL 8.6.1 (hopefully mid-April), we will make the following changes:
>
> * An IDL user will be able to run an unlimited number of sessions on their machine. In IDL 8.6 the IDL license was tied to the MAC address + install location + process ID, so each process ID would consume a separate license. In IDL 8.6.1, the IDL license will be tied to the MAC address + install location + user id, so multiple process ID’s will consume just a single IDL license.
> * This change will apply to the IDL command line, the IDL Workbench, and the Python bridge, on all platforms.
> * This change will not apply to ENVI or other Harris Geospatial products.
> * There is no policy change for “flexible single user” (other than allowing multiple IDL sessions on one machine). If you need to use IDL on two machines, you should contact Tech Support or your sales rep for options.
> * IDL Virtual Machine will remain unchanged from pre-IDL 8.6 – we just need to tie up some lose ends and release it.
>
> We are shooting for an April release.
>
> Thanks for supporting IDL over the years.
>
> -Chris
> IDL Project Lead

Many thanks to Harris/Exelis (maybe also to the IDL Project leader...) for such a revision of the new v8.6 licensing procedure. While being a regular IDL user (since v2.0), I have even been tempted to shift to Python !
By the way, I wonder whether a long lasting annoying feature of IDL licensing will also be corrected: in the case of a node-locked license on a Windows machine both used locally and remotely (through TSE/RDP), a locally opened IDL session could not be further used within a next remote connection (from the same user), and vice versa. Such a wobbling between local and remote connection is very usual for any scientist working both on and off his lab. So far a workaround was to declare the licensed machine as a license server on itself. But the trick was not possible (afaik) in case of a personal license.
What will be the status in IDL 8.6.1 ?
Cheers,
Alain.

Report message to a moderator

[Message index]

		IDL Licensing Changes By: chris_torrence@NOSPAM on Wed, 01 February 2017 09:50
		Re: IDL Licensing Changes By: markb77 on Wed, 01 February 2017 11:28
		Re: IDL Licensing Changes By: penteado on Wed, 01 February 2017 13:08
		Re: IDL Licensing Changes By: lecacheux.alain on Thu, 02 February 2017 05:57
		Re: IDL Licensing Changes By: chris_torrence@NOSPAM on Thu, 02 February 2017 11:04
		Re: IDL Licensing Changes By: LC's No-Spam Newsread[2] on Tue, 30 May 2017 08:41
		Re: IDL Licensing Changes By: tumanjong on Wed, 31 May 2017 07:41
		Re: IDL Licensing Changes By: LC's No-Spam Newsread[1] on Mon, 05 June 2017 01:40
		Re: IDL Licensing Changes By: Haje Korth on Mon, 13 February 2017 12:58
		Re: IDL Licensing Changes By: bobportmann on Tue, 03 October 2017 10:11
		Re: IDL Licensing Changes By: Doug Edmundson on Wed, 04 October 2017 09:04
		Re: IDL Licensing Changes By: Patrick Broos on Thu, 05 October 2017 15:22
		Re: IDL Licensing Changes By: Doug on Fri, 06 October 2017 07:53

Previous Topic:	Decision tree in envi
Next Topic:	The old Exelis/ITTVIS/RSI contrib directory

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 09:16:18 PDT 2025

Total time taken to generate the page: 0.00443 seconds