ZapObey problem
Paul Nolan (1470) 18 posts |
Wasn’t sure where to ask about this, but figured here would be best as it only seems to happen on RO5 in RPCEmu. Opening an Obey file in Zap (both original tartarus.org and the new tankstage builds) fails with the error “SWI &1DEF02 not known”. Tried with 3.71 and everything works as it should. Any ideas what it could be? |
Steve Pampling (1551) 8170 posts |
What version number of Zap? Zap has a copy of DeepKeys in use, but unless you are using the module from v1.46-pre2 or later it isn’t 32 bit and will fail in a 5.18/5.19 RPCEmu setup. NB. the release numbers around 1.46 are where much of the module support appears to have become 32 bit. |
Paul Nolan (1470) 18 posts |
Tried with 1.48 (the tankstage one) and latest one I could find on tartarus.org (1.47). 1.48 doesn’t appear to come with DeepKeys (or !Country) – tried with the copies included in 1.47 but no use. Harinezumi doesn’t seem to be reporting anything out of the ordinary going on. |
nemo (145) 2546 posts |
In any case, DeepKeys doesn’t have any SWIs to call, and I know I’ve been out of the loop but &1DEF02 seems a bit big to me. Who has the allocation files these days? |
Paul Nolan (1470) 18 posts |
I don’t think it actually is a SWI – Just loaded Zap in 3.71, made sure the Obey module was loaded and entered “SWI &1DEF02” into a new file in Code mode; it didn’t resolve to a name. Could it be trying to read data as code or something like that? |
nemo (145) 2546 posts |
That’s what I was implying. |
Jeffrey Lee (213) 6048 posts |
ROOL do. The publicly released allocations typically end up in the HdrSrc component, e.g. the SWI chunk listing is here |
Sprow (202) 1158 posts |
However, rotating 16 bits would be EF02001D which looks like SWI XOS_Bit + &1D. |
nemo (145) 2546 posts |
Ouch, good call. |
Theo Markettos (89) 919 posts |
I’ve tracked this down to ZapObey calling OS_Module 18 and not checking the error flag. But OS_Module 18 is failing:
works on my Pi (5.19 16-Oct-2012 is the first SD card I grabbed) but not on RPCEmu 0.8.9 Mac (OS 5.20), giving a “No more modules” error. However it does on RPCEmu 0.8.11 (OS 5.20) on Linux. So I suspect it’s one of the fixes that came in in 0.8.10. |