[A83] Re: statvars...??? [Ti83+]
[Prev][Next][Index][Thread]
[A83] Re: statvars...??? [Ti83+]
> Van: Dan Englender <dan@calc.org>
>
> Yeah, there's a few "bugs" in ion.inc, and that's one of them. They
stem
> from the fact that I really didn't want to type up ion.inc, but that Joe
> said he wouldn't make an 83 version of Ion otherwise...So it wasn't a
really
> careful job :) Anyhow, due to that little mistake, nearly no 83P Ion
> programs use statVars (which is OK, if the 83 version uses statVars, the
83P
> version can use appBackUpScreen).
I hope that it was that Joe W. didn't want to make an 83 >>PLUS<< version
if you didn't type ion.inc... btw: We better just use ti83plus.inc and
squish.inc after all?
> And because statVars isn't used by 83P Ion progs (except for Boulderdash,
> and maybe one other), MirageOS installs it's interrupt stuff there.
Thus,
> if you're developing an Ion program and want it to be compatible with
> MirageOS, either don't use 83P statVars (which, as I said before, can be
> remedied by using appBackUpScreen for the 83P version, and statVars for
the
> 83 version), or set IM 1 at the beginning of your program to disable the
> MirageOS interrupt.
What mem-areas are used by Ion on the Ti83 anyways? I hate it that Joe
didn't document his shells like the others (exept Bill Nagel) did...
Could my interrupt-problem be related to that?
BTW: I found out what the 'bug' is when using the MirageOS interrupt with
the z88dk, the MirageOS interrupt probably *only* does a "exx \ ex
af,af"... [Most] z88dk programs also uses the shadow registers, so the
interrupt program should save them [too], like push/pop'ing them on the
stack.
To fix this I now just install my own interrupt, also when compiling for
MirageOS.
Henk Poley
Follow-Ups: