@AMIGASYSTEM

Thanks for testing! Early Boot Menu is activated by adding "bootmenu" grub command switch.

Are you saing that Odyssey font problem is resolved? That Odyssey does not use this weird font by default?

Yes with your latest release "https://axrt.org/development/OWB-1.25-20240112.i386-aros.zip", the Fonts worked fine, see screenshot

In your Build there are no Fonts set to OWB, consequently OWB uses the Font "Carbon" by default, if you set a Fonts present in the Build then the fonts can be changed, with this version of OWB, previously not.

Ok, good. Glad this problem is solved.

Exactly where and how 'bootmenu' is to be added!

To the grub command line, the same way you add 'noacpi' or 'noioapic' options. In the default option in grub press 'e' and then add it after nomonitors. Then press CTRL+x.

Interesting, Early Startup in my opinion could be added in the Menu Grup, useful for minor maintenance, e.g. with Dopus4 one could easily perform editing operations, see screenshot !

deadwood excuse me one more question, what does the 'C Library' improve on AROS and its development?

From user perspective there is no benefit. We already had a C library (arosc) and now this one becomes legacy and stdlib + crt become the new C library. The benefit comes to AROS development itself, where 32-bit version comes more in line to 64-bit version, so bugs can be solved once and maintaince is easier.

deadwood if it is of interest in the attached link, there is a more updated version of diskimage, the diskimage.device seems to be the same version as your Build, while the "MountDiskImage" and "MountHDF" commands are more updated, this version of diskimage does not use stdc/posixc

He talks about HD "HDF" image editing, but then there is no DOSDriver ?
I tried manual editing but it seems to require the Mounter command which does not exist on AROS !

- Mount a single-partition hardfile on IDF0:
MountDiskImage DRIVE IDF0: filename.hdf

- Mount an RDB hardfile on diskimage.device unit 100:
MountDiskImage UNIT=100 rdb.hdf
Mounter D=diskimage.device U=100


https://www.a500...._7z.readme

deadwood do you know whether there will be midi support via usb in the next core updates

@Amiwell79

I don't remember anything related to that.

ok many thanks

yes I didn't mean the next one but maybe later

perhaps in abiv1 it is implemented

I don't know, you'd have to check that.

it seemed to me that nick had worked on this I am not sure though

Amiwell

Midi support updates were mentioned in the ABIv1 chat a few years ago.

Alfred Faust was asking about the CAMD midi driver but no one seemed interested in helping him with that. I don't believe anything has been done as far as updated midi support.

yes now I remember the driver is missing, at this point if there would be it would all work Alfred tried with his midi equipment

miker you would be able to write the driver, you would not do it for free

as Alfred told me, I understand that the only thing missing is the driver to interface with the camd.library the only thing I can do is to look for some programmer and pay him as I have always done