How does this new ceasefire affect ZORRAM?

_________________
Sent from my Quantum Computer.

@DiscreetFX

YOU MY FRIEND, YOU JUST AFFECTED ZORRAM
by stealing my thunder. I was waiting for post 59 to ZORRAM this brand new page.

ALAS, you beat me to it.

Because what's left to do on this amiga world of ours if not yell and yawp and scream and furiously dance a primal dance?

The few ones who made sense, left long ago.
The rotten one who festered around also seem to have left, just like vermin flee a sinking ship.
The good old topics of yore have worn everyone out.

I and a secret partner had a sound ppan to ferry the whole Amigaworld experience to a new promised land, including its legacy of madness, its awful yet beloved baggage. But that is gone too, abandoned not for a lack of feasibility but rather sheer ennui.

SO HERE WE STAND AGAIN, LEFT TO ZORRAM.
And another day begins/ends.

VVVVVVVOOOOOOOOOORRRRRRRRRRRRR4

- "mega" rj mical, esquire, phd

_________________
I HAVE ABS OF STEEL
--
CAN YOU SEE ME? CAN YOU HEAR ME? OK FOR WORK

@OlafS25

Quote:

OlafS25 wrote: @Hammer and I give a shit if you like it or not

Then the feeling is mutual. Your "Amiga" is fake.

Last edited by Hammer on 02-Apr-2026 at 03:31 AM.

_________________

@kolla

Quote:

kolla wrote: @Hammer So what’s preventing Deluxe Music from working? Is it tied to Paula? What exactly have you tried?

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.

I haven't tried IntroCAD 3.0 Plus (1990), XCAD 2000 v1.1 (1992) on AROS Vision.

British Amiga magazines included many full application software programs on cover disks and CDs.

-------------

I do have the AutoCAD R12 Mac 68K edition when "industry standard" is needed.

Last edited by Hammer on 02-Apr-2026 at 03:25 AM.
Last edited by Hammer on 02-Apr-2026 at 02:54 AM.
Last edited by Hammer on 02-Apr-2026 at 02:51 AM.

_________________

since the previous legal thread is completely fscked up by the trolls, and this one is only partially, here is some news from PACER:

Date Filed # Docket Text
03/31/2026 173 MINUTE ORDER: The following MINUTE ORDER is made by direction of the Court, the Honorable Ricardo S. Martinez, United States District Judge: On June 12, 2025, the Ninth Circuit Court of Appeals remanded this case on certain issues. Dkts. #171, #172. Since that date, no other action has occurred in this case. Therefore, the Court DIRECTS the parties to file a Joint Status Report on the remaining issues in this case. This Joint Status Report shall not exceed six (6) pages and shall be filed no later than May 1, 2026.(ALW) (Entered: 03/31/2026)

@OlafS25

Quote:

OlafS25 wrote: @kolla I first not understood what he really does with nonsense like "Aros Vision Roms", never heared of that.

https://www.aros-vision.de/

Google search is easy to use.

Quote:

There are also no "amigaforever roms", "amikit roms" or "betterwb roms".

There are Amiga Forever ROMs i.e. Kickstart ROMs from Cloanto.

The specific Amiga Forever ROMs are the the Kickstart 3.X (3.10) ROM that is included with Cloanto's Amiga Forever.

Google search "Amiga Forever ROMs" returns points to https://www.amigaforever.com/kb/13-114


Quote:

But from context it seems he uses the included aros roms to boot his music software from adf. Then with aros roms "workbook" is started, a cut down and vastly not tested minimalistic desktop.

Booting into AROS Vision's Directory Opus environment does NOT change the show-stopper results.


Quote:

But saying aros vision is useless because aros roms not perfectly work with this old software is like booting with 3.1 roms and if it not works saying shit and useless amigaos or Amikit.

AmigaOS 3.1's backward compatibility is many times superior when compared to AROS Vision.

My AmigaOS reference environments are
1. C= AmigaOS 3.1,
2. Haage & Partner's AmigaOS 3.9,
3. Hyperion Entertainment's AmigaOS 3.2,
4. Amiga Corp/Cloanto's Kickstart 3.10/Workbench 3.10 from Amiga Forever 11.

I sometimes use Hyperion Entertainment's AmigaOS 4.1 FE Update 3 with C= Amiga and SAM460.

Don't equate C= AmigaOS 3.1's backward compatibility results with AROS 68K's.

Last edited by Hammer on 02-Apr-2026 at 03:59 AM.
Last edited by Hammer on 02-Apr-2026 at 03:29 AM.
Last edited by Hammer on 02-Apr-2026 at 03:22 AM.
Last edited by Hammer on 02-Apr-2026 at 03:19 AM.

_________________

@OlafS25

Quote:

Deluxe Music is from 1986. I doubt that it works on any modern environment. Hammer uses it obviously in UAE with 1.3 ROMs

That's 100 percent wrong.

My Deluxe Music 2.0 (1993) testing includes major AmigaOS environment reference points i.e.
1. Commodore-Amiga Inc's AmigaOS 3.1,
2. Amiga Corp/Cloanto's Amiga Forever 11's Kickstart 3.10/Workbench 3.10.
3. Hyperion Entertainment's AmigaOS 3.2.
4. Haage & Partner's AmigaOS 3.9.

Deluxe Music 2.0 displays correctly on Workbench P96 RTG.

I use WinUAE 6.0.3, not "UAE".

----------------------------

For the record, with Deluxe Music 1.0 (1986), just for you.

Test 1: WinUAE's A1200 with Kickstart 3.1 and Deluxe Music 1.0 (1986) boot disk
Result: loads Deluxe Music 1.0 and plays the test music project.

Test 2: WinUAE's A1200 with Kickstart 3.2/Workbench 3.2 hard disk, and Deluxe Music 1.0 (1986)
Result: loads Deluxe Music 1.0 and plays the test music project.

Kickstart 1.3 is not needed when Kickstart 3.1 and Kickstart 3.2 ROMs are okay for Deluxe Music 1.0 (1996) and Deluxe Music 2.0 (1993).

Equating AROS 68K's backwards compatibility being like AmigaOS 3.1 / AmigaOS 3.2 is in dreamland.


Compaq's clean room method involves running a 3rd party software collection to make sure their clean room implementation behaves like the original IBM PC BIOS.

AROS advocates are not up to Compaq's clean room standard. This is why AROS 68K will not displace the original.

Last edited by Hammer on 02-Apr-2026 at 06:03 AM.
Last edited by Hammer on 02-Apr-2026 at 04:23 AM.
Last edited by Hammer on 02-Apr-2026 at 04:22 AM.
Last edited by Hammer on 02-Apr-2026 at 04:20 AM.

_________________

@Hammer

are you able to read hammer?

There is no "Aros Visions workbook" or "Aros Visions roms"

It is a distribution based on aros roms and included there is "workbook"

It is like there is no "betterwb" roms but based on 3.1 roms

Do you understand that? Or is it still too complicated for you to understand?

@Hammer

Messed around a bit with Deluxe Music on AROS 68k, today.

Use "Typeface" from Aminet to load and resave the fonts DMusic/8 and DMusic/16. For some reason they have NULL tf_CharKern, altough they are proportional. AOS3 seems to correct this problem at load/run time. AROS doesn't so during use bad things happen. Like text extent calculations give negative width for template to be used by Text/BltTemplate.

Next, patch the DMusic program itself with a hex editor. There are four longs in there "80080007". Change to "88880007".

80080007 == ASLFR_HookFunc. The program relies on the function to get its small-data-whatever-base-pointer in A4 register. When MorphOS initialliy still used AROS asl.library, they added some code to deal with this, but it isn't compiled in for AROS.

I have not checked if all occurencies of 80080007 in the program file are really all ASLFR_HookFunc usages. If one or more is not, you probably get a crash somewhere else as free bonus.

After starting the program use Scout to ~disable the InputHandler "MKSoft ToolWindow" by setting it's priority to very low value. This thing doesn't work correctly in AROS, but is otherwise used to allow clicking into toolwindow gadgets without deactivating main window.

@OlafS25

Maybe someone who has installed AROS vision should test if popular software works and if the problems are related to AROS 68k or to the UAE (and its settings) that is used.

I can imagine some problems with software accessing Paula and waiting forever when setting the emulated chip to MIDI bit rates.

@dalek

Quote:

since the previous legal thread is completely fscked up by the trolls, and this one is only partially, here is some news from PACER:

Oh, I think we've gone way beyond partially...

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@OneTimer1

he boots obviously direct adf with roms so it has nothing to do with the distribution

@OlafS25

Quote:

OlafS25 wrote: @Hammer are you able to read hammer? There is no "Aros Visions workbook" or "Aros Visions roms"

WinUAE 6.0.3.'s AROS ROM also shows "Workbook".

"Aros Visions workbook" refers to a specific 68K AROS distribution that shows "Workbook" when the AROS Vision HDD installation is replaced by a bootable floppy disk.

It doesn't matter which boot methods are used; AROS 68K's Amiga graphics results are buggered.

Quote:

Do you understand that? Or is it still too complicated for you to understand?

Red herring.

Last edited by Hammer on 05-Apr-2026 at 04:17 AM.

_________________

@Georg

From the Commodore The Final Years book, the story with AmigaOS 2.0 to 2.04 involves backward compatibility fixes.

Quote:

Messed around a bit with Deluxe Music on AROS 68k, today. Use "Typeface" from Aminet to load and resave the fonts DMusic/8 and DMusic/16. For some reason they have NULL tf_CharKern, altough they are proportional. AOS3 seems to correct this problem at load/run time. AROS doesn't so during use bad things happen. Like text extent calculations give negative width for the template to be used by Text/BltTemplate.

That's not an "out-of-the-box" experience i.e. not AmigaOS behavior.

On a classic Amiga with PowerPC, AmigaOS 4.1 FE Update 3 can load and display native Amiga display Deluxe Music 2.0 just fine.


Quote:

Next, patch the DMusic program itself with a hex editor. There are four longs in there "80080007". Change to "88880007".

That's not an "out-of-the-box" experience.


Quote:

80080007 == ASLFR_HookFunc. The program relies on the function to get its small-data-whatever-base-pointer in A4 register. When MorphOS initialliy still used AROS asl.library, they added some code to deal with this, but it isn't compiled in for AROS.

MorphOS kept the changes to itself.


Quote:

I have not checked if all occurencies of 80080007 in the program file are really all ASLFR_HookFunc usages. If one or more is not, you probably get a crash somewhere else as free bonus. After starting the program use Scout to ~disable the InputHandler "MKSoft ToolWindow" by setting it's priority to very low value. This thing doesn't work correctly in AROS, but is otherwise used to allow clicking into toolwindow gadgets without deactivating main window.

That's not an "out-of-the-box" experience i.e. not AmigaOS behavior.

Deluxe Music 2.0 wasn't the only test application that I used i.e. Music X 2.0 / Notation v1.2 bundle.

Going back to OneTimer1's "AROS, that could have made a difference to this mess, is constantly neglected by "the real Amiga Fans" statement; despite AROS being "free", AROS is largely ignored by the majority of Amiga fans and is based on the retro Amiga legacy support.

The Amiga platform should not be treated like the Apple Mac platform.

Valve's SteamOS (Linux based)'s strong market traction is largely based on Windows games compatibility. The same lessons apply to PC clones with PC clone BIOS vs IBM PC BIOS. Compaq's clean room method involves running many 3rd party software to make sure their clean room implementation behaves like the original IBM PC BIOS.

Last edited by Hammer on 05-Apr-2026 at 04:46 AM.
Last edited by Hammer on 05-Apr-2026 at 04:45 AM.
Last edited by Hammer on 05-Apr-2026 at 04:41 AM.
Last edited by Hammer on 05-Apr-2026 at 04:38 AM.
Last edited by Hammer on 05-Apr-2026 at 04:35 AM.

_________________

Irrelevant. What's relevant is if AROS correctly implements the Amiga OSes APIs or not.

If some applications incorrectly use them, it's their and NOT the o.s. problem: they should be fixed, and it should NOT be responsibility of the o.s. to perform internal workarounds just to run those badly coded trash.

@cdimauro

Quote:

correctly implements the Amiga OSes APIs or no

And how is that determined? By the documentation or by code? The documentation is not always consistent, doesn’t always answer corner case questions, doesn’t always document reality. And sometimes documentation is missing entirely.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

Quote:

kolla wrote: @cdimauro Quote: correctly implements the Amiga OSes APIs or no And how is that determined? By the documentation or by code?

In this case it's easy, because we've both.
Quote:

The documentation is not always consistent, doesn’t always answer corner case questions, doesn’t always document reality. And sometimes documentation is missing entirely.

What's the problem here? There's plenty of documentation (original / o.s. 1.2..3.9, AROS, MorphOS, OS4).

And when something is unclear or missing, then that's the "best" scenario: any implementation is valid.

/OT (yes, the topic is completely different from the original one. I kindly ask to open a proper thread If this discussion should continue).

NOTES
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.

Why the Eff is this conversation here at all? STFU with all this BS and leave this thread for the Hyperion / Amiga legal issues.

Does this effing site have ANY KIND OF MODERATION at all?
W
T
F
?

PADDING

_________________
I HAVE ABS OF STEEL
--
CAN YOU SEE ME? CAN YOU HEAR ME? OK FOR WORK