Giant Mutants Are Live - and They Don't Move... Because They Don't Need To
https://drive.proton.me/urls/VVFRQQD1Y8#7o3xEZn32M61

Today was giant?mutant testing day.
And honestly? I'm starting to think I created a whole new category of unfair.

These things don't walk.
They don't chase you.
They don't flank, hide, or do anything remotely tactical.

They just stand there.
Like skyscrapers with anger issues.
And then they unload.

The moment they spot you, it's like someone flipped the "infinite ammo" switch.
Rockets, bullets, beams - whatever they're built with, they fire it nonstop like they're trying to erase you from the timeline.

It's almost insulting how confident they are.
They look at you like:
"Why would I move? You're the one who should be running."

And the worst part?
I coded them.
I know exactly how they work.
And yet every time I test them, I feel like I'm trapped in a turret defense game where the turrets hate me personally.

Static enemies, sure.
But when they start firing, you realize mobility was never the problem.
Survival is.

Challenge accepted... again.

@redact a post was made by your account this evening. It was reported and I deleted it and sent a warning message. I'm a forum moderator, but not an admin.

I saw your account was created a while ago but never posted with, but thought this might be a tactic of spammers; to create an account, leave it dormant and then post.

Thanks for posting a response and explanation and a great first move to change your password.

Looks like your server might have been hacked, passwords compromised.

Someone logged into my account, even with the forum having a unique password only used on this site and not shared, and posted something dodgey, probably sex related links. I received a warning from "Amiga.org". They also changed my profile details to female, 38 and living in Algeria. I've changed my password, let's see if it happens again.

The usage stats indicate that this site might be compromised:
Users Online: 4005 Guests, 2 Users, 20 Spiders
Most Online Today: 18031

Bassano del Grappa, Italy – March 19, 2026

Today, March 19th, is Father's Day in Italy (Festa del Papà) — and what better occasion to celebrate than by honoring the father of the Amiga himself, Jay Miner? The visionary engineer and chip designer who gave life to the Amiga back in 1985 deserves to be remembered not just with words, but with something tangible for the community he helped create.

For this reason, ACube Systems has chosen today to release version 1.2 of the SiI3132 SATA2 driver for AmigaOS 4.1 — a small tribute to Jay Miner's enduring legacy.

What's new in version 1.2:

Performance & Code Efficiency — General code improvements for better overall performance and optimization.
SCSI Command Handling — Error response management for SCSI commands has been significantly improved, resulting in greater robustness during operation.
Burning Process — The handling of disc burning phases has been refined for improved reliability when working with CD/DVD drives.
As with the very first release back in October 2025 — unveiled as a special gift during the Amiga40 Germany event in Mönchengladbach to celebrate the 40th anniversary of the Amiga — this update is completely free of charge. It has always been our intention to give back to this incredible community, and that spirit remains unchanged.

The driver continues to support HDDs, SSDs, and optical drives via SATA2 on PCIe cards based on the Silicon Image SiI3132 controller, delivering high performance and stability on AmigaOS 4.1.

You can download the driver from the “Latest files” section on our homepage or directly clicking on this link:

https://acube-systems.biz/download.php?file=sii3132sata_dev_v1.2.lha

Happy Father's Day — and thank you, Jay. 🙏

There is a link to  Commit e0cd52c in the issue thread.
It says v 7.0.0 RC3, preview v.6.1.0

I dont know what to make of that version numbering. The commit is from 2021, but the latest amiberry lite release is 5.9.1. Must be refering to the regular v.7.0.0 then, no idea if its implemented in the lite variant.

I've looked at this commit, it comes from before the split into amiberry-lite and amiberry. My existing code is in sync with the latest amiberry lite jit. It looks like this may have already been applied as it's so long ago. If not it's quite hard to see where to apply it as, the lines don't match up with the commits diff and there are a lot of repeated sequences in the code, even the same comments.

[update]
I found the exact  function in the current code and the patch *is* applied. Therefore if the bug persists it must be a separate issue to this.