Aemulor and recent Tungsten ROMs

I use Aemulor on the Iyonix occasionally (converting Archive mag Publisher+ files to HTML). Using Aemulor Pro 2.32, this has never given problems. However, I have just found that using recent softloaded builds (I have 3 builds in Nov to try), Aemulor installs on the iconbar, but attempting to run a 26-bit app results in an immediate crash. The address is in the Aemulor module. Reverting to the stable 5.18 build (no softload) and Publisher, Eureka etc run normally under Aemulor. Has anyone else noticed this, or does no-one use Aemulor now?

I will give it a try later on with the BB and the new ARMv7 version of Aemulor.

Chris

Just tried it with latest Iyonix softload and get the same issue with aborts etc. 5.18 works ok.

Aemulor seems to run OK on the Beagle though with latest ROM image.

Thanks Doug. Guess I shall have to reboot when I need to use any 26-bit apps, Iyonix usually runs 24/7. In the longer term, shall have to move the Archive mag stuff over to the BB.

Well rebooting would be OK until official 5.20 firmware release is available.

Or hopefully Adrian will be over his illness before then and feels like looking at the Aemulor issue though the later may not follow if it was a contributing factor.

Hi, I’ll look into this. Hopefully this week, now that the Pi build is out in the wild. From what I know so far, however, an alternative to downgrading your OS may be to switch the application(s) that are failing to ‘ARM610’ mode. The StrongARM engine, which is unavailable on the Pi currently, is fundamentally different in its operation, and I think the clash affects it alone. These apps /do/ run using Aemulor on the RaspberryPi build of the same OS version….so it’s worth trying. I’ll let you know when I know more, and I expect there’ll be an update to the IYONIX pc versions very soon, unless it turns out to be an OS fault.

I use Aemulor Pro version 2.30 (05-May-2004) on my Iyonix 512Mbyte which runs OS 5.16 (18-Jan-2010) and the only issue I have is that if I double-click a JPEG file (which starts PhotoDesk 3.10 (14-Oct-2010)) [with or without Messenger Pro running], then the machine freezes, nearly every time. Just after you click on the message about whether to keep the clipboard (if it appears) and before the PhotoDesk icon bar icon appears.

I get an immediate abort on data transfer if I try to load Aemulor Pro Pi 2.34 on my Raspberry Pi running RC8 but the demo Pi version 2.34 works fine (Adrian is looking into this).

I get an immediate abort on data transfer if I try to load Aemulor Pro Pi 2.34 on my Raspberry Pi running RC8 but the demo Pi version 2.34 works fine (Adrian is looking into this).

I have downloaded Aemulor Pro Pi again and although the archive is exactly the same length, the contents are different and it all works faultlessly. So whatever the problem was, it has been sorted.

With Aemulor Pro version 2.32 (07-Oct-2005) on my Iyonix the issue with JPEG files and PhotoDesk causing the machine to freeze nearly every time is still there.