Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.

AROS 64-bit 2026.09 Development

Last updated on 2 days ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 24 days ago
@ retrofaza
Great job that was a really annoying bug that was preventing you from working. Thanks for fixing it; if there are any other issues, I'll let you know!

@deadwood
The ACC audio format (designed to be the successor to the MP3 format) also requires a higher stack, but once the stack is increased, it generates a different GURU error; I've attached the file.
ACC works fine on the 32-bit version of MPlayer.
You do not have access to view attachments
D
deadwoodAROS Dev
Posted 24 days ago
@ntromans

3D - this won't work, EmuV0 is not forwarding 3D calls and I won't be adding this to release backlog

MOAI - as long as there is a version you are using (MUI based), I won't be spending time on that

"Editor" error - please provide Hollywood program that generates this error (also please provide Hollywood program that generates popup menu error - I wrote about it in earlier post, you might have missed it)
N
ntromansVeteran Member
Posted 22 days ago

deadwood wrote:

@deadwood - @ntromans

3D - this won't work, EmuV0 is not forwarding 3D calls and I won't be adding this to release backlog

MOAI - as long as there is a version you are using (MUI based), I won't be spending time on that

"Editor" error - please provide Hollywood program that generates this error (also please provide Hollywood program that generates popup menu error - I wrote about it in earlier post, you might have missed it)


Please see the attached zip for both source code (very short) and an applets built from them.

Popup menu crash - just run the applet, the crash happens every time.

Editor crash - this is a but less consistent in its occurence. It seems to happen reasonably regularly if:

  • Open Editor on its own screen and then open its file requester. Don't select a file, just leave the file requester open and selected.
  • Go back to Wanderer and run the applet from a shell - usually gives the crash on cancelling the Hollywood error requester. If not, pop back to the Editor screen, re-select the file requester and then back on Wanderer to run the applet again.


Many thanks for considering these,
Nigel.
You do not have access to view attachments
D
deadwoodAROS Dev
Posted 22 days ago
Ok, got it, thanks.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 18 days ago
@deadwood
Hi, today I integrated this new build into AROS One 64-bit v11. I usually overwrite AROS One with the entire contents of new builds, but with this one, AROS One has errors with GRUB and won't boot.
What has changed in the boot folder, and what do I need to delete from the old AROS One boot folder?
D
deadwoodAROS Dev
Posted 18 days ago
I assume this is the first time you integrate an ISO since 20250418 release - because previously we just had updates and updated didn't modify boot/grub directory.

You need to completely delete your existing boot/grub directory and use a new one from ISO (20250418 uses older grub that this ISO - this is mostly likely why you are getting issues). Also note that commands in grub.cfg file have change - compare this one to 20250418 and you will see differences.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 17 days ago
AROS One has all updates installed up to the latest one 20250418-1-U3.
If I replace the Boot folder with your latest build, aros-202609-D01-pc-x86_64, I get this error in GRUB:
Booting ' AROS Default'
452: out of range pointer: 0xbff6b330
Aborter. Pres any key to quit._

If you extract your ISO on Windows using 7-Zip or other ISO-handling programs, they all report a duplicate content error for the two files in the EFI folder; basically, once you copy them, the program asks if it can overwrite those same two files.

In the local Grub folder, there are files ending with this character. Are they correct?
ben@piglatin.mo~
D
deadwoodAROS Dev
Posted 17 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - AROS One has all updates installed up to the latest one 20250418-1-U3.
If I replace the Boot folder with your latest build, aros-202609-D01-pc-x86_64, I get this error in GRUB:
Booting ' AROS Default'
452: out of range pointer: 0xbff6b330
Aborter. Pres any key to quit._


Does this happen when you replace boot directory in you VMWARE image or if you replace boot directory, the build ISO and then boot that ISO in VMARE?

AMIGASYSTEM wrote:


If you extract your ISO on Windows using 7-Zip or other ISO-handling programs, they all report a duplicate content error for the two files in the EFI folder; basically, once you copy them, the program asks if it can overwrite those same two files.


NTFS is case-insensitive and ISO contains both "boot" and "BOOT" subdirectories. That's effect of how the ISO is build. Nothing can be helped with that on Windows. Since 20250418-1 a new way to build ISOs have been introduced.

AMIGASYSTEM wrote:


In the local Grub folder, there are files ending with this character. Are they correct?
ben@piglatin.mo~


This is some side effect of building ISO. They are harmless apart from fact they are taking space. If I have time, I will see if I can clean this up.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 17 days ago
In addition to the Joliet (Windows) and RockRidge (Linux/Amiga) extensions, the new ISO now also includes an HFS (macOS) extension.

Windows uses and displays the CD as Joliet, but I also tried it with UltraISO, which supports both Joliet and RockRidge.
Only with Amiga OS on WinUAE, using real CD mounting via AsimCDFS, can I handle EFI in lowercase; however, I have to enter the folder, otherwise it copies in uppercase and displays a duplicate file error.

That said, I don’t think the Grub error is caused by copying via NTFS.
The Grub error appears both when I copy the data from the new build directly to a pre-installed AROS, and when I create a new ISO; therefore, even an older system updated from an ISO generates a Grub error.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 17 days ago
After running some tests and using a process of elimination, I’ve identified the cause of the GRUB error.

The problem occurs if the AROS 64-bit v11 system includes:
AROS-20250418-1 + U1 + U2 + U1-P1 + U2 + U3)

The file causing the GRUB error is relocator.mod
bootgrub/i386-pc/relocator.mod

By replacing relocator.mod with the one from AROS-20250418,

the new Build 2026.9 can be integrated without any issues,
D
deadwoodAROS Dev
Posted 17 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM
That said, I don’t think the Grub error is caused by copying via NTFS.
The Grub error appears both when I copy the data from the new build directly to a pre-installed AROS


Correct - grub error you got and duplicated directories are two separate topics.

FYI: I don't recommend updating grub on existing installation (none of Ux updated did that). I think it's highly likely that such update will cause existing installation to stop working.
D
deadwoodAROS Dev
Posted 17 days ago

AMIGASYSTEM wrote:



By replacing relocator.mod with the one from AROS-20250418,

the new Build 2026.9 can be integrated without any issues,


That's very weird. I would not have though about that. However glad you solved that issue Smile
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 17 days ago
Okay, I'll keep testing the new build integrated into AROS One. I hope that in the final version of the September build, relocator.mod will be fixed or replaced.
As for JanoEditor, I'll continue to use the correct version from retrofaza.
D
deadwoodAROS Dev
Posted 17 days ago
Just to clarity: Unless someone can reproduct this '452: out of range pointer: 0xbff6b330' error with a clean D01 ISO/installation I don't intend to change anything. The update package will not contain boot/grub directory anyhow not to affect existing installations and for process of assembling your distribution ISO the workaround is known now.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 17 days ago
Okay, just to be sure—would copying the entire D01 image to AROS One without “relocator.mod” cause any problems? If so, I'll redo the D01 update on AROS One without boot/grub.

Another question: Do you know if AROS 64-bit can be installed and run on Hyper-V?
D
deadwoodAROS Dev
Posted 16 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - Okay, just to be sure—would copying the entire D01 image to AROS One without “relocator.mod” cause any problems? If so, I'll redo the D01 update on AROS One without boot/grub.


Do you mean copying D01 into existing SFS AROS disk with AROS One installed?
It is really important to know whether you are integrating D01 into an existing AROS installation so that you can use that (as if making an update to installation) or whethere you have a directory in Windows where you have AROS One 1.3 files and you are copying D01 into that directory to build a new ISO image.


On your second questions: I don't really know what Hyper-V is.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 16 days ago
I mean, if I need to update AROS One to the upcoming v1.4, how should I proceed:
Integrate AROS 64-bit 2026.09 completely without “relocator.mod,” or integrate AROS 64-bit 2026.09 without the boot/grub folder.

Microsoft Hyper-V is native hypervisor-based virtualization software that allows you to create and manage virtual machines on a single physical computer or server.

System RequirementsOperating System:

Windows 10 and Windows 11 (Pro, Enterprise, and Education editions only; not available on Home) and Windows Server.Processor:
64-bit CPU with hardware virtualization support (Intel VT-x or AMD-V) to be enabled in the BIOS/UEFI.
RAM: Minimum 4 GB; more is recommended.
D
deadwoodAROS Dev
Posted 16 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - I mean, if I need to update AROS One to the upcoming v1.4, how should I proceed:
Integrate AROS 64-bit 2026.09 completely without “relocator.mod,” or integrate AROS 64-bit 2026.09 without the boot/grub folder.


But it matters where you are doing this update.

If you have AROS One files extracted to a directory on Windows and you extract D01 files and copy them over, then you must delete the boot/grub directory you have in your AROS One files directory and copy D01 including boot/grub. This way ISO built from these files will have new grub.

If you have AROS One installed to SFS disk under VMWARE and you want to copy D01 on top of it, then you cannot copy boot/grub directory. You need to keep your old grub.
Edited by deadwood on 03-08-2026 09:13, 16 days ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 16 days ago
Okay, now I get itso I need to ignore boot/grub in any case when building AROS One v1.4! Will this also apply in the future?

Speaking of Hyper-V, I found this video by Kalamatee!

https://youtu.be/...
D
deadwoodAROS Dev
Posted 16 days ago
Yes, the rules I described above will be valid for next versions as well.
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.
Users who participated in discussion: deadwood, AMIGASYSTEM, ntromans, retrofaza, Amiwell79, Jeff1138, ncafferkey, sonountaleban