Dyalog APL V18.2 Installation READ ME FIRST

• Licence types
• Installing Dyalog APL
• • Installing Dyalog APL under Windows
  • Installing Dyalog APL under Windows
  • Installing Dyalog APL under macOS
  • Installing Dyalog APL under AIX/Linux
  • Installing Dyalog APL on Raspberry Pi
• Miscellaneous Operating-specific notes
• • Problems with the LOAD configuration parameter in early 18.2 images
  • 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.

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:

• The APL 385 font is not installed. Dyalog 18.2 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: 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:

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

The existing Patch Wizard can still be used, however, from 18.2 onwards we are now generating Patch Files (.msds) which can be used to update existing 18.2 installations. Where the Patch Wizard only supported updating the four interpreter .exes and .dlls, the msds 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 you should never need to uninstall and reinstall 18.2 again (thta is our intention, but we cannot guarantee that!).

The msds will be available to DSS users on a regular basis, and will be available on the patch download page of my.dyalog.com. msds will be made available on www.dyalog.com, but these will be updated far less frequently.

Each msd 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:

• 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

Dyalog APL 18.2 requires macOS Big Sur 11.6.1 or later (although we have not yet tested under Monteray). Under Big Sur 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:

• Download the installation image from http://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 manual.
This can be found on http://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.

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.

Early releases of 18.2 had a flaw in the handling of the Create event on ⎕SE. That meant that there was a problem when using Link to launch applications directly from a directory containing source files using the LOAD parameter (see Configuration Parameters -> LOAD in the Dyalog for Microsoft Windows Installation and Configuration Guide).

If you installed 18.2.45351 or earlier then if on Windows you are using your own session file (which will always be the case if APL was installed for all users, because a local copy is made on first use), or on any platform if you have created your own modified session and you want to be able to specify

      LOAD=my.directory

then you should do one of the following:

• )load buildse and run UPDATE_182_SESSION
• )load buildse and run BUILD_SESSION to rebuild your session file from scratch
• Copy the session file in the Dyalog installation directory to the Dyalog directory under your Documents directory

The same applies on Windows if you want to be able to right click on a directory in Windows Explorer in order to Load the contents into APL.

If you do not intend to make use of the LOAD= parameter then you do not need to follow the steps listed above.

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.