OS 4.1 Update 3 Released

[HammerD]

It's not about positive/negative, but the fact that Hyperion now has released, to their paying customers(!), a piece of software that seems to be totally untested and probably not even finished developing in the first place. How they can do this is mind-boggling. They apparently are completely clueless. IMHO this puts the "X1000 booting OS4.1.3" thread in completely new light.

This must be the worst OS4 release *ever* (but what can you expect when you beg your paying customers to handle the OS development for you), it's obviously breaking the most fundamental and basic things for many users (like MUI and USB) that at least seemed to be working in OS4.1.2!

And this is how the Lead Developer comments this:

"Both IBrowse and YAM are 3rd party so I suggest you talk to the author(s) directly."
http://forum.hyperion-entertainment.biz/viewtopic.php?f=14&t=271#p3491

I mean, OMG! Can't believe I'm reading that! Like: "We ****ed up the OS so the 3rd party apps you have been using for a decade suddenly don't work anymore, but that's not our fault". I'm out of words, don't know what to say. I'm just amazed...

You're making alot of assumptions here based on a few very early initial reports.  Some of these issues have subsequently been solved by users, and are software issues based on what the user has changed in their system.

On a cleanly installed system (OS4.1 Update 1, then Update 2, then Update 3), most of these issues are not reproducible, which means something else is causing the issue, such as a old MUI class, old library version, broken sobjects, etc etc.

IBrowse works fine, FYI, if your system is installed properly.

So please hold back on your judgements until the dust settles and we can have a chance to analyze and assist users with their configurations and issues.  It's quite possible it is not a problem with the OS itself.

The official support forums are on the Hyperion server so the technical support for paying customers is there.

[HammerD]

How do you install system "not cleanly"?

What i mean is a user could have replaced libraries or other system files such as MUI classes or modified s-s or be running some 3rd party software...

It's always best to start from a formatted partition, IMHO.

It's not required, but if a user is experiencing issues we either need to track them down or start from a known state.

[HammerD]

I think there was a similar thing in Windows95 (or was it win 98?)

But does that make it *a good way* then? Especially since your update script seems to demand a clean-slate install anyway?

I mean, *you could* also do it like this:

http://www.morphos-team.net/morphos-2.0.iso
http://www.morphos-team.net/morphos-2.1.iso
http://www.morphos-team.net/morphos-2.2.iso
http://www.morphos-team.net/morphos-2.3.iso
http://www.morphos-team.net/morphos-2.4.iso
http://www.morphos-team.net/morphos-2.5.iso
http://www.morphos-team.net/morphos-2.6.iso
http://www.morphos-team.net/morphos-2.7.iso

Of course there is an upgrade option in the installer.

From many comments on various forums, it seems to me that this is what the customers wants? I don't see the point in denying it to them?

I mean, what's the problem?

A clean partition is not required, update 3 only requires Update 2 to already have been installed.

The situation is no different on MorphOS, except MorphOS hides the real MorphOS system files in a way that is not done on OS4.  But there have been many cases where users have replaced Morphos classes or system files then run into problems.   The solution was not to replace those files.  That is no different than OS4.

In any case, the issue can be solved either by tracking down the specific issue or starting from a known working baseline.

[HammerD]

Well, what was the latest version released as a complete ISO then? OS4.1.2? OS4.1.1? To make a clean-slate install you would have to start from there (wherever that is), and then start adding all subsequent updates, one after another, until you have reached the latest one...

4.1 Update 1 was a full ISO.  Update 2 was an installer as is Update 3, so the sequence is 4.1 Update 1 ISO, Update 2, then Update 3.  For AmigaOS 4.1 Classic it's just Update 3 as it is already at the Update 2 level.

...which is very different from the MorphOS way. You can download any of the above MorphOS versions and boot/install directly from the CD. Clean-slate, or upgrade, your choice. But here is the thing - you don't have to! The reason to why only the latest version is linked to from the MorphOS Team's webpage, is because that's all you'll need! No need to install x amounts of prior OS versions, and then upgrade from that.

Does it not backup your mossys: directory and install a new one every time, even if you do an upgrade? I don't really see your point.  MorphOS is coming as full releases, and not update packages, so obviously there will be a difference.  I don't see why you are making a fuss over this.

Only one download needed, always, and it's an ISO, always!

That's a design decision.  It has its good points and weak points.  One weak point is that you have to download an entire ISO, burn it, just for the "updates" to go from 2.6 to 2.7.

Yes, and this didn't happen by a random coincidence, it was a design decision. And a very good and clever decision too, with hindsight to this OS4.1.3 release (and others as well)! Upgrades goes much smoother on MorphOS, thanks to this!

Again this is a design decision, and may have been influenced by the fact that the MorphOS team didn't work from the original source code, so they separated all their things in their own directory, rather than directly updating the components themselves (because they didn't have access to them.  Effectively you have two sys: assignments which is not required for OS4 since it *is* the original.
[/quote]

If some moron breaks all recommendations and instructions and starts removing or modifying things in the system's exclusive, "don't-touch" MOSSYS, and starts relying on that, rather than use the proper user-space SYS for this, then they are completely on their own when it's time to update, and they have only themselves to blame for any problems. The "moron-protection" only goes that far you know... :p

Well this is no different than the case of OS4, if you go replacing sobjects or system libraries....

All this is obviously *very* different from OS4...

I disagree...but then again I don't think we can ever agree since you are so firmly entrenched into the MorphOS side for some reason.