Discussion:
Semicolon instead of 1 in time display (Logitech 3.40 and M2M-PC System - v1.35 for MS-DOS)
(too old to reply)
modsquad
2010-03-28 15:58:55 UTC
Permalink
If I run the "time" command in the interpreter of the M2M-PC System -
the display of the year shows a semicolon instead of 1 in the year:
*time gives:
... 20;0 instead of the correct 2010

The same problem exists in Logitech 3.40 m2 system and is seen when
running the example program DIGCLOCK.MOD that Logitech includes, which
uses the library module TIMEDATE.MOD

(Likewise same problem in the DIGCLOCK.MOD example in Multiscope 4.0
m2)

Q0.) Can anyone check this in some non-MSDOS based m2 system?
Q1.) Is it a Y2K related problem?

Q2.) Anyone know the best fix to this, assuming one has the library
source to TIMEDATE.MOD

Q3.) Since M2M-PC System v1.35 does not seem to include the source for
the time command or any of the library source for time related
commands, I also don't know how to fix this either.

Carl
Chris Burrows
2010-03-28 23:25:21 UTC
Permalink
"modsquad" <***@yahoo.com> wrote in message
news:bc219a23-a36e-4bd3-b09f-***@j16g2000prn.googlegroups.com...
> If I run the "time" command in the interpreter of the M2M-PC System -
> the display of the year shows a semicolon instead of 1 in the year:
> *time gives:
> ... 20;0 instead of the correct 2010
>
> The same problem exists in Logitech 3.40 m2 system and is seen when
> running the example program DIGCLOCK.MOD that Logitech includes, which
> uses the library module TIMEDATE.MOD
>
> (Likewise same problem in the DIGCLOCK.MOD example in Multiscope 4.0
> m2)
>
> Q0.) Can anyone check this in some non-MSDOS based m2 system?
> Q1.) Is it a Y2K related problem?
>
> Q2.) Anyone know the best fix to this, assuming one has the library
> source to TIMEDATE.MOD
>
> Q3.) Since M2M-PC System v1.35 does not seem to include the source for
> the time command or any of the library source for time related
> commands, I also don't know how to fix this either.
>

It suspect a problem in the formatting. A quick test indicates the following
program works in M2MPC:

MODULE ShowTime;

FROM OutTerminal IMPORT WriteC, WriteLn;
FROM Monitor IMPORT GetTime, Time;

(*
Time = RECORD
day: CARDINAL; (* ((year-1900)*20B + month)*40B + day
*)
minute: CARDINAL; (* hour*60 + minute *)
millisecond: CARDINAL; (* second*1000 + msecond *)
END;
*)
VAR
t: Time;
month, day, year: CARDINAL;

BEGIN
GetTime(t);
year := t.day DIV 1000B;
month := (t.day DIV 40B) MOD 40B;
day := t.day MOD 40B;

WriteC(year + 1900, 6); WriteLn;
WriteC(month, 6); WriteLn;
WriteC(day, 6); WriteLn;
END ShowTime.

Regards,
Chris Burrows

CFB Software
http://www.cfbsoftware.com/modula2
modsquad
2010-03-29 16:36:18 UTC
Permalink
Hello everyone.

TO: Chris Burrows

I don't have any DEF or MOD files in M2Sys135 directory (other than
for InOut).
I have OUTTERMI.SYM/.OBJ and MONITOR.SYM
Not in M2MCompilerSource either.

Ok, I did find OutTerminal def listing in the Modula2 Handbook PDF

Are you using the original commercial release of M2Sys135 from MRI or
what?

Thanks again for your input on the year issue.

Carl

On Mar 28, 4:25 pm, "Chris Burrows" <***@hotmail.com> wrote:
> "modsquad" <***@yahoo.com> wrote in message
>
> news:bc219a23-a36e-4bd3-b09f-***@j16g2000prn.googlegroups.com...
>
>
>
> > If I run the "time" command in the interpreter of the M2M-PC System -
> > the display of the year shows a semicolon instead of 1 in the year:
> > *time gives:
> > ... 20;0 instead of the correct 2010
>
> > The same problem exists in Logitech 3.40 m2 system and is seen when
> > running the example program DIGCLOCK.MOD that Logitech includes, which
> > uses the library module TIMEDATE.MOD
>
> > (Likewise same problem in the DIGCLOCK.MOD example in Multiscope 4.0
> > m2)
>
> > Q0.) Can anyone check this in some non-MSDOS based m2 system?
> > Q1.) Is it a Y2K related problem?
>
> > Q2.) Anyone know the best fix to this, assuming one has the library
> > source to TIMEDATE.MOD
>
> > Q3.) Since M2M-PC System v1.35 does not seem to include the source for
> > the time command or any of the library source for time related
> > commands, I also don't know how to fix this either.
>
> It suspect a problem in the formatting. A quick test indicates the following
> program works in M2MPC:
>
> MODULE ShowTime;
>
>   FROM OutTerminal IMPORT WriteC,  WriteLn;
>   FROM Monitor IMPORT GetTime, Time;
>
> (*
>     Time = RECORD
>              day:         CARDINAL; (* ((year-1900)*20B + month)*40B + day
> *)
>              minute:      CARDINAL; (* hour*60 + minute *)
>              millisecond: CARDINAL; (* second*1000 + msecond *)
>            END;
> *)
>  VAR
>    t: Time;
>    month, day, year: CARDINAL;
>
> BEGIN
>   GetTime(t);
>   year := t.day DIV 1000B;
>   month := (t.day DIV 40B) MOD 40B;
>   day := t.day MOD 40B;
>
>   WriteC(year + 1900, 6); WriteLn;
>   WriteC(month, 6); WriteLn;
>   WriteC(day, 6); WriteLn;
> END ShowTime.
>
> Regards,
> Chris Burrows
>
> CFB Softwarehttp://www.cfbsoftware.com/modula2
Chris Burrows
2010-03-30 02:12:16 UTC
Permalink
"modsquad" <***@yahoo.com> wrote in message
news:a0a960a7-4f76-4806-842a-***@f14g2000pre.googlegroups.com...

> I don't have any DEF or MOD files in M2Sys135 directory (other than
> for InOut).
> I have OUTTERMI.SYM/.OBJ and MONITOR.SYM
> Not in M2MCompilerSource either.
>
> Ok, I did find OutTerminal def listing in the Modula2 Handbook PDF
>
> Are you using the original commercial release of M2Sys135 from MRI or
> what?

Yes - I'm using the v1.35 version that you can download from my website:

http://www.cfbsoftware.com/modula2

You do not need the OBJ, DEF or MOD files to compile and run the ShowTime
example on M2MPC. The SYM files are all you need to compile the code. The
library executables (e.g. Monitor) are already in the runtime.

You are right - Monitor is not documented in M2MPC so some detective work
was need to determine that:

a) Monitor includes the time-related definitions

b) The nature of the definitions in Monitor.

If you use the M2MPC decode command you will see that Time.obj imports
Terminal and Monitor. All that remains is to find out what is exported from
Monitor:

Monitor is documented in Svend Erik Knudsen's paper on Medos-2, the Lilith
operating system. Some parts may not be applicable to M2MPC but, fortunately
for this exercise, 'time' seems to be compatible. You can download a pdf
copy of the Medos-2 paper from here:

http://e-collection.ethbib.ethz.ch/view/eth:21975

Alternatively, the source code of Monitor Lilith source code is included
with Jos Dreesen's Lilith Emulator 'Emulith' which you can download from:

ftp://jdreesen.dyndns.org/ftp/Emulith/

Both are invaluable resources if you intend spending some time on M2MPC.

P.S. Comint V4.2 under Emulith displays 2010 dates correctly ;-)

Regards,
Chris

Chris Burrows
CFB Software
http://www.cfbsoftware.com/modula2
modsquad
2010-03-30 15:59:40 UTC
Permalink
Hello again and much thanks.

Just tried it in M2M-PC and it works fine.

Have a problem with "inspect" command that just displays nul
characters, stops ok when a key is pressed, but otherwise just runs in
a endless loop. Don't need inspect that badly because there are
alternatives.

When you are at the star (*) prompt, I know you can enter a secondary
DOS shell with exclamation (!) and then go back to the star prompt by
typing "EXIT", but:
Q4.) Is there a proper command (not Ctrl-C) to completely exit M2M-PC
from the star prompt?

Thanks for all the links. I am looking forward to trying Emulith since
I always wanted to own a Lilith but couldn't come even close to
affording one.

The M2M-PC interpreter reminds me of the earliest Logitech systems
that used a similar command interpreter and LOD files.

One of the MEDOS features seems to have been inherited by Logitech:
fast file system buffering. I once estimated Logitech 3.40 FileSystem
was 4 times faster in file copy application compared to Multiscope 4.0

I guess you won't hear from me again on date questions until Dec 31,
2027

Just joking, but I wouldn't want to be a retired Cobol programmer in
case the Y2K fixes didn't address the 2027 issue 10 years ago.

Carl

On Mar 29, 7:12 pm, "Chris Burrows" <***@hotmail.com> wrote:
> "modsquad" <***@yahoo.com> wrote in message

> news:a0a960a7-4f76-4806-842a-***@f14g2000pre.googlegroups.com...
>
> > I don't have any DEF or MOD files in M2Sys135 directory (other than
> > for InOut).
> > I have OUTTERMI.SYM/.OBJ and MONITOR.SYM
> > Not in M2MCompilerSource either.
>
> > Ok, I did find OutTerminal def listing in the Modula2 Handbook PDF
>
> > Are you using the original commercial release of M2Sys135 from MRI or
> > what?
>
> Yes - I'm using the v1.35 version that you can download from my website:
>
> http://www.cfbsoftware.com/modula2
>
> You do not need the OBJ, DEF or MOD files to compile and run the ShowTime
> example on M2MPC. The SYM files are all you need to compile the code. The
> library executables (e.g. Monitor) are already in the runtime.
>
> You are right - Monitor is not documented in M2MPC so some detective work
> was need to determine that:
>
> a) Monitor includes the time-related definitions
>
> b) The nature of the definitions in Monitor.
>
> If you use the M2MPC decode command you will see that Time.obj imports
> Terminal and Monitor. All that remains is to find out what is exported from
> Monitor:
>
> Monitor is documented in Svend Erik Knudsen's paper on Medos-2, the Lilith
> operating system. Some parts may not be applicable to M2MPC but, fortunately
> for this exercise, 'time' seems to be compatible. You can download a pdf
> copy of the Medos-2 paper from here:
>
> http://e-collection.ethbib.ethz.ch/view/eth:21975
>
> Alternatively, the source code of Monitor Lilith source code is included
> with Jos Dreesen's Lilith Emulator 'Emulith' which you can download from:
>
> ftp://jdreesen.dyndns.org/ftp/Emulith/
>
> Both are invaluable resources if you intend spending some time on M2MPC.
>
> P.S. Comint V4.2 under Emulith displays 2010 dates correctly ;-)
>
> Regards,
> Chris
>
> Chris Burrows
> CFB Softwarehttp://www.cfbsoftware.com/modula2
modsquad
2010-03-30 19:06:55 UTC
Permalink
(reply to my own post:)

In regards to ETH e-link to "MEDOS-2" thesis by Svend Erik Knudsen

The file ends at page 26 or thereabouts with an actual %%END.
The description of Monitor library is in the missing part.

So I will let ETH know that file appears incomplete.
Search on internet for PS version proved futile.

Carl
---
modsquad wrote:
> Hello again and much thanks.
>
> Just tried it in M2M-PC and it works fine.
>
> Have a problem with "inspect" command that just displays nul
> characters, stops ok when a key is pressed, but otherwise just runs in
> a endless loop. Don't need inspect that badly because there are
> alternatives.
>
> When you are at the star (*) prompt, I know you can enter a secondary
> DOS shell with exclamation (!) and then go back to the star prompt by
> typing "EXIT", but:
> Q4.) Is there a proper command (not Ctrl-C) to completely exit M2M-PC
> from the star prompt?
>
> Thanks for all the links. I am looking forward to trying Emulith since
> I always wanted to own a Lilith but couldn't come even close to
> affording one.
>
> The M2M-PC interpreter reminds me of the earliest Logitech systems
> that used a similar command interpreter and LOD files.
>
> One of the MEDOS features seems to have been inherited by Logitech:
> fast file system buffering. I once estimated Logitech 3.40 FileSystem
> was 4 times faster in file copy application compared to Multiscope 4.0
>
> I guess you won't hear from me again on date questions until Dec 31,
> 2027
>
> Just joking, but I wouldn't want to be a retired Cobol programmer in
> case the Y2K fixes didn't address the 2027 issue 10 years ago.
>
> Carl
>
> On Mar 29, 7:12 pm, "Chris Burrows" <***@hotmail.com> wrote:
> > "modsquad" <***@yahoo.com> wrote in message
>
> > news:a0a960a7-4f76-4806-842a-***@f14g2000pre.googlegroups.com...
> >
> > > I don't have any DEF or MOD files in M2Sys135 directory (other than
> > > for InOut).
> > > I have OUTTERMI.SYM/.OBJ and MONITOR.SYM
> > > Not in M2MCompilerSource either.
> >
> > > Ok, I did find OutTerminal def listing in the Modula2 Handbook PDF
> >
> > > Are you using the original commercial release of M2Sys135 from MRI or
> > > what?
> >
> > Yes - I'm using the v1.35 version that you can download from my website:
> >
> > http://www.cfbsoftware.com/modula2
> >
> > You do not need the OBJ, DEF or MOD files to compile and run the ShowTime
> > example on M2MPC. The SYM files are all you need to compile the code. The
> > library executables (e.g. Monitor) are already in the runtime.
> >
> > You are right - Monitor is not documented in M2MPC so some detective work
> > was need to determine that:
> >
> > a) Monitor includes the time-related definitions
> >
> > b) The nature of the definitions in Monitor.
> >
> > If you use the M2MPC decode command you will see that Time.obj imports
> > Terminal and Monitor. All that remains is to find out what is exported from
> > Monitor:
> >
> > Monitor is documented in Svend Erik Knudsen's paper on Medos-2, the Lilith
> > operating system. Some parts may not be applicable to M2MPC but, fortunately
> > for this exercise, 'time' seems to be compatible. You can download a pdf
> > copy of the Medos-2 paper from here:
> >
> > http://e-collection.ethbib.ethz.ch/view/eth:21975
> >
> > Alternatively, the source code of Monitor Lilith source code is included
> > with Jos Dreesen's Lilith Emulator 'Emulith' which you can download from:
> >
> > ftp://jdreesen.dyndns.org/ftp/Emulith/
> >
> > Both are invaluable resources if you intend spending some time on M2MPC.
> >
> > P.S. Comint V4.2 under Emulith displays 2010 dates correctly ;-)
> >
> > Regards,
> > Chris
> >
> > Chris Burrows
> > CFB Softwarehttp://www.cfbsoftware.com/modula2
Jos Dreesen
2010-03-30 19:34:32 UTC
Permalink
modsquad wrote:
> (reply to my own post:)
>
> In regards to ETH e-link to "MEDOS-2" thesis by Svend Erik Knudsen
>
> The file ends at page 26 or thereabouts with an actual %%END.
> The description of Monitor library is in the missing part.
>
> So I will let ETH know that file appears incomplete.
> Search on internet for PS version proved futile.
>


You can also find it on bitsavers, www.bitsavers.org/pdf/eth


Jos
modsquad
2010-03-30 22:30:41 UTC
Permalink
Thanks, a whole directory of Lilith manuals!
So much to read, so little time!

Carl
---
Jos Dreesen wrote:
> modsquad wrote:
> > (reply to my own post:)
> >
> > In regards to ETH e-link to "MEDOS-2" thesis by Svend Erik Knudsen
> >
> > The file ends at page 26 or thereabouts with an actual %%END.
> > The description of Monitor library is in the missing part.
> >
> > So I will let ETH know that file appears incomplete.
> > Search on internet for PS version proved futile.
> >
>
>
> You can also find it on bitsavers, www.bitsavers.org/pdf/eth
>
>
> Jos
Chris Burrows
2010-03-30 23:17:44 UTC
Permalink
"modsquad" <***@yahoo.com> wrote in message
news:f3f9e9f0-02cd-43ae-b281-***@y17g2000yqd.googlegroups.com...
>
>Q4.) Is there a proper command (not Ctrl-C) to completely exit
>M2M-PC from the star prompt?
>

Not that I know of. I just use Ctrl-C

>Thanks for all the links. I am looking forward to trying
>Emulith since I always wanted to own a Lilith but couldn't
>come even close to affording one.
>

I wanted one badly as well but Emulith is the next best thing. It is a
remarkable achievement. There is a lot of work being done in the area of
recreating vintage systems using modern hardware (e.g. FPGA, solid-state
drives etc.) If Jos (or anybody else) ever comes up with a modern hardware
implementation of a Lilith I'll be tempted to buy one ;-)

>The M2M-PC interpreter reminds me of the earliest Logitech
>systems that used a similar command interpreter and LOD files.
>

Not surprising. I believe the initial Logitech compiler was just another PC
port of the Lilith system. The commentary about the passes during
compilation is very similar and the LOD files are executed under control of
Logitech's program M2.EXE instead of M2MPC's INTERP.EXE. It might be
interesting to see if the M2MPC decode can decode a LOD file ...

>
>I guess you won't hear from me again on date questions until Dec 31,
>2027
>
>Just joking, but I wouldn't want to be a retired Cobol
>programmer in case the Y2K fixes didn't address the 2027 issue
>10 years ago.
>

Funny you should say that. While working on this it occurred to me that if
software can be reliably expected to be executed 27 years later then next
year it is time for the Unix guys to start worrying about the 2038 bug:

http://www.2038bug.com/

Regards,
Chris
Fruttenboel
2010-03-29 09:59:48 UTC
Permalink
On Mar 28, 5:58 pm, modsquad <***@yahoo.com> wrote:
> If I run the "time" command in the interpreter of the M2M-PC System -
> the display of the year shows a semicolon instead of 1 in the year:
> *time gives:
> ... 20;0 instead of the correct 2010
>
> The same problem exists in Logitech 3.40 m2 system and is seen when
> running the example program DIGCLOCK.MOD that Logitech includes, which
> uses the library module TIMEDATE.MOD
>
> (Likewise same problem in the DIGCLOCK.MOD example in Multiscope 4.0
> m2)
>
> Q0.) Can anyone check this in some non-MSDOS based m2 system?
> Q1.) Is it a Y2K related problem?

Yes, but a weird one...

In many cheap systems, the '19' was preprinted and the year was added
so you would get 19110 as the year... :o)
The ASCII sequence is 0 1 2 3 4 5 6 7 8 9 : ; < = > ? so that figures.
Apparently the program was written in the early 90's.

> Q2.) Anyone know the best fix to this, assuming one has the library
> source to TIMEDATE.MOD

Rewrite TimeDate.mod like Chris showed.

> Q3.) Since M2M-PC System v1.35 does not seem to include the source for
> the time command or any of the library source for time related
> commands, I also don't know how to fix this either.

The disadvantage of the DEF/IMP system.... You just need to make a new
IMP module that fits the shoe of the corresponding DEF module and
recompile all programs. It's not important how exactly you write your
IMP module. You could suffice with a Foreign Module that relies on the
underlying operating system's C functions. As long as the functions in
the IMP module have the same procedure body as your DEF module.
Chris Burrows
2010-03-29 11:52:46 UTC
Permalink
"Fruttenboel" <***@gmail.com> wrote in message
news:b4818ea5-19ab-4e4d-9c74-***@e6g2000yqh.googlegroups.com...
>
> In many cheap systems, the '19' was preprinted and the year was added
> so you would get 19110 as the year... :o)
> The ASCII sequence is 0 1 2 3 4 5 6 7 8 9 : ; < = > ? so that figures.
> Apparently the program was written in the early 90's.
>

Actually the M2MPC code was written in the early 80's. I guess they didn't
anticipate that we would still be running their actual code 27 years later!

You are right about the ASCII sequence though. The year number is an offset
from 1900. The following code would correctly display "00" to "99" for 1900
to 1999. However, it would display ";0" for 2010 because 110 DIV 10 = 11

Write(CHR(year DIV 10 + ORD('0'))); Write(CHR(year MOD 10 + ORD('0')));

Regards,
Chris
modsquad
2010-03-29 14:43:24 UTC
Permalink
Thanks everyone for all the help!
Carl

On Mar 29, 4:52 am, "Chris Burrows" <***@hotmail.com> wrote:
> "Fruttenboel" <***@gmail.com> wrote in message
>
> news:b4818ea5-19ab-4e4d-9c74-***@e6g2000yqh.googlegroups.com...
>
>
>
> > In many cheap systems, the '19' was preprinted and the year was added
> > so you would get 19110 as the year... :o)
> > The ASCII sequence is 0 1 2 3 4 5 6 7 8 9 : ; < = > ? so that figures.
> > Apparently the program was written in the early 90's.
>
> Actually the M2MPC code was written in the early 80's. I guess they didn't
> anticipate that we would still be running their actual code 27 years later!
>
> You are right about the ASCII sequence though. The year number is an offset
> from 1900. The following code would correctly display "00" to "99" for 1900
> to 1999. However, it would display ";0" for 2010 because 110 DIV 10 = 11
>
> Write(CHR(year DIV 10 + ORD('0'))); Write(CHR(year MOD 10 + ORD('0')));
>
> Regards,
> Chris
modsquad
2010-03-31 21:42:47 UTC
Permalink
Hello:

decode on a LOD file doesn't work, but ...
I wonder if I should try converting LOD file first? (Is endian-ness an
issue?)

Not sure what .RLP refers to but somehow I doubt its a plotter file.

Probably I should see if the Logitech interpreter has a decode command
as well.
Problem is I may only have it on 5.25" floppies!

Maybe I will try again later.
...
Comint IV0 29.9.83

Modula - 2 Interpreter
Version 1.35 (C)Copyright Modula Research Institute 1983
*decode
decode >testmem.lod
illegal symbol read
file not a .RLP file
decode unsuccessful
*

Carl
-----

On Mar 30, 4:17 pm, "Chris Burrows" <***@hotmail.com> wrote:
> "modsquad" <***@yahoo.com> wrote in message
>
> news:f3f9e9f0-02cd-43ae-b281-***@y17g2000yqd.googlegroups.com...

snip ...

> >The M2M-PC interpreter reminds me of the earliest Logitech
> >systems that used a similar command interpreter and LOD files.
>
> Not surprising. I believe the initial Logitech compiler was just another PC
> port of the Lilith system. The commentary about the passes during
> compilation is very similar and the LOD files are executed under control of
> Logitech's program M2.EXE instead of M2MPC's INTERP.EXE. It might be
> interesting to see if the M2MPC decode can decode a LOD file ...
>

snip...

> Regards,
> Chris
Chris Burrows
2010-03-31 22:36:14 UTC
Permalink
"modsquad" <***@yahoo.com> wrote in message
news:afe12eb6-bbce-4efc-aa6b-***@h4g2000pre.googlegroups.com...
Hello:

decode on a LOD file doesn't work, but ...
I wonder if I should try converting LOD file first? (Is endian-ness an
issue?)

Not sure what .RLP refers to but somehow I doubt its a plotter file.

Probably I should see if the Logitech interpreter has a decode command
as well.
Problem is I may only have it on 5.25" floppies!

Maybe I will try again later.
...
Comint IV0 29.9.83

Modula - 2 Interpreter
Version 1.35 (C)Copyright Modula Research Institute 1983
*decode
decode >testmem.lod
illegal symbol read
file not a .RLP file
decode unsuccessful
*

Carl
-----

On Mar 30, 4:17 pm, "Chris Burrows" <***@hotmail.com> wrote:
> "modsquad" <***@yahoo.com> wrote in message
>
> news:f3f9e9f0-02cd-43ae-b281-***@y17g2000yqd.googlegroups.com...

snip ...

> >The M2M-PC interpreter reminds me of the earliest Logitech
> >systems that used a similar command interpreter and LOD files.
>
> Not surprising. I believe the initial Logitech compiler was just another
> PC
> port of the Lilith system. The commentary about the passes during
> compilation is very similar and the LOD files are executed under control
> of
> Logitech's program M2.EXE instead of M2MPC's INTERP.EXE. It might be
> interesting to see if the M2MPC decode can decode a LOD file ...
>

snip...

> Regards,
> Chris
Chris Burrows
2010-03-31 23:02:44 UTC
Permalink
> "modsquad" <***@yahoo.com> wrote in message
> news:<afe12eb6-bbce-4efc-aa6b-***@h4g2000pre.googlegr
> oups.com>...

Oops - sorry about the previous non-reply - I pressed the send button too
soon :-(

>
> decode on a LOD file doesn't work, but ...
> I wonder if I should try converting LOD file first? (Is endian-ness an
> issue?)
>

Yes. Looking at a HEX output of LOD / OBJ indicates that endian-ness is at
least one of the issues - I'm not going to pursue it any further.

Many years ago I ported Wirth's M-Code interpreter (from Appendix 1 of the
Lilith 'Yellow Report') to a couple of systems including a MC68000-based
Unix system. Managed to get some simple executables generated by M2MPC to
run on those systems - one of the most frustrating parts of the whole
exercise was the endian-ness issue.

> Not sure what .RLP refers to but somehow I doubt its a plotter file.
>
> Probably I should see if the Logitech interpreter has a decode command
> as well.

The only programs (*.LOD) I could find on the v1.1 disks are the compiler,
linker and post-mortem debugger. The later versions of Logitech compile to
standalone executables.

> Problem is I may only have it on 5.25" floppies!
>

I picked up a couple of 5.25" drives on eBay last year - they crop up quite
regularly.

Regards,
Chris
Loading...