Deluxe Music 2.0 Font issues on AROS/68k

[Ran755]

Describe the bug
Deluxe Music 2.0 issues on AROS/68k are crashing (or something similar)
Deluxe paint seems to be inflicted by the same bug

To Reproduce
AROS Vision (downloaded from 2025) ROMs are paired with WinUAE's C= Amiga hardware i.e. "Expanded WinUAE example configuration", which is a 68040-based Amiga.

With C= Amiga display chipset with AROS Vision (downloaded from 2025):

1. Double-clicked DMusic2's icon.
2. Prompts "File to Print to..." bug. Click on the Ok button to remove the nag.
3. Graphics render problem with C= Amiga's graphics chipset i.e. graphics render glitches.
4. Select the open function.
5. Illegal instruction software failure prompt.

Like DMusic 2, graphics render glitches are common with Music X 2.0 (1994).

AROS Vision's Directory Opus environment and basic Workbook are used.

Expected behaviour
running, opening menus without crash (srry, couldn't describe the problems more detailed)

---

This function had previously been documented that it would accept a null font. This practice is discouraged.
o Use of a RastPort with a null font with text routines has always been incorrect and risked the guru.
o Keeping an obsolete font pointer in the RastPort is no more dangerous than keeping a zero one there.
o SetFont(rp, 0) causes spurious low memory accesses under some system software releases.

As of V36, the following Amiga font variants are no longer directly supported:
fonts with NULL tf_CharSpace and non-NULL tf_CharKern.
fonts with non-NULL tf_CharSpace and NULL tf_CharKern.
fonts with NULL tf_CharSpace and NULL tf_CharKern with a tf_CharLoc size component greater than tf_XSize.
Attempts to SetFont these one of these font variants will cause the system to modify your font to make it acceptable.

---

Screenshots

Architecture

• AROS

CPU

• UAE (any?) emulated m68k

Version
AROS Vision (downloaded from 2025)
Srry I'm describing the product for someone else and don't have an installation installed to check it.

Additional context
Discussion here (sadly without further precise information)
https://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=45830&forum=2&start=80&viewmode=flat&order=0
https://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=45830&forum=2&start=80&viewmode=flat&order=0

Could be related to the asl.library

I have not checked what exactly that InputHandler in DeluxeMusic is doing. I just noticed that it seems to mess up some InputEvents or something and things don't work as they should like when clicking on the "keys" ( ?) in this "piano" (?) window to produce sound. Or when placing notes in the notation window. Sometimes did not work and you needed to press/release control key to make it work again.

It works with the InputHandler disabled. It just looks uglier. As when clicking in tool windows, the main window is shortly made inactive and then active again.

Also there were gfx problems, unless telling DeluxMusic to run on WB screen which has also to be set to use some PAL screenmode.

[cdimauro]

The second link is like the first one. I assume that you want to share this https://amigaworld.net/modules/newbb/viewtopic.php?topic_id=45837&forum=47 one instead.

Regarding the asl.library, a problem might be related to a tag which DMusic 2.0 uses on ASLFR_HookFunc. According to what was reported here: https://amigaworld.net/modules/newbb/viewtopic.php?topic_id=45830&forum=2&start=60&mode=viewtopic&viewmode=flat&order=0#883018 DMusic uses 80080007 (a tag?), but the user suggest to use 88880007 instead for AROS.