Re: [M100] m200.def --- eventually m200smallclib hopefully
Alright! I figured most of this stuff would already be done, just scattered all over the place. (I don't know if I'll have anything ready to release tomorrow, if not it'll be next thur. before I have any time off...) Willard
Re: [M100] m200.def --- eventually m200smallclib hopefully
>Hi: I've got an M200 -- actually I may have more than one. What state of >goodness is required? >Ben > Working is all I need. I wouldn't care if it was a beater. Willard
Re: [M100] m200.def --- eventually m200smallclib hopefully
>There's always Virtual T! Actually very well suited to test suites. > I'm just not into emulators. They're just not my thing for some reason. :-) Willard
Re: [M100] m200.def --- eventually m200smallclib hopefully
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 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 goo...@sdc.org > Socorro, New Mexico, USA > I search my heart and find Cimmeria, land of Darkness and the Night. > -- R.E. Howard >
Re: [M100] m200.def --- eventually m200smallclib hopefully
Hi: I've got an M200 -- actually I may have more than one. What state of goodness is required? Ben From: M100 on behalf of Willard Goosey Sent: May 20, 2021 3:25 PM To: m100 list Subject: [M100] m200.def --- eventually m200smallclib hopefully 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 goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] m200.def --- eventually m200smallclib hopefully
" Lastly, anybody have a m200 for sale? :-)" There's always Virtual T! Actually very well suited to test suites. -- John.
[M100] m200.def --- eventually m200smallclib hopefully
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 goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
