log in | register | forums
Show:
Go:
Forums
Username:

Password:

User accounts
Register new account
Forgot password
Forum stats
List of members
Search the forums

Advanced search
Recent discussions
- RISC OS Developments moves into hardware (News:5)
- Support movember (Gen:4)
- November News round-up (News:)
- 4 interesting RISC OS projects on Git (News:1)
- Drag'n'Drop Autumn 2019 edition reviewed (News:)
- R-Comp updates NetFetch and MPro at London Show (News:)
- RISC OS Developments makes Impression Style free (News:)
- Archive 24:5 Reviewed (News:)
- 5 websites I can now access properly with RISC OS (News:2)
- First releases of OWB and Iris RISC OS browsers (News:5)
Latest postings RSS Feeds
RSS 2.0 | 1.0 | 0.9
Atom 0.3
Misc RDF | CDF
Site Search
 
Article archives
The Icon Bar: General: Aemulor
 
  Aemulor
  This is a long thread. Click here to view the threaded list.
 
David Pitt Message #124576, posted by pittdj at 05:59, 26/9/2019, in reply to message #124575
Member
Posts: 4
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 07:05, 26/9/2019, in reply to message #124576
Member
Posts: 1598
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 23:24, 26/9/2019, in reply to message #124577
Member
Posts: 7
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 11:37, 28/9/2019, in reply to message #124577
Member
Posts: 4
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 17:04, 28/9/2019, in reply to message #124582
Member
Posts: 1598
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 21:32, 4/10/2019, in reply to message #124582
Member
Posts: 1598
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 wink

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 smile
  ^[ Log in to reply ]
 
David Pitt Message #124594, posted by pittdj at 05:48, 5/10/2019, in reply to message #124593
Member
Posts: 4
and the dreaded "Overlapping areas" error that you reported above should never be seen again smile
However, I have found another way to achieve "Overlapping areas". smile

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 22:53, 6/10/2019, in reply to message #124594
Member
Posts: 1598
and the dreaded "Overlapping areas" error that you reported above should never be seen again smile
However, I have found another way to achieve "Overlapping areas". smile
Well, you won't see that in the next version because I shall have changed the message to "Oh, hi David!" wink

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 ]
 
Pages (2): |< < 2

The Icon Bar: General: Aemulor