Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: eliyahu on January 02, 2016, 11:03:14 PM
-
via muidev.de (http://muidev.de/)...
The MUI for AmigaOS development team is proud to announce the immediate release of version 4.0-2015R4 of the Magic User Interface for AmigaOS4/PPC and AmigaOS3/m68k.
Please find the release archives in our download section (http://muidev.de/downloads/).
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.
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.
-
Thanks for the post.
-
This MUI4 for 68k is quite silly, because most of Amiga users have 68030 Amiga. 68060 Amigas are so expensive its not even funny. Vampire 600 V2 card might help here, but for AGA owners there is still no solution.
MUI 3.8 works very nicely on my A1200 68030 50MHz with 64MB RAM. MUI4 just tilts the machine and is so unstable its really painful. MUI4 on MorphOS is however fast.
Tried to run Ibrowse 2.4 with MUI4 on my A1200. Ibrowse gave only IBrowseNetwork System errors and AmIRC thought the stacksize is too low when its more than 32000. Everything is ok with maxtransfer on my SFS partitions et.
I dont get how MUI 3.8 can run fine, while MUI4 struggles so much? Sorry for beeing negative here, but the goal should not be to say WinUAE is minimal requirements.
-
This MUI4 for 68k is quite silly, because most of Amiga users have 68030 Amiga. 68060 Amigas are so expensive its not even funny. Vampire 600 V2 card might help here, but for AGA owners there is still no solution.
MUI 3.8 works very nicely on my A1200 68030 50MHz with 64MB RAM. MUI4 just tilts the machine and is so unstable its really painful. MUI4 on MorphOS is however fast.
Tried to run Ibrowse 2.4 with MUI4 on my A1200. Ibrowse gave only IBrowseNetwork System errors and AmIRC thought the stacksize is too low when its more than 32000. Everything is ok with maxtransfer on my SFS partitions et.
I dont get how MUI 3.8 can run fine, while MUI4 struggles so much? Sorry for beeing negative here, but the goal should not be to say WinUAE is minimal requirements.
On Aros Vision i have no interest to integrate MUI4 because there is no software needing it. Even worse at least one MUI-Application (Wildfire) do not recognize it and not works. So it is completely useless to me. Perhaps it looks better but for me it is more important that all applications work.
-
On Aros Vision i have no interest to integrate MUI4 because there is no software needing it. Even worse at least one MUI-Application (Wildfire) do not recognize it and not works. So it is completely useless to me. Perhaps it looks better but for me it is more important that all applications work.
can you go ahead and report the wildfire issue to the team? they're always looking for feedback.
-- eliyahu
-
I dont get how MUI 3.8 can run fine, while MUI4 struggles so much? Sorry for beeing negative here, but the goal should not be to say WinUAE is minimal requirements.
It would be nice if they'd taken MUI3.8 and built on it, incrementally, made small updates and modernizations, and checked and maintained backward compatibility with the older version as they went. I mean, I'm no software developer, but that's what I would've done.
I don't think this was the case, here. If I understand correctly MUI4 for classic systems / 68k was a backport of the MOS version, which was done by a completely different team from the original developers?
Have yet to see a single post from anyone running MUI4 on a classic system "without issue". Of course would like to be proven wrong, and hope they keep up development - "maybe it'll work someday" - but just glad they remembered to include the disclaimer "Yes, this says it's for 68k/classic. No, it probably won't work on your 68k/classic system". LOL. ;)
-
It would be nice if they'd taken MUI3.8 and built on it, incrementally, made small updates and modernizations, and checked and maintained backward compatibility with the older version as they went. I mean, I'm no software developer, but that's what I would've done.
I don't think this was the case, here. If I understand correctly MUI4 for classic systems / 68k was a backport of the MOS version, which was done by a completely different team from the original developers?
Have yet to see a single post from anyone running MUI4 on a classic system "without issue". Of course would like to be proven wrong, and hope they keep up development - "maybe it'll work someday" - but just glad they remembered to include the disclaimer "Yes, this says it's for 68k/classic. No, it probably won't work on your 68k/classic system". LOL. ;)
I am no expert for MUI history so someone else can correct me if I am wrong. How everyone knows was and is MUI the software from Stefan Stuntz who later became part of the MorphOS team and MUI became integral part of MorphOS (the desktop is based on it). Stefan Stuntz developed 3.9 and the first version of 4, later that development was taken over by others. As far as I know is Stefan Stuntz not actively developing anymore (most of the time travelling around) but of course I do not know that just guessing. So version 4 was done by the same developer. The devs from AmigaOS camp got access to 3.9 code (lately it was indicated that they even had access to early 4 code) and were allowed to take a snapshot of that. So code of todays MorphOS MUI4 has nothing (or at least not much) to do with "MUI4" on AmigaOS because the devs there only got the snapshot and had later no access anymore and try to add MorphOS MUI4 features.
-
can you go ahead and report the wildfire issue to the team? they're always looking for feedback.
-- eliyahu
I will...
-
as i understand this mui4 makes use of aiss. if the imagery is too heavy for amiga hardware, how about a low color iff option?
-
What I learn now is that this new MUI4 version for 68k/PPC is incompatible with MUI4 version which is for MorphOS. How silly is this? Yes, OWB for AmigaOS 4 needed MUI4 maybe, but then this starts a new fight that no one wants to have in Amiga community.
Jens of this MUI4 version should never ever get support. Also that they legitimate the whole thing by releasing MUI4 68k? MorphOS had MUI4 for many years now that works nicely. If Jens MUI4 and MorphOS MUI4 is incompatible its just silly. People programming 68k Amiga apps should use MUI 3.8 still.
Please stop this nonesense Jens! This is not community friendly thing to do!
-
I am no expert for MUI history so someone else can correct me if I am wrong. How everyone knows was and is MUI the software from Stefan Stuntz who later became part of the MorphOS team and MUI became integral part of MorphOS (the desktop is based on it). Stefan Stuntz developed 3.9 and the first version of 4, later that development was taken over by others. As far as I know is Stefan Stuntz not actively developing anymore (most of the time travelling around) but of course I do not know that just guessing. So version 4 was done by the same developer. The devs from AmigaOS camp got access to 3.9 code (lately it was indicated that they even had access to early 4 code) and were allowed to take a snapshot of that. So code of todays MorphOS MUI4 has nothing (or at least not much) to do with "MUI4" on AmigaOS because the devs there only got the snapshot and had later no access anymore and try to add MorphOS MUI4 features.
Good summary, Olaf.
MUI4 for AmigaOS has been created by parties other than those that worked on 3.9 and 4.0.
What sources they had access to is somewhat speculative, but as they can't use the MorphOS version calling it MUI4 is somewhat deceptive.
-
Even the 68k version of 3.9 causes all kinds of issues on a real Amiga. I have a CSPPC/060 and it didnt run correctly. Cost me hours of attempting to get it stable with the only result in a new install of OS3.9 and putting back MUI 3.8 again.
I dont think this is intended for real Amiga machines. Its more geared at Amikit and UAE systems. Sadly WinUAE has caught up and in just about all cases now is faster than the real thing with better resources.
-
Even the 68k version of 3.9 causes all kinds of issues on a real Amiga. I have a CSPPC/060 and it didnt run correctly. Cost me hours of attempting to get it stable with the only result in a new install of OS3.9 and putting back MUI 3.8 again.
I dont think this is intended for real Amiga machines. Its more geared at Amikit and UAE systems. Sadly WinUAE has caught up and in just about all cases now is faster than the real thing with better resources.
@Iggy
thanks :)
@Thread
I would say it this way... for MorphOS optical improvements make a lot of sense because you have enough resources and the desktop is based on it. On AmigaOS it is not used for that but propably they have the motivation to compete with MorphOS. For 68k it is (besides for someone using Scalos) only a GUI toolkit for applications, considering the problems it causes (how many people have already reported) and that there is no application needing it, it makes not that much sense. On slower hardware the high requirements are another problem. And even when you would have faster hardware (Vampire 2) why artifically slowing it down without real benefits. My personal view on that.
-
considering the problems it causes (how many people have already reported) and that there is no application needing it, it makes not that much sense.
It causes confusion, that's the frustrating part. People come along who might be new to the scene, or just coming back after decades, and they won't know about all these reported problems. They'll just go into Google and search out "the latest version of MUI", and then get stuck with this mess. I'm just kvetching, not really sure what to do about this other then comment annoyingly in as many threads as possible, LOL. ;)
On a side note, I noticed the registration page for MUI (http://www.sasg.com/cgi-sasg/order_info?app=mui) is still active. I tried to register it a year or so back, not because I expected anything, but just because I felt like it was the right thing to do (after using "copies" of the program all through the '90s). Didn't get any response to my payment, but a "thank you" email at least, would've been nice. :(
-
the registration page for MUI[/URL] is still active. I tried to register it a year or so back, not because I expected anything, but just because I felt like it was the right thing to do (after using "copies" of the program all through the '90s). Didn't get any response to my payment, but a "thank you" email at least, would've been nice. :(
Stunzi is travelling the world with his mountainbike most of the time and blogging about that. He was cycling South-America from spring 2014 to early 2015 and a bit later was off again to Italy for a while. I guess he just had no time to respond.
Stunzi's website: http://www.alpenzorro.de - quite a freak (in a definitely positive manner)
-
Thanks to developers for the new version. Please keep the updates coming.
@thread
As the readme says this version is targeted at powerful systems. Either get one or use MUI3.8 instead. But stop whining please. I am happy that someone is still developing something for 68k, especially in 2016!
-
Thanks to developers for the new version. Please keep the updates coming.
@thread
As the readme says this version is targeted at powerful systems. Either get one or use MUI3.8 instead. But stop whining please. I am happy that someone is still developing something for 68k, especially in 2016!
not everything is "whining". I do not wine, I just state that oviously not all 68k software is working with it, and I have not digged deeper. Also there is no 68k software needing it. Others have stated that it made their system unstable and software is not working or at least not fully. The high demands is just one aspect there.
-
@OlafS3
In that case you might want to use the following website instead: https://muidev.de/query
-
Thanks to developers for the new version. Please keep the updates coming.
@thread
As the readme says this version is targeted at powerful systems. Either get one or use MUI3.8 instead. But stop whining please. I am happy that someone is still developing something for 68k, especially in 2016!
I agree its awesome and enjoy it a lot on the latest AmiKit releases. It just needs to be made very clear that this isnt for the average Amiga machine is all.
-
I am no expert for MUI history so someone else can correct me if I am wrong. How everyone knows was and is MUI the software from Stefan Stuntz who later became part of the MorphOS team and MUI became integral part of MorphOS (the desktop is based on it). Stefan Stuntz developed 3.9 and the first version of 4, later that development was taken over by others. As far as I know is Stefan Stuntz not actively developing anymore (most of the time travelling around) but of course I do not know that just guessing. So version 4 was done by the same developer. The devs from AmigaOS camp got access to 3.9 code (lately it was indicated that they even had access to early 4 code) and were allowed to take a snapshot of that. So code of todays MorphOS MUI4 has nothing (or at least not much) to do with "MUI4" on AmigaOS because the devs there only got the snapshot and had later no access anymore and try to add MorphOS MUI4 features.
MorphOS has been based on MUI5 for quite a while now.
-
AROS uses Zune. MUI4 was solely developed for OS4 so that OS4 could have OWB, it was a matter of "browser envy". The idea to "backport" it to m68k was AmiKit's idea I think, I suppose it too was for OWB? Anyways, people can spend their time, RAM and CPU cycles however they want. Remember back in the 90ies, there was a strong "anti-MUI" sentiment back then, because of bloat and "un-amiga" way of doing things, and that was MUI3.
PS - great to hear that Stunzi is living his dream riding his bike all over the world still, more people here should follow his example :)
-
This MUI4 for 68k is quite silly, because most of Amiga users have 68030 Amiga.
Most Amiga users use WinUAE or FS-UAE, not old hardware :hammer:
-
I agree its awesome and enjoy it a lot on the latest AmiKit releases. It just needs to be made very clear that this isnt for the average Amiga machine is all.
imho it shouldnt be handled like that. amiga applications should be made with possibly good scalability in mind, since the common denominator is by today standards rather weak hardware. uae demanding eye candy should be optional. otherwise we, and beyond everyone else, the developers themselves, end up with unmaintainable versions mess, where practical end user support is simply beyond the available resources.
and im not saying this to particularly criticize the package in question. i think this paradigm should apply where possible, as alas it has been compromised too much, quite against the genuine amiga philosophy about a slim, resource sparing software.
i think genuine amiga hardware should be in this respect still a good reference for ng systems such as aros, even if the actual software, run on it, may happen to be more demanding.
-
PS - great to hear that Stunzi is living his dream riding his bike all over the world still, more people here should follow his example :)
Must be nice, the rest of us have to work for a living. Guess he struck it rich being an Amiga software developer? :laughing: :laughing:
-
Must be nice, the rest of us have to work for a living. Guess he struck it rich being an Amiga software developer? :laughing: :laughing:
You don't have to be rich to do this kind of thing, it is more a matter of prioritizing and making choices, and not be afraid to pick up stray jobs along the route and do some volunteer work for food and shelter here and there.
-
You don't have to be rich to do this kind of thing, it is more a matter of prioritizing and making choices, and not be afraid to pick up stray jobs along the route and do some volunteer work for food and shelter here and there.
LOL. Doesn't work that way in the US. Unless you have wealthy parents, I suppose. :p
-
LOL. Doesn't work that way in the US. Unless you have wealthy parents, I suppose. :p
Nah, it can work that way, here, it's just that in our practice we're fairly well separated from those who do. Think of them as "micro-contractors." I knew a guy a long time ago who moved from place to place and worked offering himself as a handy-man or for construction where ever he went. I actually met him after he finished a six-month stint on a fishing boat.
Of course, there's a lot of business and union regulation in some areas which would prevent that. Stupid things like needing a low-voltage certification to run network cable.