Hi Williard, I found a cross reference list on Club100 at
https://ftp.whtech.com/club100/ref/cross1.doc that says that 1BB1h on the 100 is 2697h on the 200 (for RSTDOG) and another link at https://ftp.whtech.com/club100/ref/cross2.doc (the second list) says F932 on the 100 is F222 on the 200 although that entry has an asterisk saying it didn't come from the same reliable source as the other and that it isn't tested. I'm willing to test on my T200 if you have anything to test. Regards, Douglas On Thu, May 20, 2021 at 2:25 PM Willard Goosey <[email protected]> wrote: > So, due to popular demand (one d00d asked) I've started putting > together a m200.def to match m100.def. This will hopefully lead to an > equally (in)capable m200smallclib, but first things first!!! > > This is complicated by the fact that I don't have a m200... This is > pre-alpha completely untested stuff! > > So, starting from the club100 scan of the m200 techref, there are some > addresses I just can't read. They are: > CHPLPT > SNDCOM(*) > INZCOM > > (*)also need to know if SNDCOM is the same evil hack of "jump into the > middle of sd232 (which preserves BC) so we need a dummy value on the > stack" as the m100 call. > > Also, to get smallclib's cstart.a85 fully working I need the m200 > versions of these: > RSTDOG (1bb1h on m100) > POWERFLAG (0f932h on m100) > > > Last week was hell at work so I haven't had a chance to do any other > research. URLs to other m200 assembly docs welcome! > > Lastly, anybody have a m200 for sale? :-) > > Willard > -- > Willard Goosey [email protected] > Socorro, New Mexico, USA > I search my heart and find Cimmeria, land of Darkness and the Night. > -- R.E. Howard >
