Not yet. Once I clean up (mainly related to the other uae_core impls already in tree) and test some things (mainly other architectures) I plan to do so.

I implemented the ARAnyM use_core changes on top of kanjitalk755 fork. It is in branch kanjitalk755_aranym_wip

Nice job!

For reference, what kind of benchmark scores do you get with MacBench 4.0? (focusing on graphics scores)

I applied latest ARAnyM changes to uae_core as of September 23 2025 to my fork of BasiliskII, core_cleanup branch.

Mainly floating point rounding mode correctness, shift masking, and accurate PC.

It seems like Hatari UAE core is more updated then ARAnyM's core. I'll see if I can integrate the changes...

Does QEMU support userspace emulation of A/UX programs yet?

One main reason is that I'm looking into porting a newer version of GCC to compile executable for A/UX and it would be much faster to test using the same filesystem as the host instead of copying the executable into the disk image every ...

It's the first I saw. I'll probably try it out myself later

There is also the scale up fork here, which lets you resize the window on runtime: viewtopic.php?f=6&t=10713

Updated with latest ARAnyM changes.

I still need to figure out why "idlewait" hangs randomly…

kanjitalk755 wrote:

uyjulian wrote:Okay, it seems like the random hang on startup is caused by the SDL2 code. See https://github.com/cebix/macemu/issues/203

The issue will be fixed with the following commit:

https://github.com/kanjitalk755/macemu/ ... c82f828bac

Cool. I'll check it out

As for a 64-bit JIT, could it be borrowed from FS-UAE?
I'm actually working on porting the JIT from ARAnyM. See my thread: https://www.emaculation.com/forum/viewtopic.php?f=6&t=9674

I plan to submit changes to both ARAnyM and Basilisk II after I am finished with my changes and the issues are ...

Okay, it seems like the random hang on startup is caused by the SDL2 code. See https://github.com/cebix/macemu/issues/203

I proposed several solutions in the issue. I will go for the solution that use memory banks addressing.

But I dont know the performance hit, compared to direct addressing. I ...

Okay, it seems like the random hang on startup is caused by the SDL2 code. See https://github.com/cebix/macemu/issues/203

Shoebill loads the kernel from the root filesystem. The A/UX Startup utility isn't used. https://github.com/pruten/shoebill/blob/2b4768daee2227cf19e9556c73afd318f0e8bf8c/core/core_api.c#L637

A/UX userspace emulation would be interesting, just to run the assembler for cross-compiling GCC (since A/UX ...

Unless you are using a CRT, mode switching should take a toll on the monitor. How can that be? It does nothing else than moving the image on the screen. If this would take a toll on the monitor, watching a movie or playing a game would have a much worse impact on the monitor.

Sorry, I meant to ...

Unless you are using a CRT, mode switching should not take a toll on the monitor.

If you get stuck in full-screen, you can press Ctrl-Esc to quit the emulator.

You can set higher resolution for BasiliskII to make use of your monitor's increased resolution.

I synchronized changes with ARAnyM again.

There's still the following issues:
1. Program randomly hanging on startup
2. Program not working properly with idlewait option (no events except mouse movement events are delivered)

It may be possible that 10.15 does not force vsync (while 10.14 does)

extfs_macosx.cpp and extfs_unix.cpp use different methods of storing resource forks.

extfs_macosx.cpp uses the named fork to store the resource fork data: /path/file/..namedfork/rsrc
See https://github.com/cebix/macemu/blob/master/BasiliskII/src/MacOSX/extfs_macosx.cpp#L226

extfs_unix.cpp uses ...

If you want to change the configuration file path, you might be able to inject a dylib and overwrite the pointer to the configuration file path.

I know that MiniVMac does write to .dsk images of RAW type.
I used that procedure some time ago to write physical floppies from Terminal with dd in OSX.
Maybe RAW is the key here too - dd does not like any headers for sure.

Maybe this is still of use for you:
https://www.emaculation.com/forum ...

You need to install SCSI drivers (for example from patched Apple SD HC Setup or LaCie Silverlining) in order for the disk to be usable.

You can open the disk via fusehfs to transfer applications if installing the drivers is too complicated for you.

Haemogoblin wrote:So I think what we are saying is, the RPi can’t emulate PPC?

If you want QEMU on Raspberry Pi, go compile it yourself. It may also be in the repositories.

If you want to emulate a PPC, use QEMU or SheepShaver.