[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: Olle Hedman <alh@home.se>
• Date: Wed, 12 Dec 2001 23:27:20 +0100
• In-Reply-To: <200112122150.fBCLo0m02912@sunsparc.hysoft-automation.com>
• References: <01c18345$aff2edc0$080a0a0a@ronald>
• Reply-To: assembly-83@lists.ticalc.org

At 22:49 2001-12-12, you wrote:
 >> won't it be extremely slow (assuming you're using bcall(_LCDBusy))?

>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...

You can read the lcd command port and check bit 7 if the lcd is busy or not.
I'm quite sure this is what he uses.
But this too, is quite slow, since checking the value takes in avarage 
longer time then an extra long "blind" delay...
At least it did last time I counted. I am known to have been wrong before :)

///Olle

• [A83] Re: Ion v1.6 garbled screen
• From: Patrick Davidson <pad@OCF.Berkeley.EDU>

• [A83] Re: Ion v1.6 garbled screen
• From: "Ronald Teune" <rtwolf@gmx.net>
• [A83] Re: Ion v1.6 garbled screen
• From: Peter-Martijn Kuipers <hyper@@hysoft-automation.com>

• Prev: [A83] image storage on 83+?
• Next: [A83] Re: Custom program loader
• Index(es):
  • Main
  • Thread