This document contains information that may affect the installation of Dyalog APL.
This file is setup_readme.htm and is included in the help directory in the Dyalog installation directory.
You should have received or downloaded an installation image appropriate to your licence type; Educational or Non-Commercial users should install from the Non-commercial image, all other registered users should install from the Commercial image.
If you believe that your image is for the wrong licence, please contact sales@dyalog.com
This second issue of 14.1 does not include the ability to perform an installation without administrator privileges. Dyalog expects to make this functionality available when a new set of 14.1 installation images is issued later in 2015.
Please note: the installation of Dyalog APL will require a reboot of the system to be fully effective !
If you have already installed 14.1 on your PC, then you will need to uninstall 14.1 before rebooting and then installing afresh. The reboot between uninstalling and reinstalling is important - the new installation may fail if this is not done.
If you are planning to reinstall, remember that this process will result in all previous settings being lost; you may wish to take a copy of the files under the installation directory, your session file and of the registry keys associated with 14.1 before uninstalling the previous issue.
To perform a default installation of Dyalog APL:
If you are installing under Windows Vista, then we recommend that you disable User Account Control before installing Dyalog APL. UAC is enabled and disabled in Control Panel -> User Accounts -> Turn User Account Control on or off. It is best to apply any patches to the interpreter before reenabling UAC.
Additional information about installing Dyalog APL can be found here on the Dyalog Forums.
This should be read in conjunction with the ride2_readme.htm file.
To install:
Note: the startup icon that you click on to start Dyalog on OS X starts the RIDE client which spawns a new APL process. If the RIDE client terminates, the APL process which is associated with it will also terminate.
Dyalog checks for the existence of the file ~/.dyalog/dyalog.config. If it does not exist, this file is created.
dyalog.config should be used to set non-default options for configuration parameters such as MAXWS or TRACE_ON_ERROR; this file is
read each time APL is started, and these values used in preference to the default values. Dyalog recommends that this file is edited rather
than the mapl startup script which will be overwritten whenever a later revision of the current version of Dyalog APL is installed.
Dyalog intends to improve the nature of the configuration file; future versions of this file will have a different structure, and will
simply define name-value pairs.
A full list of the possible values that can be defined in this file currently appear in the Configuration Parameters section of the Dyalog for
Microsoft Windows Installation and Configuration Guide and the Dyalog for UNIX Installation and Configuration Guide.
Please follow the instructions in the Dyalog for UNIX Installation and Configuration Guide manual.
This can be found on http://docs.dyalog.com/14.1.
If you have multiple versions of Dyalog APL installed on your PC, uninstalling any version may result in the APL fonts being uninstalled. Dyalog has placed a zip file containing the APL fonts here so that you can download and reinstall them.
There are more details in the FAQ section of the Dyalog Forums.
When a version of Dyalog is installed on under Windows, files such as workspaces are associated with that newly-installed version. You can change this association by running the user command ]FileAssociations. However, you must run APL as Administrator to make this change.