[A83] Re: Ion v1.6 garbled screen

[A83] Re: Ion v1.6 garbled screen

• To: assembly-83@lists.ticalc.org
• Subject: [A83] Re: Ion v1.6 garbled screen
• From: Peter-Martijn Kuipers <hyper@@hysoft-automation.com>
• Date: Wed, 12 Dec 2001 22:49:58 +0100 (CET)
• In-Reply-To: <01c18345$aff2edc0$080a0a0a@ronald> from "Ronald Teune" at Dec 12, 2001 08:46:26 PM
• Reply-To: assembly-83@lists.ticalc.org

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))?
> 
> 
> 
> 

• [A83] Re: Ion v1.6 garbled screen
• From: Olle Hedman <alh@home.se>

• [A83] Re: Ion v1.6 garbled screen
• From: "Ronald Teune" <rtwolf@gmx.net>

• Prev: [A83] Re: Custom program loader
• Next: [A83] Re: Back to the home screen
• Index(es):
  • Main
  • Thread