Dyalog APL V20.0 Issue 1: Installation READ ME FIRST

• Licence types
• Installing Dyalog APL
• • Installing Dyalog APL under Windows
  • Updating Dyalog APL under Windows
  • Installing Dyalog APL under macOS
  • Installing Dyalog APL under AIX and Linux
  • Updating Dyalog APL under Linux and macOS
  • Installing Dyalog APL on Raspberry Pi
• Miscellaneous Operating-specific notes
• • Windows
  • • Association of APL fonts with APL versions
    • Association of APL files with APL versions

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. If you register when downloading the installation images you will be granted 14 days's access to patch files which will enable you to update your interpreter to the most recent set of patches made available.

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_20240101.pdf.

If you already have a 20.0 installed, you will first need to uninstall it. We also very strongly recommend that you delete the Dyalog*.20* directory in your documents directory.

If you are uninstalling 20.0, ensure that you also uninstall the IME (the top option on the uninstall dialog).

Dyalog 20.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:

• The APL 385 font is not installed. Dyalog 20.0 will use the correct font, but no other application will do so.
• The IME is not installed. Instead the keyboard is defined as a series of Registry entries. This means that the keyboard cannot be used in other than the interpreter.
• No attempt is made to install the VS2015 redistributables globally; they are therefore not available outside the interpreter unless they have been installed beforehand.
• A non-administrator install is available only to the user who performed the installation; on a shared machine all users would have to perform a non-administrator installation.

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:

1. Extract the contents of the downloaded zip file into a temporary directory
2. Double click on the newly extracted setup*.exe (you are probably reading this having taken these two steps !).
3. Select "Yes" to the question "Do you want to restart the installer with Administrator privileges?"
4. Select "Yes" in the User Account Control pop up. Note that this Msgbox may hide behind other windows !
5. For a new install
   • Enter your serial number into the field on the setup form. Again note that this form may hide behind other windows.
   • If installing the Unicode Edition, ensure that the Unicode IME is selected - it is optional for the Classic Edition.
6. Click on Default Install.
7. You must accept the Licence terms which will appear in a pop-up window to continue with the installation.
8. At the end of the installation process you will be prompted to reboot your PC; Dyalog APL will not be fully installed until the PC has been rebooted - it is recommended that you perform that reboot as soon as possible having installed Dyalog APL.
9. Double click on the new Dyalog APL shortcut on your desktop; enjoy Dyalog APL !

To perform a default installation of Dyalog APL without administrator privileges:

1. Double click on setup.exe (you are probably reading this having taken that step !).
2. Select "No" to the question "Do you want to restart the installer with Administrator privileges?"
3. Enter your serial number into the field on the setup form. Again note that this form may hide behind other windows.
4. Click on Default Install.
5. You must accept the Licence terms which will appear in a pop-up window to continue with the installation.
6. Click on Finish. No reboot is necessary.
7. Double click on the new Dyalog APL shortcut on your desktop; enjoy Dyalog APL !

The newly-installed files will be put in a directory similar to c:\Users\andys\AppData\Local\Programs\Dyalog\Dyalog APL-64 20.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.

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:

1. By downloading a .msd patch zip file, extracting the contents and running the patch*exe that you have extracted
2. By downloading an installation image, extracting the contents and running the setup*exe that you have extracted
3. By using the old Patch Wizard (although this only patches the 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:

• Download the zip file
• Extract the contents of the zip file into a temporary directory
• Run the patch*exe that is in that temporary directory

To patch from an installation image:

• Download the installation image zip file
• Extract the contents of the zip file into a temporary directory
• Run the setup*exe that is in that temporary directory

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 20.0 requires macOS Ventura (13.7.4) on Mx-based macs. It is no longer available for x86-based machines.
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:

• Download the installation image from https://my.dyalog.com
• Double click on the newly-downloaded pkg file
• Follow the onscreen instructions

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 https://docs.dyalog.com/20.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 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 20.0 currently requires 32-bit Raspberry Pi OS Buster or later.

On 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.

To install pre-release versions of Dyalog APL on the Pi, use the instructions on https://packages.dyalog.com/, but rather than calling
     echo "deb https://packages.dyalog.com ${CODENAME} main" | sudo tee /etc/apt/sources.list.d/dyalog.list
use
     echo "deb https://packages.dyalog.com ${CODENAME} beta" | sudo tee /etc/apt/sources.list.d/dyalog.list
That is, replace main with beta.

There is more information about 32-bit Raspberry Pi OS 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.