To be able to use this Windows server-type license on Linux, using a plain text editor, change the path on the DAEMON line to reflect the UNIX path to the "bin" subdirectory of the main IDL directory on the Linux system in the Linux copy of the license file. For example:

SERVER myserver 00aabb11ccdd 1700
DAEMON idl_lmgrd /usr/local/rsi/idl_6.2/bin
<<etc.>></etc.>

Finally, you will need to install, configure and run the FLEXlm license manager on each operating system of the dual-boot machine in order to be able to use this server-type of license file. Below are links to the online instructions to install and configure the license manager on Linux and Windows:

[ Back To Top ^ ]

* Using an RSI product Linux license-server type license file on Windows

To use a license-server type RSI product license file that was built for Linux, on the Windows side of a dual-boot system, change the path on the DAEMON line of the license file to the "idl_lmgrd.exe" file that is located in the C:\RSI\FLEXlm directory on the Windows system. Then follow the instructions in the previous step to configure and start the license manager service.

[ Back To Top ^ ]

* What if I have an ENVI for Windows HASP-style license?

If you currently have an ENVI for Windows HASP-style license that you would like to use on a dual-boot Windows/Linux machine, note that HASP-style licensing for RSI products is not currently supported on Linux. To permit use of such an ENVI license on both sides of a Windows/Linux dual-boot machine, your license would need to be permanently converted to a single-user node-locked (SN) server-type license, assigned to the lmhostid of the dual-boot machine, and you would also need to return the HASP device to RSI or your local distributor.

If you would like to convert your ENVI for Windows HASP-style license to a single-user node-locked (SN) server-type license, please contact your local RSI office or your local distributor for assistance or to discuss other available options.

[ Back To Top ^ ]

* What if I have a Windows no-server SN license that is node-locked to a Windows "DISK_SERIAL_NUM" type of LMHostid?

If you have a Windows no-server SN license that is node-locked to a "DISK_SERIAL_NUM"-style lmhostid, in order to be able to use your license, you would need to reassign the lmhostid in the license file to be the NIC hardware address lmhostid of the Windows/Linux dual-boot system, and the license file would have to be regenerated for you as a server-type SN license file. To make this change, please contact your local RSI office or your local distributor for assistance.

Sample ENVI+IDL Windows "DISK_SERIAL_NUM" SN license file:

INCREMENT idl idl_lmgrd 6.100 1-jan-0000 uncounted \
    ABC123DEF456GHI789JK VENDOR_STRING="000111-1Single-User \
    Node-Locked Windows License" PLATFORMS=i86_n \
    HOSTID=DISK_SERIAL_NUM=1234ABCD ck=28
INCREMENT envi idl_lmgrd 4.100 1-jan-0000 uncounted \
    ABC123DEF456GHI789JK VENDOR_STRING="000111-1Single-User \
    Node-Locked Windows License" PLATFORMS=i86_n \
    HOSTID=DISK_SERIAL_NUM=1234ABCD ck=28
INCREMENT idl_tifflzw idl_lmgrd 1.000 1-jan-0000 uncounted \
    ABC123DEF456GHI789JK VENDOR_STRING="000111-1Single-User \
    Node-Locked Windows License" PLATFORMS=i86_n \
    HOSTID=DISK_SERIAL_NUM=1234ABCD ck=28
INCREMENT idl_gif idl_lmgrd 1.000 1-jan-0000 uncounted \
    ABC123DEF456GHI789JK VENDOR_STRING="000111-1Single-User \
    Node-Locked Windows License" PLATFORMS=i86_n \
    HOSTID=DISK_SERIAL_NUM=1234ABCD ck=28

[ Back To Top ^ ]

Solution:
[Edit this field in the IDL-based Tech Tip Editor, v62]