[iyonix-support] Re: Spam infiltration

In message <Pine.LNX.4.64.0607291704280.798@xxxxxxxxxxxxxx>
          Iyonix PC Owner <iyonix@xxxxxxxxxxxxxx> wrote:

>On Sat, 29 Jul 2006, Tim Powys-Lybbe wrote:
>
>> I've done that and it starts up OK now, thanks.
>>
>> But when I drag an offending e-mail to it, I get this message in a
>> MDM box:
>>
>>  Application is not 32-bit compatible
>
>OK, it has been compiled with the 32bit flags on, but on my old
>RISC PC, which I no longer own. I have used Castle's first version
>of the Acorn C/C++ compiler suite.

The Castle Tools do default to 32bit on the RiscPC, just tried with C
vsn 5.64. I am sure all versions did that, though I could be wrong.

There a ways to tell what standard an absolute has been compiled or
assembled to. The flag at offset &30 in the AIF header can be &1A or
&20, dec. 26 or 30. Note that not all 26bit AIFs have that flag but it
must be present in a 32bit absolute. OS5 does not read that flag but
Aemulor certainly does. 

For a C absolute a look at the SharedCLibrary SWIs called shows all,
after 'xpand'ing if necessary.

For 32bit C :-

  SWI     XSharedCLibrary_LibInitAPCS_32
  SWI     XSharedCLibrary_LibInitModuleAPCS_32

For 26bit C :-

  SWI     XSharedCLibrary_LibInitAPCS_R
  SWI     XSharedCLibrary_LibInitModule

StubsG has :-

  SWI     XSharedCLibrary_LibInitAPCS_32
  SWI     XSharedCLibrary_LibInitAPCS_R
  SWI     XSharedCLibrary_LibInitModuleAPCS_32
  SWI     XSharedCLibrary_LibInitModule

If Castle's 32bit Stubs is used then the correct rmensures are given on
the Castle site, http://www.iyonix.com/32bit/32bitIntro.shtml

I hope that is of use.
-- 
David Pitt.

Computing with RISC OS.
---
To alter your preferences or leave the group, 
visit http://www.freelists.org/list/iyonix-support
Other info via http://www.freelists.org/webpage/iyonix-support

Other related posts: