Applying patches to Windows Versions
Posted: Wed Nov 18, 2009 12:33 pm
After receiving a Dyalog APL Personal or Non-Commercial license, you are entitled for a period of two weeks to download the latest patches which can be applied to the interpreter in order to bring it uptodate.
DSS users are entitled to download whilest they have a valid DSS agreement, and DSS+ users are additionally entitled to download new versions of Dyalog APL. Other license agreements may also include these entitlements.
To apply patches, you use the PATCH workspace; either by downloading the patch files from http://my.dyalog.com using a web browser, or via the PATCH workspace itself. In either case, the user name and password is the one issued to you either as part of a DSS/DSS+ agreement, or that was included in the email when you received your Personal or Non-Commercial license.
If you download via a web browser, then it will be necessary to unzip the patch file before proceeding.
If you wish to save the patched file to $DYALOG, then you will need to start APL by right clicking on the shortcut and clicking on "Run As Administrator". Then )LOAD PATCH. The Configure button on the first page allows you to enter your username and password, and also caters for simple ftp proxy servers.
From then on, it is a question of following the prompts: note that the installation process creates a $DYALOG\base directory, in which the base builds of the development executable, the development DLL, the runtime executable and the runtime DLL are located. It is essential to use these as the files to be patched; for that reason, do not overwrite them !
The resulting patched file will be saved by default in $DYALOG. Note that under Windows it is not possible to alter a file which contains a currently-running executable, so you cannot save the patched file as $DYALOG\dyalog.exe for example. My preferred method is to save the file as a different name, and then alter the Dyalog startup icon to point to this new file. This allows you to quickly fallback to the previous executable if desired.
If you regularly apply patches, then you may prefer to initiate the patch mechanism by double clicking on the patch icon; you can run as administrator either by right clicking on the icon and selecting "Run as administrator", or to make this permanent, select the Properties of the Icon, and on the Compatibility Tab select the "Run as Adminstrator" checkbox. Note that this shortcut uses $DYALOG\base\dyalog.exe to run, so using this method it is possible to overwrite $DYALOG\dyalog.exe (assuming you have no other APL sessions running).
Dyalog recommends that you have a look at the rest of the DSS pages; there may be other fixes and downloads that are appropriate to your environment. Note that either you will need to "Run As Administrator" for each of these too, or you will be prompted for permission to copy files into directories which require Administrator privileges.
Dyalog intends to alter the PATCH workspace and associated webapges in the near future; please check back to see if there are changes to this note that will affect you.
DSS users are entitled to download whilest they have a valid DSS agreement, and DSS+ users are additionally entitled to download new versions of Dyalog APL. Other license agreements may also include these entitlements.
To apply patches, you use the PATCH workspace; either by downloading the patch files from http://my.dyalog.com using a web browser, or via the PATCH workspace itself. In either case, the user name and password is the one issued to you either as part of a DSS/DSS+ agreement, or that was included in the email when you received your Personal or Non-Commercial license.
If you download via a web browser, then it will be necessary to unzip the patch file before proceeding.
If you wish to save the patched file to $DYALOG, then you will need to start APL by right clicking on the shortcut and clicking on "Run As Administrator". Then )LOAD PATCH. The Configure button on the first page allows you to enter your username and password, and also caters for simple ftp proxy servers.
From then on, it is a question of following the prompts: note that the installation process creates a $DYALOG\base directory, in which the base builds of the development executable, the development DLL, the runtime executable and the runtime DLL are located. It is essential to use these as the files to be patched; for that reason, do not overwrite them !
The resulting patched file will be saved by default in $DYALOG. Note that under Windows it is not possible to alter a file which contains a currently-running executable, so you cannot save the patched file as $DYALOG\dyalog.exe for example. My preferred method is to save the file as a different name, and then alter the Dyalog startup icon to point to this new file. This allows you to quickly fallback to the previous executable if desired.
If you regularly apply patches, then you may prefer to initiate the patch mechanism by double clicking on the patch icon; you can run as administrator either by right clicking on the icon and selecting "Run as administrator", or to make this permanent, select the Properties of the Icon, and on the Compatibility Tab select the "Run as Adminstrator" checkbox. Note that this shortcut uses $DYALOG\base\dyalog.exe to run, so using this method it is possible to overwrite $DYALOG\dyalog.exe (assuming you have no other APL sessions running).
Dyalog recommends that you have a look at the rest of the DSS pages; there may be other fixes and downloads that are appropriate to your environment. Note that either you will need to "Run As Administrator" for each of these too, or you will be prompted for permission to copy files into directories which require Administrator privileges.
Dyalog intends to alter the PATCH workspace and associated webapges in the near future; please check back to see if there are changes to this note that will affect you.