Thanks to all concerned with putting this release together.

and thanks MorphOS Team! Good work as usual. I will install it ASAP.

[ Edited by Cego On 2015/6/19 13:43 ]

Great!

What are the changes in the Sdk?

Yeahhh. Thanks MorphOS Team...

Ambient screenbar autohide bug is not corrected from version 3.8....

Impressive yet again; thanks guys!

It's always a pleasure to update, See the message that there's an update, download the .iso, copy the boot.img and boot from .iso file and start the update process. All in all it's less than half an hour.
Nice!

I didnt even finish with 3.8! LOL!

Bad ass! Excellent job guys!

Thanks for the update, will install soon.

Now par with Amiga OS 3.9! Will next be 3.10 and then 3.11 for Workgroups? Or will will it be 4.0 and then 4.1, along with AmigaOS 4.1 and Linux 4.1 on an X5000? :)

I have already updated both (OS and SDK). No problems.
Thank you MorphOS Team!

That was quick.
That leaves 4.0 as our next revision.
With every full X.0 revision usually comes major changes.
Just imagine what could come next.

next version will be 3.10

Thanks MorphOS Team for the update!

Quote:

If MorphOS is planning to make a 3.10 and 3.11 etc. Then it 3.8 should be 3.08, and 3.9 should have been named 3.09. But to my knowledge, they never did this. Using that numbering scheme, I would consider 3.7 to be 3.70, 3.8 to be 3.80, and 3.9 to be 3.90. This makes naming a future release as 3.11 from 3.90 very confusing. Unless MorphOS next release is 3.1.0 and 3.1.1 ...

But I am looking forward to MorphOS version 4.0 ! And perhaps all the dreams of MorphOS will come true. and even more exciting, is that MorphOS release version numbers are "catching up" to AmigaOS release numbers. So not only is MorphOS evolve significantly compared to AmigaOS, MorphOS now release version numbers will soon be larger than AmigaOS! I think it will be very exciting for MorphOS to release MorphOS version 4.2 and 4.3 and 4.4 and onwards, especially before AmigaOS releases AmigaOS 4.2 and 4.3!

@In_Correct

Not at all, AFAIK they simply follow the standard Amiga versioning scheme, version.revision, as outlined by Commodore in the Amiga Style Guide, and after 9 comes 10 and then 11. Thus a 3.7 version is 63 releases prior to 3.70! It's not a decimal system, but a versioning system with two numeric integer placeholders separated by a dot, so there is no need to write "07" or "007" or "0007" instead of 7, if you mean a seven you write a seven!

Using version numbers with three numeric placeholders (major.minor.revision) is perhaps common in the Unix/Linux world, but AFAIK this is "un-amiga", and is something rarely seen both when it comes to SW and the OS itself (with a few exceptions). This is also "illegal" according to the amiga style guide and will break the amiga version string format.



[ Edited by takemehomegrandma On 2015/6/21 0:19 ]

@kolla

Quote:

Possibly 3.10 for X5000. At least that's what the next version should be, with or without the X5000 support.

Compressed Textures do not work in OpenJK:

Setting r_ext_compress_textures "1" will freeze the whole system after opnening the game menu.
I tested it on Power Mac G5 with Radeon 9600XT.

Quote:
Regarding major version bumping, it will probably be done whenever the team feels like there are "major enough" changes to justify that. This isn't Firefox 38.0.5 or Chrome 43.0.2357.124 (These will likely be bumped by at least 10.0.0 by the time you read this, but you get the point).

Remember what happened after MorphOS 1.4?

And regarding VBO support, finally!

Quote:

Some more details would be helpful in order to track this down. Which graphics mode/resolution is selected and is it happening at some fixed position in the game or random ?
It might be a specific issue related to G5 systems.

[ Editiert durch pega-1 Ein 2015/6/23 6:53 ]

THanks for this new update. Can someone please tell something about " ixemul (50.10) and an integrated Scintilla documentation file"?
For ixemul I am interested in Netsurf which used ixemul for all thel atest versions. Just the newest one tries to run without but it still does not work. All the former version need an ixemul library that is not compatible with MOS as was said a while ago. So is this ixemul more compatible with ixemul 60-something? Can we get a better NetSurf this way or what are the differences to former versions?
For the Scintiall thing I did not find anything new about documentation, also the Amiga Guide file is not much updated. What was meant here?

I have recently installed 3.9 on a Pegasos 1 and a Pegasos 2.

I think that I am coming through some crashes when accessing Internet on Peg1.

For example the Download_fonts script would randomly crash and freeze the system on downloading.

I have to run the script several times (after rebooting) to get it completed with no crush... I have used the same script on 3.8 and it worked at once. No crushes. But ok my Internet experience with 3.8 was deadly sort.

Or when I am trying to download mplayer from Fab's site and even on simple navigation (again on Fab's page) it crashed again, system froze. Had to reboot.

I am using the via_rhinepci.device. Tried DHCP and static IP, no change.

I tried to download the same mplayer file on my Pegasos 2 system and also got on IRC no crashes.

Ok my testings were not so extended (some more on Peg1). But I am posting it here.

Any ideas?

ps. Only 256MB of RAM in this machine, could be a reason?

[ Edited by CountRaven On 2015/6/24 4:10 ]

Quote:

Do you get any crash requester from the OWB? Enable Memory sbar module and have an eye on it while using the system, does it go to low figures, like only couple tens of megs free?

Quote:

Unfortunately 68k ixemul versions beyond V50 are broken beyond repair by clueless author. 68k users should upgrade to older version and developers fix their mess.

Quote:

Yes will check that.

EDIT: And I did it well there seems to be plenty of memory available, even when OWB is running.

EDI 2: And I installed the stuff on another Peg1 and it work. So I got to check this machine (perhaps the hard disk cables or my memory stick, or my ethernet cable will go through it).

[ Edited by CountRaven On 2015/6/24 13:22 ]

[ Edited by CountRaven On 2015/6/24 14:17 ]

Quote:

SDK:Guide/Scintilla.guide

Quote:

Right, and it is indexed so that one can right-click on Scintilla keywords in Scribble to get information.

Quote:

Resolution is 1280x1024
It crashes directly after displaying the logos of companies at the menu
(black screen)
Disabling compressed textures leads to a working game.

[ Edited by eliot On 2015/6/25 4:51 ]

So for NetSurf will that new ixemul make it easier to port it to MorphOS? Because there is no light version of OWB anymore this would be a fast alternative.

SDK:Guide/Scintilla.guide : thanks, I found the context menu in Scribble.

Quote:

No. ixemul isn't for UI apps, it's for shell-only nix utils.

Quote:

It got an April fix. I have ordered some new 80 wire ide cables, as it seems problems are focusing on the hard disk access. I have opened a new topic.

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=11247&forum=11

Will check and report back.

BTW Compared to other ftp clients like AmiTradeCenter,
Transfer is again extremely slow. Transfer reaches about 2 MB/sec when downloading
a 600 MB file from ftp server to Ram:. AmiTradeCenter achieves about 6 MB/sec.
Both, server and Mac G5, using GBit ethernet.
My iMac achieves about 28 MB/sec..
My Amiga 4000T with 68060@66MHz also reaches 2 MB barrier, so it runs at same speed as the G5.


EDIT:

Maybe I I am misreading the displayed information of the UI?

Transfer.png

[ Edited by eliot On 2015/6/27 16:40 ]

@ Eliot

According to your picture, Transfer reports 21 MB/s.

[ Edited by ASiegel On 2015/6/27 18:37 ]

Quote:

Yes, I missed the "k".

> I missed the "k".

Wouldn't that be 21 kB then? :-)

Quote:

I see a "k" in your screenshot

And 20889kB/s are ca. 21 MByt /sec

[ Edited by pegasos-sigi2 On 2015/6/29 18:14 ]

>>> According to your picture, Transfer reports 21 MB/s.

>> Yes, I missed the "k".

> I see a "k" in your screenshot ;-)

Else he would've had a hard time missing it, I guess :-)

> And 20889kB/s are ca. 21 MByt /sec :-)

Alreday established in what you quoted.

In Scribble, which AFAIK, is part of the MOS revision release, came as a new version with MOS v3.9. So, I saw there were changed options to Save a file to CMD+w (which seems to have been changed from CMD+s - fairly standard option across many platforms) and Save As has been changed to CMD+s (from CMD+z - which seems a far more logical and standard saving method than what has now replaced it).

Even more troubling is that CMD+W (Upper Case W) is now used for Save ALL, which used to be CMD+w (Lower Case w).

So, I have to ask, has some mix-up occurred during the coding of the choice of the saving options?

I have to say that, as I am so used to using the other methods of saving that I have replaced the new version of Scribble with one of my older release versions - just to save the confusion of saving the wrong file/overwriting a file inadvertently, by pressing what would now be the incorrect key qualification.

If possible please return the keyboard saving options to their more standard original ones.

** EDIT ** Nicholai (developer) pointed out that I can input different keyboard shortcuts, basically to my own choice, by amending them in the settings for Scribble, which I probably had forgotten about, but have now done, which has resolved this matter - so there is no need to reply to this issue with MOS 3.9. ** End of EDIT **

I should also mention that I am also noticing strange download speeds being quoted by OWB in the Download window giving me spurious quotes of downloads of 3.9Gb, and sometimes 560kB for all my downloads, ( 20 active download files at a time) when my broadband service offers/supplies me with a maximum 412kb service (I know I can get a much faster service if I wanted, but it's all I need) when it is running, but the system sems to be saying it is handling much faster speeds than it is capable of.

I am often getting lock-ups, stalling of activity of USB data lines, saving to HDD/USB stick on a USB spur, seems to be the main issue during protracted periods of downloading which my system did not suffer from when using v3.7 (never installed v3.8 - too many problems with it for me to consider installing it, for my liking).

The whole system then seems to hang, and I cannot save a document or other file, during this problem, while doing some downloading, to any other HDD on the system, and so I lose all the data in the currently being worked on file, which is really very annoying, which again, never happened when I was using v3.7.

Anyone else suffering the same issues/concerns?

[ Edited by NewSense On 2015/7/25 1:26 ]

[ Edited by NewSense On 2015/7/26 2:53 ]