AROS 68k updates from ApollOS repository

[AMIGASYSTEM]

Ok, bug report created: https://github.com/deadw00d/AROS/issues/64

Thanks

[AMIGASYSTEM]

@ deadwood

On AROS x86 I happened a few times to access "Early Startup Menu", I don't remember if with the two pressed Mouse keys or if from the Spacebar.

It seems to be not easy to access Early Startup Menu, to my important for maintenance, I also noticed that the Early Startup Menu GUI is outdated and the cursor moves by itself, basically you can't boot the system "without startup-sequence" as you can do AROS 68k.

It would be nice to have on AROS x86 the new "Early Startup Menu" GUI that you created on AROS 68k !

[deadwood]

@ deadwood

On AROS x86 I happened a few times to access "Early Startup Menu", I don't remember if with the two pressed Mouse keys or if from the Spacebar.

It seems to be not easy to access Early Startup Menu, to my important for maintenance, I also noticed that the Early Startup Menu GUI is outdated and the cursor moves by itself, basically you can't boot the system "without startup-sequence" as you can do AROS 68k.

It would be nice to have on AROS x86 the new "Early Startup Menu" GUI that you created on AROS 68k !

You can enter bootmenu by editing grub command line and adding "bootmenu" argument.

The changes to bootmenu will eventually make their way to x86 AROS once it catches up with Core.

[AMIGASYSTEM]

Ok thanks

[AMIGASYSTEM]

Bootmenu was active on my AROS One x86, you just had to have the Grub window active and be quick to press the spacebar.

I booted the system from the prompt and ran Dopus4, handy for doing any maintenance when the system doesn't boot.

I would like to put Dopus4 on the Grub so that I can boot AROS directly from Dopus4, is this possible?

[deadwood]

No, I don't think so without major development.

[AMIGASYSTEM]

Ok that's ok, I created a little script now at the prompt just type Dopus, noticed that many things work fine like editing text, watch a video listen to music and much more.

I will inform AROS One x86/68k users about this important feature for OS maintenance.

I wanted to create a function key ALT+F1 but there is no Keymaps Editor, FKey unfortunately works only on Wanderer

[OlafS3]

new fixes

perhaps you (Deadwood) could look at it

https://github.com/ApolloTeam-dev/AROS/commit/9bc0a17d5c4702a2a03a2d898cd0009e5b20e5a1
https://github.com/ApolloTeam-dev/AROS/commit/76e477c6682d92ca30a520e7b6f4e1af16d6511b
https://github.com/ApolloTeam-dev/AROS/commit/cefc910dd99968da73df07ff5bbc4caa0f6e067d

[deadwood]

Yes, I've seen those. I generally wait until there a bigger batch of changes before porting, unless there is something that would immediately help someone.

[Mazze]

...now there are also problems with languages, you can not change the language to the system.

Catalogs have a version number. AROS applications try to open a particular version number. If it doesn't match the catalog won't be opened and the default language (usually English) is opened.

See here for Wanderer:
https://github.com/aros-translation-team/wanderer/tree/c4d7be1dd5116b26825f721a41435880c3df159c
You can see in file catalog_version.h the version number 4. That's the required version.
But italian.ct has this line
## version $VER: wanderer.catalog 3.0 (08.06.2017)
i.e. it has only version 3.

Someone has to update the ct files.

[AMIGASYSTEM]

I believe that besides "wanderer.catalog" there are other Italian catalogs with the same problem.

With a Hexadecimal Editor I tried to modify the date of "wanderer.catalog" and it worked, but not everything was lacalized in Italian

[Telematix]

I believe that besides "wanderer.catalog" there are other Italian catalogs with the same problem.

With a Hexadecimal Editor I tried to modify the date of "wanderer.catalog" and it worked, but not everything was lacalized in Italian

I think that the new version has to be translated first (from scratch if it does not exist or updating the previous version).
When the file has been updated and has all the messages that the new version needs, the catalog has to be generated with flexcat. 

Several years ago I tried to update and complete the spanish catalogs and itīs not very difficult:
https://ae.amigalife.org/index.php?topic=651

[AMIGASYSTEM]

Thanks Telematix, I tried FlexCat (it seems to be only for Windows systems) but I have the doubt that the catalogs created are for AROS x86, and not compatible with AROS 68k !

[Telematix]

I used a linux version, compiled from the AROS sources.
Tried it on linux hosted and, when it had no errors, uploaded the source file to the git server so it can be used.

https://github.com/aros-translation-team

[OlafS3]

@AMIGASYSTEM

The closes thing there is to the readme you suggest is commit log of repository: https://github.com/aros-development-team/AROS/commits/master. By comparing build dates with commit date you can derive the change.

If you are looking for full system builds with my changes, they can be downloaded from here: https://build.axrt.org/download/builds/AROS-ABIv11/ with commit log here: https://github.com/deadw00d/AROS/commits/master

A more user-friendly description of changes I'm attaching to full releases (see here: https://axrt.org/index.php?tab=releasenotes-aros-v0). For automated builds this won't be available and you need to use commit history as shown above.

I have a question. The full builds here are identical to the main branch (http://aros.org/nightly1.php) or your specific branch? The commits on main branch (often from Kalamatee) sound interesting but I am not sure what is what. In my case I am of course mainly interested in ABI11 (68k). I have just tested. With your nightly all is ok, in the main download page the fix seens not to be commited on ABI1. What is difference between both? Identical (including recent fixes and additionally yours) or different and only updated from time to time?