Envelope-to: 052922@sbc-85.com
Delivery-date: Sat, 24 Sep 2022 00:41:46 -0500
From: Michael Kamprath <michael@kamprath.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_EA81CEE6-A904-40BA-B17C-82DD9E5A7E78"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: MOSTEK 3870 Assembler
Message-Id: <C855369F-BB4C-4F0C-8C03-8AAC5B2F4031@kamprath.net>
Date: Fri, 23 Sep 2022 22:41:15 -0700
To: "052922@sbc-85.com" <052922@SBC-85.COM>


--Apple-Mail=_EA81CEE6-A904-40BA-B17C-82DD9E5A7E78
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi!

I saw your videos on your MOSTEK 38P70 project. They were very helpful =
for my own project using the chip, thanks!

I noted that you complained about some of the limitations of the DASM =
assembler. If you are interested, I have created a MOSTEK 3870 =
configuration for my customizable assembler, BespokeASM. You can check =
it out here:

=
https://github.com/michaelkamprath/bespokeasm/tree/main/examples/mostek-38=
70

I will say that the specific things you complained about (notably around =
address management) are much improved in BespokeASM. However, while the =
mnemonics are the same, the general assembly syntax around things like =
directives and labels is different from DASM. You can even define =
assembler macros.

Note that I am at the start f my project, so I expect my MOSTEK 3870 =
support to evolve some.=20

Anyway, I just thought I=E2=80=99d share.

Michael Kamprath


--Apple-Mail=_EA81CEE6-A904-40BA-B17C-82DD9E5A7E78
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Hi!<div class=3D""><br class=3D""></div><div class=3D"">I saw =
your videos on your MOSTEK 38P70 project. They were very helpful for my =
own project using the chip, thanks!</div><div class=3D""><br =
class=3D""></div><div class=3D"">I noted that you complained about some =
of the limitations of the DASM assembler. If you are interested, I have =
created a MOSTEK 3870 configuration for my customizable assembler, =
BespokeASM. You can check it out here:</div><div class=3D""><br =
class=3D""></div><blockquote style=3D"margin: 0 0 0 40px; border: none; =
padding: 0px;" class=3D""><div class=3D""><a =
href=3D"https://github.com/michaelkamprath/bespokeasm/tree/main/examples/m=
ostek-3870" =
class=3D"">https://github.com/michaelkamprath/bespokeasm/tree/main/example=
s/mostek-3870</a></div></blockquote><br class=3D""><div class=3D"">I =
will say that the specific things you complained about (notably around =
address management) are much improved in BespokeASM. However, while the =
mnemonics are the same, the general assembly syntax around things like =
directives and labels is different from DASM. You can even define =
assembler macros.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Note that I am at the start f my project, so I expect my =
MOSTEK 3870 support to evolve some.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Anyway, I just thought I=E2=80=99d =
share.</div><div class=3D""><br class=3D""></div><div class=3D"">Michael =
Kamprath</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_EA81CEE6-A904-40BA-B17C-82DD9E5A7E78--