Posts for the month of February 2015

MUI 4.0-2015R1 for AmigaOS4/PPC and AmigaOS3/m68k released

The MUI for AmigaOS development team is proud to announce the immediate release of version 4.0-2015R1 of the Magic User Interface for AmigaOS4/PPC and AmigaOS3/m68k. Please find the release archives in our download section [​​​​http://download.muidev.de/].

Like all former releases a keyfile is required to enable all available settings. Old keyfiles from MUI 3.8 can be used without any restriction.

This is the first public release of MUI4 for AmigaOS3/m68k after it has been distributed together with AmiKit8 already.

Please note that MUI4 for AmigaOS3/m68k is definitely targeted at powerful systems with a fast CPU and a fast graphic board. Although it is still possible to run this release on a real 68k machine an emulation like WinUAE is very highly recommended. Also colormapped screens with 256 colors at most are still supported, but MUI4 makes heavy use of fancy truecolor images and effects which cannot be provided on colormapped screens with the full range of possibilities.

MUI 3.9-2015R1 for AmigaOS3/m68k released

The MUI for AmigaOS development team is proud to announce the immediate release of version 3.9-2015R1 of the Magic User Interface for AmigaOS3/m68k. Please find the release archive in our download section ​​​​​​http://download.muidev.de/

This will be the last release of MUI 3.9 for AmigaOS3. All further development efforts will be put into MUI4 which has been released in parallel. At least a 68020 CPU is required. A faster CPU and a graphic board is highly recommended. Additionally MUI 3.9 will make use of 3rd party system extensions like AfAOS.

Like all former releases a keyfile is required to enable all available settings. Old keyfiles from MUI 3.8 can be used without any restriction.

The development of MUI 3.9 will be stopped after this release. However, if you nevertheless encounter any bugs then please report them in the bugtracker along with a verbose description of the problem as well as detailed instructions on how to reproduce the issue. It is possible that this bug still exists in MUI4, because it inherits many code passages from MUI3.x.