Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!pur-ee!ea.ecn.purdue.edu!wieland
From: wieland@ea.ecn.purdue.edu (Jeffrey J Wieland)
Newsgroups: comp.os.cpm
Subject: Re: Turb Modula 2 problems
Message-ID: <16196@ea.ecn.purdue.edu>
Date: 6 Oct 89 16:42:54 GMT
References: <89100422391364@masnet.uucp>
Reply-To: wieland@ea.ecn.purdue.edu.UUCP (Jeffrey J Wieland)
Organization: Purdue University Engineering Computer Network
Lines: 31

In article <89100422391364@masnet.uucp> wayne.hortensiu@canremote.uucp (WAYNE HORTENSIU) writes:
>I'm unable to get REL.MCD to convert a .REL file to a .MCD file. When I
>run it from with TM2, I get an out of memory error. Linking it to
>REL.COM and running it from the command line gets me an
>IllegalInstruction in module 7h/@p5 error. The call stack displays a
>module name of AAAAAA, followed by READSY, followed by REL. The AAAAAA
>certainly doesn't sound right...

>Can anyone shed some light on what is happening here? I've read that REL 
>is a memory hog, but it should be able to convert a short (8-line)
>assembler file, shouldn't it?

Unfortunately, REL.MCD cannot be made into a runnable .COM file.  The
REL.MCD for the unreleased TM2 1.1 is supposed to ba able to be made
into a COM file.  I ran across a reference to this on the old Echelon
ZNODE Central some time back.

Have you tried the simple example in the TM2 Reference Manual?  I was
able to .REL'ify it without difficulty with my Kaypro (57.25 K TPA).

My best suggestion is make sure that you have as much free memory as
possible.  Boot the bare minimum system that you can -- no TSR-type
programs, DateStamper, Z-System, externally loaded drivers, or 
what-have-you.  Then try again.

If that fails, perhaps you find a CP/M machine with a bigger TPA that
you can use to generate the .REL files.  A CP/M 3.0 machine might 
work well.
--
			    Jeff Wieland
			wieland@acn.purdue.edu