EmuV0 v1.0 is here!

EmuV0 is an emulator that allows running many of the 32-bit AROS applications under 64-bit AROS in an integrated and transparent way. As we are closing on migration to 64-bit system, EmuV0 fills the remaining software gap until native ports arrive. Focus in version 1.0 was on bringing 32-bit Hollywood applications and Hollywood 11 compiler to 64-bit, but many non-Hollywood application are also usable. Enjoy the software you like using on a brand new, 64-bit AROS system!

EmuV0 will be integrated into upcoming release of AROS One and AROS Portable distributions.

Last edited by deadwood on 23-Jan-2026 at 10:04 AM.

_________________
https://www.axrt.org

@deadwood

its like a coherence mode?

_________________

@Mobileconnect

What do you mean by coherence mode?

With EmuV0 you open 32-bit application as if they were 64-bit application, they get real 64-bit windows, screens, tasks etc. You can't really tell it's a 32-bit application running.

It's like running m68k applications under AmigaOS4 or MorphOS, but simply x86(32-bit)->x86(64-bit) instead of m68k(32-bit)->PPC(32-bit).

Last edited by deadwood on 23-Jan-2026 at 01:51 PM.

_________________
https://www.axrt.org

@deadwood

Well done!

Short video showing how the Emuvo emulator works, featuring some Hollywood 32-bit programmes running on AROS One 64-bit!

https://youtu.be/vY1URwXRWb0

_________________
AROS One Home Site
AfA One Amiga OS 3.9

Good to see the progress of 64-bit AROS. Having a very well integrated 32-bit emulator like this makes a lot of sense. Once EmuV0 has matured a little, changing to 64-bit AROS will obviously be a much more attractive option .

_________________

@Tpod

the real question is could this also be expanded to allow running of 68k amiga software as first class citizens in AROS 64bit?

_________________

@Mobileconnect

Yep good question; if the answer is yes, that's the plan, once that's working well I think setting up a dedicated AROS machine would be on the cards for me for the first time.

_________________

Quote:

Mobileconnect wrote: ... could this also be expanded to allow running of 68k amiga software as first class citizens in AROS 64bit?

You can just use this:
https://amigaworld.net/modules/newbb/viewtopic.php?topic_id=45754&forum=47#882576

Running 68k Amiga software under AROS_x86 / AROS_64 will always be difficult because of different endian modes and pointer length.

Last edited by OneTimer1 on 24-Jan-2026 at 04:13 PM.

@deadwood

I can think of one possible modes to do that:

Some AROS-x86 emulation tool that could translate the 32Bit addresses into 64Bit addresses, so it can be done by reserving a 2GB address space for AROS-x86 or by running an own AROS-x86 in AROS-64.

Could you enlighten me how it was done?

@Mobileconnect

Quote:

the real question is could this also be expanded to allow running of 68k amiga software as first class citizens in AROS 64bit?

I have some ideas how the technology behind EmuV0 could be used to enable running 68k amiga software in such mode. This will have to wait though. Right now the focus in on finishing the last stage of migration: matching 32-bit in terms of hardware supported and possibly improving it at the same go.

_________________
https://www.axrt.org

@OneTimer1

There is a short description here:

https://github.com/deadwood2/AROS/blob/master/workbench/tools/AoA/SPECIFICATION

Basically the emulation is built on two pillars:

1) 32-bit applications are loaded into 32-bit subspace of 64-bit address space and receive memory allocations only from that subspace
2) 64-bit processor is switched into 32-bit mode when executing 32-bit code and switched back to 64-bit mode and entering 64-bit code

Last edited by deadwood on 24-Jan-2026 at 06:08 PM.

_________________
https://www.axrt.org

@deadwood

Quote:

Basically the emulation is built on two pillars: 1) 32-bit applications are loaded into 32-bit subspace of 64-bit address space and receive memory allocations only from that subspace 2) 64-bit processor is switched into 32-bit mode when executing 32-bit code and switched back to 64-bit mode and entering 64-bit code Emulator creates following proxy libraries each time it is started: exec, dos, graphics, intuition, utility, cybergraphics The role of the proxy libraries is to take calls from 32-bit code and forward them to 64-bit kernel. This allows for integration of 32-bit programs within 64-bit enviroment. For example 32-bit program opening an Intuition window will actually open a 64-bit Intuition window and emulator will provide translation of arguments and data structures back and forth.

Thank you, that made sense to me and just writing those proxy functions is a lot of work, a lot of boring work but it won't work without. Thank you for making it and keep on the good work.

Last edited by OneTimer1 on 24-Jan-2026 at 08:39 PM.
Last edited by OneTimer1 on 24-Jan-2026 at 08:37 PM.

With proxy functions there's a lot of potential. You could:

- validate parameters before calling the real function, and leave with a safe panic before calling the real function with bad parameters
- put allocations/created objects on a cleanup stack for safe cleanup in the event of a panic
- provide proxy objects, that work more like windows handles

_________________