Great find... how about switch to Apple Logo and extend it with machine language to use that hardware?
That could be WAY more practical.
DC

Do we know anything about the actual lineage of Lego Logo?  Is it
derived from some other Logo implementation?

The reason I ask is because at least with Apple Logo there are hooks
implemented for assembly language (at least according to page 238 of
http://www.virtualapple.org/docs/Apple%20Logo%20II%20Reference%20Manual.pdf)

It's possible that such hooks also exist for Lego Logo if it were
derived from some less child-oriented implementation (i.e. present in
the upstream but not documented in Lego's docs).

Devin

On Tue, Jan 17, 2017 at 9:49 PM, Douglas Crawford via vcf-midatlantic
<vcf-midatlantic@lists.vintagecomputerfederation.org> wrote:

On 1/17/2017 7:06 PM, Evan Koblentz via vcf-midatlantic wrote:

This is getting to be what may be an insurmountable challenge. The Logo
in
question is Lego Logo, and the disk is in a non-standard format, as I
discovered when I tried to convert it with ciderpress (I wanted to use a
very nice disassembler I found for the IIgs). The disk is self booting,
so
even if I can get the code into a disassembler, writing changes back to a
usable format is going to be a major challenge. So far I have not found a
way to do it.

Changed subject line to match thread fork.

Yikes that's perhaps a show stopper for modifying the executable file.
At best a program would patch the in memory image after the boot of LEGO,
which also will be tricky.