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.
There is now a single licence agreement for Dyalog APL, covering both commercial and non-commercial usage.
Unregistered installations (those which do not have a valid serial number) are covered by the Basic licence.
Using or entering a serial number other than the one issued to you is not permitted. Transferring the serial number to anyone else is not permitted. For the full licence terms and conditions, see https://www.dyalog.com/uploads/documents/Terms_and_Conditions.pdf.
Programs compiled with VS require appropriate version of the VS Runtime to be installed. Versions of Dyalog APL prior to 19.0 were built with VS2015, so the VS2015 runtime was installed along with the interpreter. Dyalog APL version 19.0 is built with VS2022, so the VS2022 Runtime is installed along with the interpreter. Microsoft state that the VS2015 and VS2022 Runtimes are the same.
Dyalog 19.0 can be installed either with administrator rights, or without. Dyalog Ltd strongly recommends that whenever possible, the installation is performed with administrator privileges.
An installation performed without administrator privileges has the following limitations:
Note: the installation of Dyalog APL will require a reboot of the system to be fully effective !
To perform a default installation of Dyalog APL with administrator privileges:
To perform a default installation of Dyalog APL without administrator privileges:
The newly-installed files will be put in a directory similar to c:\Users\andys\AppData\Local\Programs\Dyalog\Dyalog APL-64 19.0 Unicode.
Additional information about installing Dyalog APL can be found here on the Dyalog Forums.
If you have problems typing APL characters, it is worth taking a look at the links at the bottom of the Fonts and Keyboard page on the Dyalog website at www.dyalog.com/apl-font-keyboard.htm.
The existing Patch Wizard can still be used, however, from 18.2 onwards we are now generating Microsoft Patch Files (.msps) which can be used to update existing installations. Where the Patch Wizard only supported updating the four interpreter .exes and .dlls, the msps contain updates for any file in a release which has changed. They are cumulative, and it is Dyalog's intention that once you have installed 18.2 or later you should never need to uninstall and reinstall 18.2 or later again (that is our intention, but we cannot guarantee that!).
The msps will be available to DSS users on a regular basis, and will be available on the patch download page of my.dyalog.com. msps will be made available on www.dyalog.com, but these will be updated far less frequently.
Each msp will be included in a patch*zip file, along with a patch*exe file; both files have the same revision number
To apply a patch:
Dyalog APL 19.0 requires macOS Big Sur 11.6.1 or later on Intel-based macs, and macOS Ventura (13.4.1) on Mx-based macs. When you first attempt to access certain directories (Documents or remote filesystems) you will be prompted by the operating system to allow Dyalog APL to access that directory.
To install:
You should read the Configuration section of the release notes which explain the purpose of and usage of the ~/.dyalog/*dcfg files. They allow you to
configure Dyalog APL in a cross-platform manner.
All of the configuration parameters that are used by Dyalog under macOS can be found in the Dyalog for macOS Installation and Configuration Guide.
The 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.
Please follow the instructions in the Dyalog for UNIX Installation and Configuration Guide . This can be found on http://docs.dyalog.com/19.0.
Under Linux (including the Raspberry Pi) if you install from your desktop you should find a Dyalog APL (TTY) icon in the start menus. If you subsequently install RIDE, a "Dyalog" icon is also added; this causes RIDE to start and it then starts a Dyalog session.
Under Linux (including Pi) the script /usr/bin/dyalog is under the control of the update_alternatives system. If you have multiple versions of Dyalog APL
installed on Linux and you wish to change the version which /usr/bin/dyalog starts, use sudo update_alternatives --config dyalog.
You should read the Configuration section of the release notes which explain the purpose of and usage of the ~/.dyalog/*dcfg files. They allow you to
configure Dyalog APL in a cross-platform manner.
Dyalog recommends that you never edit /usr/bin/dyalog or $DYALOG/mapl. Rather either take a copy of the script and edit that, or write your own script which
sets the environment and then calls the Dyalog-supplied script, or better yet, edit your personal copy of the new configuration files.
Dyalog APL 19.0 currently requires 32-bit Raspbian Buster or later: for Bookworm you need 19.0.48479 or later (as is the case for 17.1, 18.0 and 18.2). .NET is not supported on armv6 CPU - that is, Pi Zero, 1 and 2.
There is more information about Raspberry Pi O/S support and .NET support in the dyalog_readme.htm which appears in the Help directory under the installation directory.
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 APL is installed on Windows, files such as workspaces and .aplf files are associated with that newly-installed version. The user command ]fileassociations can be used to change the associations; if you choose to change the system-wide setting you will be prompted to allow ]fileassociations to start an interpreter with raised privileges.