I was thinking similar to how wine works, Zeta to haiku wrapper can be very helpful and overall really haiku software and games, along with this we get more BeOS games and this could be intergrated into Haiku 64 bit and 32 bit haiku to give more of them legacy game.
As for ZetaOS being close sourced, this help us as a wrapper, compatibility layer is allow in multiple part of EU and US as In many regions, laws allow you to reverse-engineer software for the specific purpose of interoperability making two things work together that weren’t designed to.
Lastly, it should be very light to make a wrapper or compatibility layer as haiku and Zeta share a lot of similarities and coding matching, which should allow for Zeta app to be able run on Haiku more easy than usual
The few commercial applications for Zeta were all released relatively early on and may work by just taking a copy of libzeta.so from a Zeta image, and placing it in a local /libs folder.
Anything else that was adjusted in the API/ABI could be handled without a massively complex intermediate layer.
Everyone knows about the legalities of creating something compatible, remember that BeOS was closed source to begin with and Haiku 32bit is effectively 100% compatible with BeOS applications
A developer worked on Haiku x64 supporting Haiku/BeOS 32-bit applications. Think the project is in limbo at the moment. I got most of the BeOS/Zeta “native” apps working on Haiku x86…
I was thinking about making zeta compatible with 64 bit first meaning if we get this first, we’re able to get BeOS running as they have the same binary because we’re adding legacy apps from both era to run on both then I saw that there’s a legacy package install installer so we could put that to use and zetaOS library on 64 bit to make it run that type of hardware but we could make a wrapper instead of a compatibility layer