[A83] Re: Ion v1.6 garbled screen


[Prev][Next][Index][Thread]

[A83] Re: Ion v1.6 garbled screen




Hmm, I remember reading in the SE addendum,
that thare's a memory address you can coll for an LCDBusy routine.
not quite sure though...

--Peter-Martijn
 
> 
> snip
> 
> >display controller slower than expected) bad things happen.  In regard to
> >Phoenix 1.51, I may actually have a real solution, though.  You can get an
> >experimental new version of it from:
> >
> >http//www.ocf.berkeley.edu/~pad/experimental/phoenixz-ti83.zip
> >http//www.ocf.berkeley.edu/~pad/experimental/phoenixz-ti83p.zip
> >
> >In this version, I use a copy routine which checks whether the display is
> >ready, so it should be able to adapt to any display speed, giving even the
> >extremely long delays needed on some 83+SEs.  But I'm not yet completely
> >sure this will work.
> 
> won't it be extremely slow (assuming you're using bcall(_LCDBusy))?
> 
> 
> 
> 





Follow-Ups: References: