| |
Aemulor |
| |
This is a long thread. Click here to view the threaded list. |
| |
|
David Pitt |
Message #124576, posted by pittdj at 06:59, 26/9/2019, in reply to message #124575 |
Member
Posts: 5
|
Version 2.52 is on the site. Aemulor 2.52 does start up on the Titanium and Raspberry Pi 3B+ both running OS5.27 23-Sep-19.
Many thanks. |
| |
 [ Log in to reply ] |
| |
|
Adrian Lees |
Message #124577, posted by adrianl at 08:05, 26/9/2019, in reply to message #124576 |
Member
Posts: 1637
|
Aemulor 2.52 does start up on the Titanium and Raspberry Pi 3B+ both running OS5.27 23-Sep-19.
Many thanks. Thanks for that. I tested on ARMbook but am mostly using WandBoard and ARMbook at the moment, so it's good to know the others work. |
| |
[ Log in to reply ] |
| |
|
Fred Bambrough |
Message #124580, posted by freder at 00:24, 27/9/2019, in reply to message #124577 |
Member
Posts: 10
|
Brief test shows it working on Beagleboard -xM.
[Edited by freder at 00:25, 27/9/2019] |
| |
[ Log in to reply ] |
| |
|
David Pitt |
Message #124582, posted by pittdj at 12:37, 28/9/2019, in reply to message #124577 |
Member
Posts: 5
|
Just a bit more compatibility info.
On a Mac RPCEmu 0.9.1 running RISC OS 5.27 (27 Sep 2019) Aemulor 2.52 fails to start with the "Overlapping areas" error. The better news is that Aemulor 2.52 does start up on a home built rom that contains the new Kernel OS_DynamicArea 26 call.
With OS5.22, patched as required, Aemulor 2.40 starts up, but Aemulor 2.52 does not, "Aemulor cannot start because it is unable to shrink the application slot on this OS version. Please report &FC01B62C to the author".
HTH. |
| |
[ Log in to reply ] |
| |
|
Adrian Lees |
Message #124584, posted by adrianl at 18:04, 28/9/2019, in reply to message #124582 |
Member
Posts: 1637
|
Just a bit more compatibility info.
On a Mac RPCEmu 0.9.1 running RISC OS 5.27 (27 Sep 2019) Aemulor 2.52 fails to start with the "Overlapping areas" error. The better news is that Aemulor 2.52 does start up on a home built rom that contains the new Kernel OS_DynamicArea 26 call. That's great. You are likely the first person to have tested the new code.
With OS5.22, patched as required, Aemulor 2.40 starts up, but Aemulor 2.52 does not, "Aemulor cannot start because it is unable to shrink the application slot on this OS version. Please report &FC01B62C to the author".
HTH. Thanks, I will look into that. |
| |
[ Log in to reply ] |
| |
|
Adrian Lees |
Message #124593, posted by adrianl at 22:32, 4/10/2019, in reply to message #124582 |
Member
Posts: 1637
|
Just a bit more compatibility info.
On a Mac RPCEmu 0.9.1 running RISC OS 5.27 (27 Sep 2019) Aemulor 2.52 fails to start with the "Overlapping areas" error. The better news is that Aemulor 2.52 does start up on a home built rom that contains the new Kernel OS_DynamicArea 26 call. Can I ask whether you are using 256MiB of RAM, and if not would you please try it? There is a known - but unexplained issue - which somehow causes a hang during booting when using a manually-patched ROM image with 256MiB, and it would be great if the OS_ReadDynamicArea somehow 'resolves' (avoids) that issue because I really can't see how to approach debugging it 
With OS5.22, patched as required, Aemulor 2.40 starts up, but Aemulor 2.52 does not, "Aemulor cannot start because it is unable to shrink the application slot on this OS version. Please report &FC01B62C to the author". That'll be fixed in the next release. It will now start with patched ROMs and the dreaded "Overlapping areas" error that you reported above should never be seen again  |
| |
[ Log in to reply ] |
| |
|
David Pitt |
Message #124594, posted by pittdj at 06:48, 5/10/2019, in reply to message #124593 |
Member
Posts: 5
|
and the dreaded "Overlapping areas" error that you reported above should never be seen again However, I have found another way to achieve "Overlapping areas".
This was from a Titanium running RISC OS 5.27 (01 Oct 2019) and using Aemulor Pro 2.52 (25 Sep 2019).
With Aemulor configured to 28MB wimpslots but the Next slot set to above that then Aemulor fails to start, "Aemulor cannot start because it is unable to shrink the application slot on this OS version. Please report &FC01CAE4 to the author". That seems reasonable, Aemulor should not force the issue. Unfortunately trying to restart Aemulor after Next has been reduced to below 28MB results in "Overlapping areas". Rmkilling Aemulor does not help, the machine has to be restarted.
There is no such problem if an actual too large Wimpslot, either a big app like MuView, 30MB, or a huge Taskwindow, is present, then Aemulor reports that, "Aemulor cannot start because 'MuView' is using more than 28MiB of memory. Please quit the task or reduce its memory usage". Aemulor does restart when the large Wimpslot has been removed. |
| |
[ Log in to reply ] |
| |
|
Adrian Lees |
Message #124595, posted by adrianl at 23:53, 6/10/2019, in reply to message #124594 |
Member
Posts: 1637
|
and the dreaded "Overlapping areas" error that you reported above should never be seen again However, I have found another way to achieve "Overlapping areas".
Well, you won't see that in the next version because I shall have changed the message to "Oh, hi David!"
I don't recall the details now, but I really thought that I had resolved the issue with oversized Next slot prior to releasing Aemulor all those years ago, having spent some time trying to work out what was going on/what needed doing. Perhaps something changed, or I'm just wrong. Either way, I can reproduce it here, thank you.
You're right that I have explicit code to check and report used applications slots that exceed the limit.
[Edited by adrianl at 23:54, 6/10/2019] |
| |
[ Log in to reply ] |
| |
|
Steven Gregory |
Message #124986, posted by thecellartroll at 20:26, 9/11/2020, in reply to message #124595 |
Member
Posts: 135
|
Hi Adrian, I am very late to the Aemulor party! But thank you very much for releasing it into the world!
One question: is StrongARM emulation disabled on Raspberry Pi? I've tried it on Pi Zero and Pi3 B+ and on both the StrongARM option is always greyed out. |
| |
[ Log in to reply ] |
| |
|
Adrian Lees |
Message #125041, posted by adrianl at 17:35, 4/1/2021, in reply to message #124986 |
Member
Posts: 1637
|
Hi Adrian, I am very late to the Aemulor party! But thank you very much for releasing it into the world! Apologies for the tardy reply. I haven't been checking the forums lately.
One question: is StrongARM emulation disabled on Raspberry Pi? I've tried it on Pi Zero and Pi3 B+ and on both the StrongARM option is always greyed out. Yes, it's disabled on everything except the IYONIX pc because it relies upon some special-purpose hardware present in the XScale CPU of that machine. The name 'StrongARM engine' refers to the speed of the emulation, but that speed also applies to the performance on the IYONIX pc.
All newer machines offer higher performance even with the slower 'ARM610 engine' and it's unlikely that you'll encounter any compatibility differences.
Hope that helps. |
| |
[ Log in to reply ] |
| |
|
Adrian Lees |
Message #125320, posted by adrianl at 22:16, 22/8/2022, in reply to message #125041 |
Member
Posts: 1637
|
A quick note to say that there is a new version 2.54 of all builds of Aemulor in the new store https://sendiri.co.uk/store.
The store, out of pragmatism, is simple and targeted for now, so there's little product information at present, but it allows you to order Aemulor and Geminus versions and associated licences.
Presently, these builds are only available in the store; in time the existing bespoke product information and download pages shall be integrated with the store to make things more consistent.
Aemulor remains a free item and will run with all previous and existing functionality unlicensed, but it contains the licence management code that Geminus and other planned programs use, because some future planned additions and features may require a licence.
[Edited by adrianl at 22:16, 22/8/2022] |
| |
[ Log in to reply ] |
| |
|
Micky Micky |
Message #125525, posted by -micky at 21:48, 12/11/2023, in reply to message #125320 |
Member
Posts: 1
|
I wish to use !NWClient but it still did not works.
Here it is:
https://www.kingswood-consulting.co.uk/nwclient/
I test it with RPCEmu 0.9.4 with Risc OS 3.71 with ethernet bridge. It works.
But with my Raspberry Pi 3b+ and Risc OS 5.28 and Aemulor 2.55 (Cortex-A53) it did not.
Did you know why?
Micky |
| |
[ Log in to reply ] |
| |
|
Chris Evans |
Message #125529, posted by CJE at 11:22, 16/11/2023, in reply to message #125525 |
CJE Micros chap
Posts: 228
|
Adrian isn't often on this forum. If you ask on: https://www.riscosopen.org/forum/
you might get a reply from someone else. |
| |
[ Log in to reply ] |
| |
| Pages (2): |< <
2
|
