Running Coconizer via ADFFS, possible?

[Vanfanel]

Hi Jon

I have found this copy of the free program Coconizer 1.3 for Risc OS:
http://ftp.uni-stuttgart.de/pub/systems ... onizer.zip

Is it possible to run it via ADFFS? What "!Run" file should I try it with?
Since the Cononizer sound modules are already supported, it must be easy I believe.

Thanks!

[JonAbbott]

What "!Run" file should I try it with?

You'll need to modify its !Run to start/stop the JIT before/after any 26bit apps/Modules.

[Vanfanel]

How's that done exactly? GOARM3JIT? Have you tried Cononizer already? Since you tried the player module, maybe you tried the program itself too.

[JonAbbott]

How's that done exactly? GOARM3JIT?

Yes, its documented in !Help, or just look at another script.

Have you tried Coconizer already? Since you tried the player module, maybe you tried the program itself too.

Coconizer is only used by Arcturus, so I've never looked at it or attempted to make it 26/32bit neutral.

[Vanfanel]

@Jon: I tried adding
GOARM3JIT 0

to the top of it's !Run file, and also tried moving it to a position just before RunImage is run. In both bases I get "Internal Error: Abort on data transfer at &0120E484"

I have tried adding "winpslot" and "JITMEMORYA" lines from Arcturus before the GOARM3JIT call, but I get aborts on data transfer, too. Any new ideas are welcome.

[JonAbbott]

I get "Internal Error: Abort on data transfer at &0120E484"

It's trying to access an illegal address then, so possibly has a bug in the code or is self-modifiying in an elevated CPU mode - there will be an SWI OS_EnterOS somewhere early in the code.

I have tried adding "winpslot" and "JITMEMORYA" lines from Arcturus before the GOARM3JIT call

The WimpSlot isn't required, it will just get 8MB if not set by the Obey or code itself. The JITMEMORYA lines from Arcturus definitely won't be required as they're specific to each program and used to change instructions during the JIT encoder stage.

At this point you need to start inspecting the registers and code around where it crashed to determine why it crashed and how to fix the issue. If ADFFS doesn't trap the abort and report it, then *SHOWREGS will contain the registers, PC and CPU mode the abort occurred in.