• Download Iso Image

Introduction
This tutorial explains some alternative methods of making it possible to install AmigaOS 3.9 on a real Amiga by using the Emergency Disk II boot floppy, and it's mainly intended for those who doesn't have a CD-ROM drive connected to their Amiga. The tutorial is really not completely finished yet, among other things, it will in the future include some instructions on how to make a customized AmigaOS 3.9 ISO image.
Let's start off by debunking a couple of myths that seems to be floating around:
Myth 1: The AmigaOS 3.9 CD contains copy protection.
This is not true, and I belive there are two reasons why some people seem to think so. The first one is the fact that although it's possible to browse the CD on a Windows PC, there will be problems when trying to copy all files from it. But what causes this isn't copy protection, no it's quite simply because Windows doesn't 100% support the file system used on the CD (there are problems with international characters in the file names for example).
The second reason has to do with the Boing Bag updates. Upon installing them, the installer will ask the user to insert the AmigaOS 3.9 CD, and then it will try to verify if it's a genuine CD by simply checking for the presence of certain files on it. One example of the files that will be checked, is the AmigaOS3.9:Videos/Angels.avi file, and if it's missing, the installer will complain.
Myth 2: You need the AmigaOS 3.9 CD for installing AmigaOS 3.9.
This is not entirely true, because what you need is the contents of the CD, and a way for the Emergency Disk and the various installers to find this content. This basically means that the AmigaOS 3.9 files can be on any storage device. Below you will find various solutions as to how this can be arranged, so continue reading on.
Accessing the AmigaOS 3.9 CD via WinUAE
As mentioned above, there are certain problems with trying to copy files from the AmigaOS 3.9 CD on a Windows PC, but it is possible to achive this by using an emulated Amiga. The instructions below describes how this can be done with WinUAE, but have in mind that I'm using version 2.3.1 of the program here, I don't know if it will work with earlier versions.
First of all you need to insert the AmigaOS 3.9 CD into the CD/DVD drive of your PC. If you have plans of copying the contents of the CD over to a empty USB pendrive or Compact Flash card (to be used with a CF-PCMCIA adapter), you should insert this as well, just have in mind that it must have a capacity of at least 512MB. Take a note of the volume name of the USB drive/CF card since it will make it easier to identify later on, and if it doesn't have a name, I recommend that you give it one before you continue.

This may work well with AmigaOS 3.1 and lower, but with AmigaOS 3.9 it can be a bit problematic. The thing is that WinUAE needs to be set up to emulate an Amiga which is precisely like the real Amiga the harddisk is intended for, this is because the AmigaOS 3.9 install will be customized to the very Amiga it is installed on.

1. Mar 19, 2016  AmigaOS3.9: or AmigaOS39: is a CD-ROM, ISO image or hard drive image prepared from the AmigaOS 3.9 CD-ROM for the purpose of installing AmigaOS 3.9 to your emulation.
2. Installation of AmigaOS 3.9 under WinUAE. Translated by Desolator. You can download it from Copy the S catalogue.

Now you can start WinUAE. I will not explain how to set up an emulated Amiga here, instead I will assume that you already have done this in the past. What you basically need is a bootable HDF image, but a Workbench ADF image file might work as well (like I did in the example below).
Before you click the Start button in WinUAE, you should first click 'Hard drives' in the box to the left. Next, make sure that the 'Add PC drives at startup', 'Include removable drives.' and 'Include CD/DVD drives.' options are enabled. Continue with clicking the Start button.
Please note the following:
1. In case you are a little worried about giving the emulated Amiga access to all drives on your PC, have in mind that enabling the 'Add PC drives at startup' option may really not be necessary. As an alternative you can add a directory present on your PC instead.
2..Since Emergency Disk II floppies created with Amiga911 Maker 1.62 now supports booting from AmigaOS3.9 HDF images in addition to ISO, you may consider creating a hardfile and adding it to the emulated Amiga if you intend to later use E-Disk-II for installing OS3.9 on your real Amiga. Just make a new HDF file that's at least 512 MB big, so that all AmigaOS 3.9 files can be copied to it.

After the emulated Amiga has booted, you should be able to see the AmigaOS3.9 icon on the Workbench screen. Since WinUAE will treat the CD in the same way as if it was mounted on a real Amiga, you should now be able to copy the files from it without any errors. The easiest way to do this is probably by using a filemanager of some sort (like DOpus), but it can also of course be done in a Shell window. Just remember that ALL files must be copied, this includes both the audio and video files.
Below are some examples of what you can do next:
1. Copy the AmigaOS 3.9 files to a USB pendrive or CF card
First you must try to locate your pendrive or CF card, if you did what I mentioned earlier about taking a note of the volume name, this shouldn't be a problem. Otherwise you can try to locate the correct device by checking the capacity or contents of all the mounted drives on your emulated Amiga. When you have figured this out, you can either use a filemanager for copying all the files, or you can do it in Shell. In my case, the pendrive was called CORSAIR, so I entered the following in Shell:
Copy AmigaOS3.9: to CORSAIR: ALL
But here you must of course replace CORSAIR with the volume (or device) name of your own pendrive/CF card. After the copying is done, you can make an additional EXTRAS drawer for the Boing Bag updates, an A911Extras drawer pack and various other stuff that can be useful to have. This is best done from Workbench in order to give the drawer an icon (EXTRAS.info)
Now there is one final thing to do, and that is to rename the pendrive/CF card. This has to be done from Windows, so quit WinUAE. It would really have been best to rename the pendrive/CF card to AmigaOS3.9, but here the problem is that FAT formatted drives can't have dots in the volume names, so you will have to rename the device to AmigaOS39 instead. Don't worry about the drive not having the correct name since the Emergency Disk II floppy will look for both names upon booting.
2. Copy the AmigaOS 3.9 files to a HDF image file
With Amiga911 Maker 1.62 it is possible to create Emergency Disk II floppies that supports booting from both AmigaOS3.9 ISO and HDF image files, where they can be present on any drive that gets mounted upon booting the Emergency Disk II. For doing this you must first create a new HDF image file in WinUAE, and then add it to the emulated Amiga. The HDF image needs to be at least 512 MB in size, and you should also make sure that the default settings with a block size of 512 bytes and a BlocksPerTrack value of 32 is used. Another thing is that it's safest to just use the standard FastFileSystem (FFS).
After the emulated Amiga has booted up, you may need to format the HDF image. So click on the correct device icon, and select 'Icons > Format disk' from the Workbench menu. In the window that now pops up, make sure that only the 'Fast File System' and 'International Mode' options are enabled. The Volume Name suggested should be 'Empty', and you can just leave this alone for now (you will rename it later). Now click the 'Quick Format' button in order to start formatting the HDF file. When this is done, you can copy all files from the AmigaOS3.9 CD to the HDF volume, so either use a filemanager or enter the following in Shell:
Copy AmigaOS3.9: to Empty: ALL CLONE
Since the copying is done to a volume with the native Amiga filesystem (FFS), the CLONE argument can be used in order to preserve all Amiga specific file attributes. When the copy process is finished, you can finally rename the volume name from Empty to AmigaOS3.9 by clicking the drive icon and selecting 'Icons > Rename' from the WB menu. Now you can just quit WinUAE and copy the HDF image file to whatever device to be used on the real Amiga. You will also have to configure the Emergency Disk II in order for it to use the HDF file for booting, some instructions for this can be found in the Preperations part of the Using the Emergency Disk II tutorial.
3. Copy the AmigaOS 3.9 files to the harddisk of your PC
You can also copy all files from the AmigaOS 3.9 CD directly to the harddisk of your PC. This can be useful if you need to do something with the files outside of WinUAE. One example can be if you can't get the USB pendrive or Compact Flash card to be properly mounted on the emulated Amiga. Then you can first copy the files from the AmigaOS 3.9 CD over to the harddisk, and then in Windows copy the files from the harddisk to the pendrive/CF card. Another example is if you want to add all AmigaOS 3.9 files to a zip archive file, and then somehow transfer it to a real Amiga. Just have in mind that it's really a good idea to first make a folder on your PC's harddisk, and then copy all files into that folder. As an example, I made an AmigaOS3.9 folder on my KISS partition (drive D: in Windows), and then entered the following in Shell:
Copy AmigaOS3.9: to KISS:AmigaOS3.9 ALL
4. Activate an Emergency Disk II floppy
Another thing you can do is activating a ready-made Emergency Disk II floppy, you can find download links for the ADF images on the Downloads page, and instructions for activating can be found on the Ready-made Emergency Disk II page.

When preparing a harddisk for the Amiga by using WinUAE
A lot of people prefer to use WinUAE for setting up a harddisk to be used on a real Amiga, and this also involves installing the operating system as well. This may work well with AmigaOS 3.1 and lower, but with AmigaOS 3.9 it can be a bit problematic. The thing is that WinUAE needs to be set up to emulate an Amiga which is precisely like the real Amiga the harddisk is intended for, this is because the AmigaOS 3.9 install will be customized to the very Amiga it is installed on. Failing to do this may lead to the real Amiga crashing upon booting from the harddisk.
But there is an alternative way to do things. First of all you have to make sure that you have access to the AmigaOS 3.9 CD from within the emulated Amiga (read further up on this page regarding this). Now when you partition the drive, make sure to create at least two partitions, where the second one is at least 500MB in size. On the first partition (bootable) you can install Workbench 3.1 if you want to, this is just so that you have something to boot from. Then copy everything from the AmigaOS 3.9 CD to the second partition. When this is done, you can copy whatever extra stuff you want included as well, this can be things like the Boing Bag updates, an Emergency Disk II ADF file and maybe one of the A911Extras packs as well. The final thing to do is renaming the second partition to AmigaOS3.9.
Now you can connect the harddisk to your Amiga and start it up. The next thing to do is preparing an Emergency Disk to be used for installing AmigaOS 3.9. Here you can use my Emergency Disk II, or you can create a standard original one instead (both will work fine for this purpose). In case you need to write an ADF file to a floppy disk, have in mind that the A911Extras packs contains software for doing so. When the Emergency Disk is finished, use it to start up your Amiga. Upon booting, the disk will simply look for AmigaOS3.9:, and since your second partition has this name, it should then continue to boot from it. Now you can install AmigaOS 3.9, then reboot and finally install the Boing Bags.
After you are finished, and you no longer need the files present on your second partition, just quick-format it and use it for something else.
Some important notes:
1. Although it might be tempting to add, replace or delete files to/from your new AmigaOS 3.9 pendrive/CF card/drawer, I will STRONGLY suggest that you don't do this. The contents of the original CD, and especially what's in the Emergency-Boot drawer, is very generic where it should work on ANY Amiga with a 68020 processor. If you mess around too much with the files, your Amiga may crash upon booting the device, or it may work on one Amiga model, but not on another. So try to keep things clean!
2. If you still want to add files to your AmigaOS 3.9 device, keep them separated from the original AmigaOS 3.9 files by creating an EXTRAS drawer dedicated for the other files. This way you will always know that whatever is present in the EXTRAS dir, it's not a part of the original AmigaOS 3.9 files.
3. I will repeat it again: When you copy the contents of the AmigaOS 3.9 CD to another device, you'll need ALL files including the media files, otherwise you WILL have problems with installing the Boing Bag updates.
4. Have in mind that when copying files from the AmigaOS 3.9 CD, the copied files will most likely be write protected.
5. In case you are worried about the files on the pendrive/CF card not having the correct Amiga specific file protection bits, there is a function on the Emergency Disk II that can be used for fixing the bits after AmigaOS 3.9 has been installed. To do this, just select 'Misc > Fix Protection bits' from the Workbench menu.
6. How the AmigaOS3.9: vs. AmigaOS39: stuff works, is that upon booting the Emergency Disk II floppy, it will check if AmigaOS3.9: exists, and if it doesn't, it will look for AmigaOS39: instead. If the latter can be found, a simple 'Assign AmigaOS3.9: AmigaOS39:' will be run.

AmigaOS 4 (abbreviated as OS4 or AOS4) is a line of Amigaoperating systems which runs on PowerPC microprocessors. It is mainly based on AmigaOS 3.1 source code developed by Commodore, and partially on version 3.9 developed by Haage & Partner.^[1] 'The Final Update' (for OS version 4.0) was released on 24 December 2006 (originally released in April 2004)^[2] after five years of development by the Belgian company Hyperion Entertainment under license from Amiga, Inc. for AmigaOne registered users.^[3]

• 2Description
• 3Development process
• 4AmigaOS 4 prominent features
• 5Compatible hardware

History[edit]

During the five years of development, purchasers of AmigaOne machines could download pre-release versions of AmigaOS 4.0 from Hyperion's repository as long as these were made available.

On 20 December 2006, Amiga, Inc terminated^[4] the contract with Hyperion Entertainment to produce or sell AmigaOS 4. Nevertheless, AmigaOS 4.0 was released commercially for Amigas with PowerUP accelerator cards in November 2007^[5] (having been available only to developers and beta-testers until then). The Italian computer company ACube Systems has announced Sam440ep^[6] and Sam440ep-flex motherboards, which are AmigaOS 4 compatible. Also, a third party bootloader, known as the 'Moana', was released by Acube on torrent sites; it allows installation of the Sam440ep version of OS4 to Mac Mini G4's. However this is both unofficial and unsupported as of today, and very incomplete, especially regarding drivers. During the judicial procedure (between Hyperion and Amiga, Inc),^[7] OS4 was still being developed^[8] and distributed.^[9]

On 30 September 2009, Hyperion Entertainment and Amiga, Inc. reached a settlement agreement where Hyperion is granted an exclusive right to AmigaOS 3.1 and market AmigaOS 4 and subsequent versions of AmigaOS (including AmigaOS 5 without limitation).^[10] Hyperion has assured the Amiga community that it will continue the development and the distribution of AmigaOS 4.x (and beyond), as it has done since November 2001.^[11]

Description[edit]

AmigaOS 4 can be divided into two parts: the Workbench and the Kickstart.

Workbench[edit]

The Workbench is the GUI of OS4, a graphical interface file manager and application launcher for the Operating System. It also includes some general purpose tools and utility programs such as a Notepad for typing text, MultiView for viewing images and Amigaguide documents, Unarc for unpacking Archives, a PDF reader, a number of small preferences programs for changing settings of the GUI and OS, among other programs.

Kickstart[edit]

The Kickstart contains many of the core components of the OS. Prior to version 4 of AmigaOS the Kickstart had been released mostly on a ROM (hardware included with the computer). In OS4 the Kickstart is instead stored on the hard disk. It consists mainly of:

• ExecSG, a preemptive multitasking kernel. ExecSG was licensed to Hyperion Entertainment by Thomas and Hans-Jörg Frieden.^[12][13][14]
• Intuition, a windowing system API.
• AmigaDOS and AmigaShell, the AmigaDOS is the disk operating system for the OS, whereas the Shell is the integrated Command Line Interface (CLI). The CLI and the GUI complement each other and share the same privileges.
• Petunia, a Motorola 68020 processor emulator with dynamic recompilation, also called just-in-time compilation (JIT compilation), for PowerPC based Amigas. It gives OS4 backward compatibility to some extent, it will only run system friendly (following the OS3.x API without communicating directly with the classic Amigas' custom chipset) AmigaOS 3.x programs.^[15] For the programs that Petunia can't handle, such as most 'bang the hardware' (which uses legacy Amiga hardware directly) Amiga games and demos, UAE can be used which can emulate different Amiga chipsets (OCS, ECS, AGA) as well.

Development process[edit]

Download Iso Image

There have been many different versions of the AmigaOS operating system (OS) during its three decades of history.

Versions 1.0 to 1.3[edit]

The first AmigaOS was introduced in 1985 and developed by Commodore International. It was nicknamed Workbench from the name of its Graphical user interface (GUI), due to an error of Commodore Marketing and Sales Department, which labeled the OS disk just with the name 'Workbench Disk' and not with the correct name 'AmigaOS Disk (Workbench)'. The first versions of AmigaOS (1.0 and up to 1.3) are here indicated with the name of their original disks to preserve original custom.

Versions 2.0 to 3.1[edit]

Workbench 2.0 improvements introduced a lot of major advances to the GUI of Amiga operating system. The blue and orange colour scheme was replaced with a grey and light blue with 3D aspect in the border of the windows. The Workbench was no longer tied to the 640×256 (PAL) or 640×200 (NTSC) display modes, and much of the system was improved with an eye to making future expansion easier. For the first time, a standardised 'look and feel' was added. This was done by creating the Amiga Style Guide, and including libraries and software which assisted developers in making conformant software. Technologies included the GUI element creation library gadtools, the software installation scripting language Installer, and the AmigaGuide hypertext help system.

Versions 3.5 and 3.9[edit]

After the demise of Commodore, the later owners of the Amiga trademark granted a license to a German company called Haage & Partner to update the Amiga's operating system. Along with this update came a change in the way people referred to the Amiga's operating system. Rather than specifying 'Kickstart' or 'Workbench', the updates were most often referred to as simply 'AmigaOS'.Whereas all previous OS releases ran on vanilla Amiga 500 with 68000 and 512 kB RAM, release 3.5 onwards required a 68020 or better and at least 4 MB fast ram.

Versions 4.0 and 4.1[edit]

In 2001 Amiga Inc. signed a contract with Hyperion Entertainment to develop the PowerPC native AmigaOS 4 from their previous AmigaOS 3.1 release.^[16] Unlike the previous versions which were based on the Motorola68k central processor, OS4 runs only on PowerPC computer systems. Amiga, Inc.'s (current Amiga trademark owners) distribution policies for AmigaOS 4.0 and any later versions required that OS4 must be bundled with all new third-party hardware 'Amigas', with the sole exception of Amigas with Phase5 PowerPC accelerator boards, for which OS4 is sold separately. This requirement was overturned in the agreement reached between Amiga, Inc. and Hyperion in the settlement of a lawsuit over the ownership of AmigaOS 4.In 2014 Hyperion introduced AmigaOS 4.1 Final Edition incorporating all previous downloadable updates and some new features like unified graphics library with RTG support and support for more than 2 GB RAM.^[17]

Versions 4.2[edit]

In May 2012 Hyperion announced that they were working on AmigaOS 4.2. It would introduce hardware accelerated 3D support, multi-core support, a vastly improved file system API and many other features.^[18]Paperport 12.1 keygen: full version software.

AmigaOS 4 prominent features[edit]

Prominent features compared to other operating systems or previous versions of AmigaOS:^[19]

Appearance[edit]

• Screens: You can have as many different screens as you like for any purpose, each with its own application on it; or you can open a public screen which several applications can share. Switching between screens can be done in an instant, and you can come back to an application and find it exactly how you left it. It is even possible to drag the current screen down to reveal another screen behind it, (even if they have different display resolutions) so that you can view two screens simultaneously, or even drag and drop files and other content from one screen to another.^[20]
• Menuing: The menu bar appears at the top of the screen when the right mouse button is pressed down and disappears when it is not needed, thus reducing screen clutter and giving more room to work.

File handling[edit]

• Descriptive file structure: Operating system files are divided up into clearly labelled drawers (folders). For example, all libraries are stored in 'Libs:' standard virtual device and absolute path finder for 'Libs' directory, Fonts are all in 'Fonts:' absolute locator, the files for language localization are all stored in 'Locale:' and so on.
• RAM disk: A virtual hard drive, it acts like any other disk, and stores files and data in memory rather than on your actual hard drive. The RAM disk is dynamically resizable and takes up only as much of your memory as it needs to. It can be used as a temporary store for your own purposes or as a place for software installers to put temporary files, and is cleared out at reboot so you won't be cluttering up your computer with thousands of unnecessary files that bog down your system. Additionally there is an optional RAD disk, a recoverable version of the RAM disk, which preserves contents after a reboot.^[21]
• Datatypes: Recognises and handles file types: displaying a picture, playing a music file, decoding a video file, rendering a web page etc. Any application can access Datatypes transparently, and thus have the ability to use any file that you have a Datatype for.
• Icon handling: A file can have a default icon representing the type of file or a custom icon specific to the individual file. Additionally icons can store extra commands and metadata about the associated file — which program to open it in, for example.
• Assigning devices: Instead of assigning drives (devices) a letter or fixed label, each drive can be given a name. Drives can be given more than one name so the system always knows where things are, if it is the system boot drive it is also known as 'Sys:'. Areas of hard drive can be assigned a label as if they were a virtual disk. For example, it is possible to mount MP3 players as 'MP3:' and external networked resources as logical devices.

Other[edit]

• Live CD: The OS4 installation CD can be used as a Live CD.
• Dockies: It is a fully configurable docking bar for icons, allowing quick access to most used applications. These dock bar icons, 'Dockies', are fully dynamic, which means they can show real-time content and act as useful micro tools. A Docky might act as a magnifying glass, display the time, or show you the latest weather forecast or stock market information direct from the Internet.
• Scripting: Implemented scripting as a fundamental feature. Using the AREXX scripting language and Python it is possible to automate, integrate and remote control almost every application and function of the computer. Function sets and tools from several applications can be brought together into a single, integrated interface to allow the most complex jobs to be performed with the utmost simplicity.

• The Grim Reaper: The 'Guru Meditation' is replaced by 'The Grim Reaper', a crash handling system that attempts to catch crashes and attempts to stop them from getting out of control. It can provide complete information about the crash and optionally suspend the offending task.
• AmiUpdate: Is an updating system designed purely for the latest incarnation of the AmigaOS 4.^[22] It is able to update OS files and also all Amiga programs which are registered to use the same update program that is standard for Amiga. Updating AmigaOS requires only few libraries to be put in standard OS location 'Libs:', 'Fonts:' etc. This leaves Amiga users with a minimal knowledge of the system almost free to perform by hand the update of the system files.

Compatible hardware[edit]

Amiga[edit]

Released for Amigas equipped with third party PPC add-on boards:

• Blizzard PPC equipped Amiga 1200
• Blizzard 2604e (prototype card) equipped Amiga 2000^{[citation needed]}
• CyberStorm PPC equipped Amiga 3000 or Amiga 4000

AmigaOne[edit]

Released for AmigaOne motherboards:

• AmigaOne-SE (A1-SE)
• AmigaOne-XE (A1-XE)
• Micro-AmigaOne (Micro-A1)
• AmigaOne X1000 (A1X1K; A1-X1000)
• AmigaOne 500 (A1-500), an AmigaOne computer based upon the Sam460ex board introduced by Acube Systems.^[23]
• AmigaOne X5000 (A1X5K; A1-X5000)

Pegasos[edit]

Released for Pegasos systems:

• Pegasos II (Peg2)^[24]

Samantha[edit]

Released for Sam440 systems:

• Sam440ep^[25][6]
• Sam440ep-flex
• Sam460ex^[26]

Versions[edit]

Future[edit]

For the AmigaOS 4.2, Hyperion Entertainment planned the following updates:

• Multiple core support (SMP)
• New ExecSG scheduler
  • Selectable policy for scheduling (may include per task)
  • Scheduling of task groups with internal scheduling of tasks within that group
  • Scheduling of tasks across multiple CPU cores (may include core affinity)
  • Support for real-time scheduling
• Graphics and Gallium3D
  • Enables access to full OpenGL implementations like Mesa
  • Compositing may be done via Gallium3D
  • Opens the door to replacing the entire graphics subsystem
  • multi-header support

See also[edit]

References[edit]

1. ^''Amiga Inc vs Hyperion Trial is Over - Part 2 of 4' (AmigaOS 3.1 source code [7:15])'. YouTube.com. 2009-10-27. Retrieved 2010-09-20.
2. ^Administrator. 'AmigaOS 4.0 Developer Pre-release goes gold'. hyperion-entertainment.biz.
3. ^http://www.hyperion-entertainment.biz/8080/news/2007-01-01^{[permanent dead link]}
4. ^'Announcement at Amiga Inc. official site'. Amiga.com. Archived from the original on July 29, 2008. Retrieved 2010-01-31.
5. ^AmigaOS 4.0 for Classic Amiga gone Gold.^{[permanent dead link]}
6. ^ ^ab'ACube Systems Srl'. acube-systems.biz.
7. ^'Amiga Inc v. Hyperion VOF'. News.justia.com. Archived from the original on 4 January 2010. Retrieved 2010-01-31.
8. ^Hyperion Entertainment news.^{[permanent dead link]}
9. ^'AmigaOS 4 for distribution'. ACube Systems. Retrieved 2010-11-05.
10. ^'Hyperion, Amiga, Inc. Reach Settlement, All Legal Issues Resolved'. OSNews. 2009-10-17. Archived from the original on 19 October 2009. Retrieved 2009-10-18.
11. ^'Hyperion Entertainment CVBA and Amiga Inc. reach settlement'. Hyperion Entertainment. 2009-10-17. Archived from the original on 23 October 2009. Retrieved 2009-10-18.
12. ^'Friedens explain ownership of ExecSG and licensing to Hyperion Entertainment'. amigaworld.net. 2006-11-06. Archived from the original on 2016-03-04. Retrieved 2015-08-24.
13. ^'DECLARATION of Hans-Jorg Frieden filed by Defendant Hyperion VOF'. justia.com. 2007-05-21.
14. ^'Second DECLARATION of Hans-Jorg Frieden filed by Defendant Hyperion VOF'. justia.com. 2007-05-21.
15. ^'Project Petunia'. Almos Rajnai. 2006-12-30. Retrieved 2010-11-10.
16. ^'Amiga/Hyperion contract'. 2010-10-10. Retrieved 2010-09-03.
17. ^'News'. hyperion-entertainment.biz.
18. ^'AmigaOS 4 developer interview: Why it endures and what the future holds'. Computerworld. 2012-05-31. Retrieved 2012-06-02.
19. ^'YouTube video 'Why use Amiga in 2009? - Long cut''. Youtube.com. 2009-03-23. Retrieved 2010-01-31.
20. ^'YouTube video Amiga OS4 Intuition'. Youtube.com. 2007-01-19. Retrieved 2010-01-31.
21. ^Feature Spotlight: The RAM Disk.^{[dead link]}
22. ^'AmigaOS 4 updating system'. Amiupdate.net. Retrieved 2010-01-31.
23. ^'ACube Systems announcement'. acube-systems.biz. Retrieved 2011-10-11.
24. ^'AmigaOS 4.1 for Pegasos II'. Amigaworld.net. Retrieved 2010-01-31.
25. ^OEM Version of AmigaOS 4.1 for SAM440ep imminent.^{[permanent dead link]}
26. ^'AmigaOS 4.1 for Sam460ex'. ACube Systems. 2010-05-13. Archived from the original on 17 May 2010. Retrieved 2010-05-13.
27. ^AmigaOS 4.0 Developer Pre-release goes gold.^{[permanent dead link]}
28. ^First AmigaOS 4.0 Pre-Release update available.^{[permanent dead link]}
29. ^'New AmigaOS Update available'. Hyperion-entertainment.biz. 2004-12-27. Retrieved 2010-01-31.
30. ^'AmigaOS 4.0 Prerelease Update #3 available'. Hyperion-entertainment.biz. Retrieved 2010-01-31.
31. ^'AmigaOS4.0 Developer Prerelease Update #4 released'. Hyperion-entertainment.biz. 2006-02-08. Retrieved 2010-01-31.
32. ^'AmigaOS 4.0 July 2007 Update Available'. Hyperion-entertainment.biz. Retrieved 2010-01-31.
33. ^'AmigaOS 4.0 for classic Amiga computers compatibility list' (in Italian). Acube-systems.biz. 2009-12-22. Retrieved 2010-01-31.
34. ^'AmigaOS 4.0 February 2008 update for CyberStormPPC and BlizzardPPC available'. Hyperion-entertainment.biz. Retrieved 2010-01-31.
35. ^Hyperion Entertainment announces AmigaOS 4.1.^{[permanent dead link]}
36. ^'New AmigaOS 4.1 Quick Fix available'. Hyperion-entertainment.biz. 2009-06-21. Retrieved 2010-01-31.
37. ^'Update 1 of AmigaOS 4.1 available for immediate download'. Hyperion-entertainment.biz. 2010-01-14. Retrieved 2010-01-31.
38. ^'Update 2 of AmigaOS 4.1 available'. Hyperion-entertainment.biz. 2010-04-30. Archived from the original on 2011-07-06. Retrieved 2010-05-01.
39. ^Steven Solie. 'AmigaOS 4.1 Update 3 Released'. hyperion-entertainment.com.
40. ^'AmigaOne X1000 Update 5 CD goes gold!'. Amigans.net. 2012-01-29. Retrieved 2012-01-09.
41. ^'AmigaOS 4 Update 5 is out for all'. Amigaworld.net. 2012-08-16. Retrieved 2012-08-18.
42. ^'Hyperion Releases AmigaOS 4.1 Update 6'. Amigaworld.net. 2012-11-30. Retrieved 2012-12-01.
43. ^'AmigaOS 4.1 Final Edition shipping now!'. Amigaworld.net. 2014-12-18. Retrieved 2014-12-19.
44. ^'Breaking the Memory Barrier - Hyperion Entertainment Blog'. hyperion-entertainment.biz.
45. ^'AmigaOS 4.1 Final Edition available before the end of 2014'. Amigaworld.net. 2014-10-26. Retrieved 2014-12-19.
46. ^'Announcing AmigaOS 4.1 Final Edition, Update 1'. Hyperion-entertainment.com. 2016-12-31. Retrieved 2017-01-01.
47. ^'Final Edition Update 1 is OUT'. Amigaworld.net. 2016-12-31. Post 18 by zzd10h. Retrieved 2017-01-01.

Notes[edit]

External links[edit]