Aemulor not working on later non ZPP builds

Aemulor does not working on later (After mid June we think) non ZPP builds of IGEPv5 and Titanium.
Does anyone have a post June non ZPP build on different hardware they can try Aemulor please?
We can then feed that information back to Adrian.

Someone who knows more than me has said:
Having looked back through the CVS changes since June the two most likely to
trip up Aemulor are probably

• Delete lots of old switches (June 30th)
  This in itself doesn’t change any APIs, but some code will have moved
  around, so if Aemulor is doing any pattern matching looking for things
  in the Kernel to hook onto then it /might/ have caused an issue.

• Add support for shareable pages and additional access
  privileges (August 2nd)
  This may be more relevant since I think the new access bits are encoded in
  previously reserved fields

Aemulor Pro 2.34 is working on my Iyonix and my RPi1 in ARMv7 strict mode, both running low vector builds of OS5.23 from source code archives 2016-10-08.

I do see the issue on the Titanium, where Aemulor 2.35 will not start. Offset &8D7C in Aemulor. After cancelling the error I did see some “overlapping area” errors.