Quote:
One more solution left that I haven’t mentioned: a MorphOS emulator.

> a MorphOS emulator. :-)

What do you mean? A software that acts like MorphOS but isn't? Or a software that acts like MorphOS-compatible hardware? If the latter: QEMU.

I mean software that allows you to install MorphOS on a standard PC machine. Just like WinUAE does for AmigaOS.

Quote:

You mean, really unusably slowly?

PPC is the worst case scenario to emulate: multiple instruction sets, FPU and Altivec, MMU, special purpose registers, condition registers, more than one instruction set, decrementer, etc etc.

And x64 is the worst case scenario to emulate it: all that would need to be done on software, with no hardware acceleration on a single thread on a CPU family that now routinely requires 16 or more cores to meet its true speed, and which is architecturally and logically very different.

I'd say it might be decades before something like QEMU was fast enough, but it's already been decades, and the core increase seems to be pushing us further rather than closer, so I'd actually be quite comfortable predicting it never could.

@KennyR

While all that may be true, it is also true that the OG Rosetta managed o.k. speed running PPC code even on something as weak as a CoreDuo.

PPC Emu on ARM64 hardware is around the corner ;)

Quote:

Using half the CPU's actual computing power, not one sixteenth...

Quote:

Not sure what tree you're trying to bark at here....

We already use only a part of the computing power since many supported PPC are dual or even quad core.
The initial CoreDuo/CoreSolo were not that far off from G4/G5 clock by clock and core by core.
Current x86 cores are several times faster than those from 2006.

So if we could somehow get Rosetta's performance running MorphOS on a current Intel or AMD CPU we would have created the fastest MorphOS computer by quite a margin.

Not that thats gonna happen.

Quote:

/me looks over at my dual EPYC 7502 ... 1/128th >.<

Quote:

It's an arithmetic growth while overall CPU speed is growing geometrically.

Quote:

QEMU is a full emulator, it emulates the whole CPU warts and all. Rosetta was not some magic hyper-efficient form of it. It only translated user-mode instructions. Where it could, it pulled x64 code from the OS to replace PowerPC code rather than translate it. MacOS talked to Rosetta for all the necessary address mapping, and was an abstracted layer that never had to deal with the MMU, I/O, timers, and so on like MorphOS does.

And before anyone says it could be added, I'm not sure MorphOS is capable of doing that by dint of its inherent design of being a shared address OS. Like multi-core, it's not even clear where to begin, never mind how it might work.

Quote:

Btw, there's also qemu usermode emulation which only does cpu emulation plus syscall translation.

Allows for example to run 32 bit big endian PowerPC Linux programs on 64 bit little endian x64 Linux.

Like for example AROS PPC Hosted/Linux (older version, because unmaintained, so tried old build from 2013) which "boots" into AROS desktop in 2 seconds on AMD Ryzen 7 7800X3D. With maybe 10 year old PC (i5 4590) it was 4 seconds.





[ Edited by Georg 26.01.2026 - 12:42 ]

Sure, that is kinda what Amithlon did 25 years ago.

Wich would either need support from the OS or the ability to patch it.

FLOW STUDIO (V1.11):

There are some things which hopefully will be changed at MOS3.20!

1. When trying to print in postscript and printrequester (prefs) opens, ANY next button-press starts printing!! (no matter on what you click).

2. Changeing font for output doesn't influence anything for printout or save pdf. What is the purpose of that pref? Only changeing editors font influences print-output (but not to pdf - this never changed!).

3. Formatting: Tabs are not allways set right in pdf output.

4. Printing over TP produces a gray background on paper (no way find to set it to clear white).

Same issues are fouind in former SCRIBBLE.

Quote:

I doubt that any of this will be addressed for the next MorphOS release and this is the wrong thread to talk about it anyway unless you expect all the users around here to give you some "100%", "I agree", "I totally disagree" reply.
I guess the original idea of this thread was not to present dedicated bugfix wishes for individual applications here but more of a general outlook/expectations for everyone in the first place.
Last but not least the main audience for this aren't the MorphOS Team developers anyway. So if you expect us to read every thread on morph.zone to identify specific bug reports, you definitely didn't understand the function of this forum.
It is mostly meant as a MorphOS user community exchange. If you want to reach out to actual Team developers, you can do so via the known channels, either by bugreport via the bugreport form or more directly via IRC or even Discord these days.

Printing in Flowstudio is really something that has not seen much love in the past for obvious reasons I don't want to get into now.
At least the backgroud printing colour over TP sounds like something that could be easily addressed.

OK, OK, didn't think about that - will use bugreport next...

I would like and strongly recommend to move MorphOS to ARM technology. If it would not be possible x64 (Sh*t happens).
About gaming..Pinball games. We've got only 1. YES! Just 1. Even Atari is better. ProPinball or at least Pinball Dreams 2. That would be great.
I dont wanna tell anything wrong about Wayfarer but Cloudflare is a pain in the neck.
The most important is We MorphOS users like me, lets stay together

Quote:
You can assume that MorphOS Team members have some educated opinions about the future architecture path.

From what I can tell is that ARM technology is not really homogenous, you can't build a "one fits all" system but need to decide what type of ARM "tree" you want to follow, otherwise it's impossible to maintain for a team that only has limited resources.

Quote:
Cloudflare clearly is but I don't see how Wayfarer can do anything about it.
The company is very secretive about its technology/what they are doing and not open at all for supporting solutions like ours.
I wished it would be different but we have to get along with it.

Quote:
Well, yea, the only way forward is to build and grow an even stronger MorphOS community. There is no way forward without actual users of the system.

Quote:

Copy that. We spoke many times of problems with non-standart SPE FPU unit and ABI in e500 core ( P1022 ), and ARM has even more FPU types and the same soft-float / heard-float issues ABI

1. Basic Office suite (CellBasics + Stylos integration as much as possible)
2. Multi-core support in MorphOS 3.20

[ Edited by tomasz 19.02.2026 - 15:48 ]