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_20220315.pdf.
Dyalog 18.2 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: Dyalog strongly recommends that if not already installed, you include the VS2015 runtime packages when you install Dyalog APL; failure to do so may result in the failure of .Net-related code.
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 18.2 Unicode.
Under Windows 11 Classic editions of Dyalog APL are apt to be configured to use the us.din keyboard. You can correct this by going to Options->Configure->Input, selecting the correct input translate table and restarting Dyalog APL. We are investigating this, but it may be an issue for UK keyboard users only.
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.
Registered users can patch their Dyalog installations to the most recent revision that has been uploaded for 14 days from when you registered. There are three ways to patch your Windows interpreter:
Note that the .msd patch zip file is considerably smaller than an installation image !
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. Each msp will be included in a patch*zip file, along with a patch*exe file; both files have the same revision number.
To patch from an msd zip file:
To patch from an installation image:
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!).
Dyalog APL 18.2 requires macOS Big Sur 11.6.1 or later. It will run on ARM-based macs under Rosetta. When first you attempt to access certain directories (Documents or remote filesystems) you will be prompted by the operating systemto 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 manual.
This can be found on https://docs.dyalog.com/18.2.
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.
Download the latest installation image for your platform and follow the instructions above to install it - this will cause the installation to be updated.
Dyalog APL 18.2 requires 32-bit Raspbian Buster or later. .NET Core is not supported on armv6 CPU - that is, Pi Zero, 1 and 2.
To install and run on Raspberry Pi O/S Bookworm you must use 18.2.48479 or later, which is available on packages.dyalog.com.
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 APL script files are associated with that newly-installed version. The user command ]fileassociations can be used to change the associations and now supports both user and system wide installations, and now copes with the need to raise privileges to update the registry where necessary. This controls for example what appears in the context menu when you right click on my.aplf file See ]fileassociations -?? for more information.