Topic : User Manual for TeraDesk Author : Wout Klaren, Henk Robbers, Djordje Vukovic Version : February 2017 Subject : Documentation/Utilities Nodes : 87 Index Size : 2746 HCP-Version : 3 Compiled on : Atari @charset : atarist @lang : en @default : Main @help : @options : -i -t4 +z @width : 75 View Ref-FileContentsIntroductionHardware and Operating System requirements 1.2.2 TOS version compatibility TeraDesk Tera Desktop should work with all existing versions of TOS, but it is very much more useful with versions 1.04 (also known as 1.4) and above. There are several reasons for this, because in TOS version 1.04 and above: - Folders can be renamed. - The file processing routines are very much better and enable more facilities to be used. - GEM programs (including Tera Desktop itself) can be started automatically after booting. - There are significant bugs in TOS 1.0 and TOS 1.02 (1.2) - Functionality of Tera Desktop is reduced with TOS versions older than 1.04 (1.4) because of limitations on the size of menus. Since Version 2 TeraDesk runs in modern multi-tasking environments, such as MagiC, TOS with Geneva, MiNT with N.AES, XaAES, MyAES or Atari AES 4.1. It can be run with memory protection; however, in such environments, problems may occur with some incorrectly-programmed or set AV-protocol clients which can cause TeraDesk to crash if run with memory protection. See The AV Protocol. Versions of TOS that are not multi-tasking-capable are often referred to in this manual as 'single-TOS'. TeraDesk 3* was tested on a number of system configurations, including (but not limited to): TOS 1.00 (RAM-loaded) TOS 1.02 + MiNT 1.15.12 + AES 4.1 / N.Aes TOS 1.04 TOS 1.04 (RAM-loaded) TOS 1.04 + NVDI 2.0 TOS 1.04 + MiNT 1.15.12 + AES 4.1 / N.Aes TOS 2.06 TOS 2.06 + NVDI 4.11 TOS 2.06 + NVDI 4.11 + Wdialog 2 TOS 2.06 + NVDI 4.11 + AES 4.1 TOS 2.06 + NVDI 4.11 + MyAES TOS 2.06 + Geneva 4 / 6 + NVDI 4.11 TOS 2.06 + MiNT 1.15.12 + NVDI 4.11 + AES 4.1 / N.Aes / MyAES TOS 2.06 + MiNT 1.17.0 + NVDI 4.11 + AES 4.1 / N.Aes / XaAES / MyAES TOS 3.05 + NVDI 2.0 TOS 3.06 Hades TOS 3.06 + oVDI Hades TOS 3.06 + MiNT 1.16 + oVDI + N.Aes / XaAES TOS 4.04 TOS 4.04 + MiNT 1.16 + AES 4.1 / N.Aes / XaAES / MyAES Milan TOS 4.09 + MiNT 1.15.12 + N.Aes / XaAES KAOS TOS MagiC 6.0 + NVDI 5.0 MagiC 6.1 + NVDI 4.11 MagiC 6.2 + NVDI 4.11 The program should work (with some restrictions) on TOS 1.0, but more recent versions of Tera Desktop were not tested thoroughly with it. The possibility of encountering hitherto undetected problems with this TOS version can not be excluded, but please report such problems. Also, newest versions of TeraDesk were not tested on -all- variants of operating system(s) listed above. Tera Desktop may fail on versions of MiNT or MagiC previous to 1.12 and 3.0 respectively. A problem was encountered related to mouse clicks on the desktop icons when TeraDesk was running in TOS 2.06 (only). An attempt has been made to cure this, but it is not yet sure whether this has been completely successful. A similar problem may exist in TOS 3.06. Changing screen resolution works with varying success in different AESes (generally supported with AES 4 versions only), e.g. in TOS + Geneva or TOS (+ MiNT) + AES4.1 it works perfectly; in some other environments it doesn't work so well, or at all. TeraDesk makes several inquires to try to determine TOS- and AES- versions, their capabilities and limitations. If a version of TOS or AES is not able to answer these questions, TeraDesk tries to make guesses that may not always be correct. It is also possible that an incorrect answer to an inquiry is supplied by TOS/AES. In that case TeraDesk may work with unnecessary limitations, or else try to activate features which may not work. If TeraDesk is used with the new AESes currently being developed (e.g XaAES or MyAES), occasional unwanted behaviour may occur due to some features of these AESes that are not yet fully functional. Such issues are usually resolved with new releases of the AESes. If TeraDesk is used on an emulator, part of its functionality may be lost because of sometimes incomplete emulation. Such cases may include e.g. not recognising certain keyboard key codes, not being able to show directories in the 'unsorted' order, encountering problems in the creation of symbolic links or encountering strange file or directory owner IDs and file protection states. Users should be aware that the current version of Tera Desktop has the limitation that the number of items in a directory, or the number of selected items in a directory tree should not exceed 32767, and that the total size of all items in a directory (not counting the sizes of objects in subdirectories) or of all objects included in a selection should not exceed 2047 GB (2 TB). The maximum disk partition size that can be correctly displayed is one billion clusters, which is at least 1 TB; there are some provisions in the code to increase those limits to 2 EB in the future. Maximum permitted size of one individual file is 2 GB. See also Supported screen resolutions