Totally unrelated but thank you for sharing this!
On Sun, Jan 23, 2022, 18:24 Stephen Adolph wrote:
> my current rom location decoder ring...
>
> -- Forwarded message -
> From: Stephen Adolph
> Date: Sun, Jan 23, 2022 at 11:21 AM
> Subject: Re: [M100] t200 addresses? from
So, which addresses for the named routines actually work?I'm especially nervous
about the off-by-one differences...I still don't have a T200 so I can't test
this myself... :-(WillardSent from my Galaxy Tab® A
null
I was looking at that today...I can't even get the dependencies of the
dependencies for raspian jesse.Im afraid my linux boxen are almost as outdated
as my model 100!WillardSent from my Galaxy Tab® A
null
I think Steve Adolph created the t200 file?
-- John.
On Sat, Jan 22, 2022, 6:47 PM Willard Goosey wrote:
> I'm seeing different addresses in hterm.git/lib/T200rom*.asm
> can a t200 dev confirm these?
> LCD 503CH (everywhere else)
> LCD 5030H (T200rom_published_lib.asm)
>
> KYREAD 0C00H
>
I did; I can send it again to the list.
lets see if it gets through the size filter!
On Sun, Jan 23, 2022 at 6:03 PM John R. Hogerhuis wrote:
> I think Steve Adolph created the t200 file?
>
> -- John.
>
> On Sat, Jan 22, 2022, 6:47 PM Willard Goosey wrote:
>
>> I'm seeing different addresses
I think you could test this pretty effectively in Virtual T.
you could set a breakpoint at the final return, and then try calling the
routines from BASIC.
Also, sometimes both entries can be valid. Depends on the use case.
Steve
On Sun, Jan 23, 2022 at 6:58 PM Willard Goosey wrote:
> So,
