Short: UnRAR 5.70
Author: Alexander Roshal, Marcin Labenski (Amiga Port)
Architecture: ppc-amigaos >=4.1; ppc-morphos >=3
This is a brand new UnRAR port for AmigaOS4 and MorphOS based on source code
UnRAR license is available in license.txt file in this archive.
This port uses also code from newlib 3.1.0 and utf8proc.
Newlib license is available in license_newlib.txt file in this archive.
Utf8proc license is available in license_utf8proc.txt file in this archive.
Source code of this program is available on github:
* support all the basic unrar commands and options, including listing,
unpacking (all or selected items), printing and testing archive files
* support national characters in archive name, names of files and directories
in the archive, passwords, comments and list files
* support restoring information about file modification date, owner and group
* support unpacking symbolic links and hard links stored in archives
* support unpacking multi-volume and SFX archives
* can read switches from configuration file s:rar.conf or RAR environment
* support AmigaOS localization via locale.library
unrar_mos - unrar version for MorphOS 3
unrar_aos4 - unrar version for AmigaOS 4.1
catalogs - unrar translations - currently Polish translation only
license.txt - UnRAR license
license_newlib.txt - newlib license
license_utf8proc.txt - utf8proc license
UnRAR.readme - this readme file
copy unrar_mos to c:unrar
copy catalogs to locale:catalogs all
Note: MorphOS has its own unrar 3.90 in protected System:MorphOS/C direcory
that is used with higher priority than a file in c:unrar. And so if you want
to use the one from c: you need to call it explicitely, like this:
c:unrar l my_archive.rar
To avaid this, you can also copy unrar to c:unrar5, and then call it as unrar5:
copy unrar_mos to c:unrar5
unrar5 l my_archive.rar
copy unrar_aos4 to c:unrar
copy catalogs to locale:catalogs all
Note (for both MorphOS and AmigaOS4): if you have Polish locale set and you
don't like my Polish translation, do not copy it to locale: and you will get
English only version.
Detailed port description
All the basic functions like listing (verbose, base, technical),
unpacking (w/ or w/o path, selected files or all), testing or printing
works fine. Note, that wherever a path is needed it has to be in amiga
format not POSIX i.e. //test.rar not ../../test.rar.
National characters support
RAR stores data in UTF-8 in an archive file, then reads it into Unicode
(wchar_t) and finally it uses it (print, create files, find files, ...)
in UTF-8. Unfortunately, no Amiga operating system supports UTF-8 today,
therefore in order to handle national characters in file names,
comments, etc. it needs to be converted to OS local encoding set in OS
prefs. Unrar reads what was set using environment variables:
* on MorphOS: CODEPAGE
* on AmigaOS4: Charset
Characters that cannot be converted, because are not present in selected
codepage, are replaced with '?'. That means that national characters are
fully supported but only for selected locale, i.e. if I have Polish
locale with ISO-8859-2 encoding and have a rar archive with Spanish
characters, they will not appear and will be replaced by '?'. That in
turns mean that some files may have the same names even if they are
different files. In that case only one will be unpacked. To deal with
this, you can use special environment variable RAR_CODEPAGE that allows
overriding codepage (for both MorphOS and AmigaOS4) without changing
system prefs. For an example above, if you set RAR_CODEPAGE, you will
still not see Spanish characters (unless you have the right font) but at
least you should get all the files unpacked.
National characters in file names
National characters in file names are handled as described above - this
* name of files, directories and links in an archive
* targets for symbolic and hard links in an archive
* archive names given to unrar command
* names in list files (if -sc option is not used)
Obviously, in order to see national characters in shell or when browsing
unpacked files in Ambient/Workbench you need to have fonts with the
right encoding installed in OS and set as system font and/or as Ambient
National characters in password
National characters are supported in passwords. A password can be given
in the following forms:
* from shell when asked
* in command invocation using -p switch
* from RAR environment variable
* from rar.conf configuration file
In each of the case above, only passwords containing national characters
of currently selected locale are supported and should be given using
locale encoding (as for file names described above). If the password is
not using current locale charset, RAR_CODEPAGE need to be used to select
Unrar has -sc<chr>[obj] switch described as "Specify the character set" that
is not very useful and not very well documented. From the source code I
read that <chr> can be one of:
* "a" for ANSI,
* "o" for OEM,
* "u" for Unicode and
* "f" for UTF-8.
For non-Windows systems, only "u" and "f" matter (BTW: "u" is UTF-16 not
[obj] is one of:
* 'c' for comment - does not apply unrar, used only in 'full' rar utility
* 'r' for redirect - applies to Windows only
* 'l' for file lists - applies to file list to unpack (specified after "@"),
file list to exclude (specified after -x@) and filter file list
(specified after -n@).
When -sc switch is not used, unrar will try to autodetect UTF-16 and
UTF-8 and when it fails it will assume local encoding. The latter will
also happen when "a" or "u" was used.
All above is standard unrar behavior - I'm only documenting it here.
Unrar supports wildcards in Windows style:
* "?" = any character
* "*" = any character sequence
Amiga style wildcards are not supported at this moment.
File modification dates
When unpacking, created files get modification date set as stored in RAR
archive. The date is set in the local time zone. As there is no special
attribute for creation and access dates in AmigaOS, these values are
File owner and group
When unpacking from RAR archive with option -ow, unrar will try to set
owner name and group. It will only succeed if a user with given name and
a group with given name is present in local system. Otherwise an error
will be printed. When -ow is not used, owner/group is ignored.
Symbolic links in an archive
RAR can store symbolic links and this unrar port supports that. When
unpacking, targets for Unix symbolic links will be changed into Amiga
links (Makelink function) provided that filesystem into which unpack is
done supports that (SFS does). When the filesystem does not support
symbolic links, an error will be printed and the symbolic link will be
As RAR stores symbolic link target in the form that is right on OS where
an archive was created, before making links in Amiga, the path needs to
be converted (for instance ../test.txt need to be changed to /test.txt).
This unrar port does such conversion.
Note: unrar checks if a link is safe to create and will skip links
targeting outside of unpacking directory. In order to make it create
them, you need to use -ola switch when unpacking.
Hard links in an archive
Hard links are supported in a similar way as symbolic links. Again, they
will only work if target filesystem supports hard links (SFS dos not).
Otherwise an error will be printed and hard link will be ignored. There
is no option in unrar that would allow the user to unpack hard links as
regular files or symbolic links - so if target filesystem does not
support hard links it is not possible to get them unpacked.
Reference files in an archive
RAR can pack identical files as references inside of an archive - that
reduces size of the archive file. In order to make such archive -oi
switch should be used when packing. When unpacking, duplicates are
re-created as separate files. That is fully supported in this unrar
NTFS Junction Points in an archive
NTFS Junction Points are like symbolic links, but their target is always
absolute path with a drive letter in front. In Unrar version 5.7 for
Unix-like systems (including Amiga) these kinds of links are always
skipped silently (!). While it is a different behavior from how it was
in 5.0, I decided to keep it unchanged for Amiga. So, in practice,
junction points are always skipped when unpacking.
Unrar has a config file in which you can store switches that will always
be used when unrar command is called. In order to do that, "switches="
should be present in the file with all the switches to add (for instance
"switches=-ad -ola"). This port of unrar looks for configuration file in
There is also "RAR" environment variable that can have switches to use
(like a value of "switches=" in configuration file). The priority of
resolving switches to use is: directly given in command, RAR environment
variable, configuration file.
Support for localization
This unrar port complies with localization rules of MorphOS and AmigaOS.
You can find cs/cd file for making additional translations on GitHub
in "locale" directory.
Notes about porting
This port is based directly on unrar source code version 5.7.3
(unrarsrc-5.7.3.tar.gz) from rarlab.com:
For normalizing UTF, I used utf8proc. I did not need to port it to Amiga
- it compiles without any change:
For vfwprintf-like functions from libc, that are not implemented on
Amiga at all, I ported the code I took from newlib 3.1.0:
MorphOS version of unrar has been compiled using gcc 4.4.5 (part of SDK
3.12). AmigaOS4 version of unrar has been compiled using gcc 4.2.4 (part
of SDK 53.20).