on my a4k 060 id say reasonable. especially rtg. the problem is with the available desktops, each one has its drawbacks, workook is too proimitive, wanderer doesnt save some prefs in right endianness and has slow dir sisting routine, scalos eats up too much chipram, magellan is too unintuitive and more a file manager imho. also the new versions are slower than original.
Yeah, the desktops make a big difference and it's hard to separate whether it is Workbook (for example) or drawing operations being slow.
you can turn off jit in uae, then it will be actually even slower than the real thing. however if you want to get aros running on your real machine to see for yourself, i can help you.
I've tried a few variations of that.
Running it as approximate A1200 speed, no jit, etc. give me a result, but it's hard to judge if it's correct.
For example, I'd assume that memory speed would be orders of magnitude faster than any real system, even with RTG.
When I run WinUAE as fast as it can go, screen and window redraws are just slow. With approximate 020 it's massively slower so to me that implies that it's CPU bound and not so much memory speed bound.
Given the emulated system/RTG memory bandwidth available, even if the emulator is wasting a lot of cycles and moving byte by byte, I'd expect better. It's not like it's using a chipset screenmode.
There have to be basic design problems that multi-GHz x86 is covering up.
AmigaVision is one way I've been testing because it comes with a few more things, the nightlies are very bare bones.
If you open the System drive In ArosVision, then drag it's position to a new location a few times, it stalls for a second or more every few drags. What can take that long, even with JIT?
I'm not just complaining, I want to know what's happening so that it can be corrected.
