Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!ut-ngp!melpad!osi3b2!james
From: james@osi3b2.UUCP (James R. Van Artsdalen)
Newsgroups: net.micro.pc
Subject: Re: MSC V4.0 - ROMable code?
Message-ID: <211@osi3b2.UUCP>
Date: Thu, 25-Sep-86 00:32:09 EDT
Article-I.D.: osi3b2.211
Posted: Thu Sep 25 00:32:09 1986
Date-Received: Thu, 25-Sep-86 07:22:35 EDT
References: <3720@mnetor.UUCP>
Organization: Origin Systems Inc.
Lines: 22
Keywords: Can MSC generate ROMable code?
Summary: supposedly yes

In article <3720@mnetor.UUCP>, george@mnetor.UUCP (George Hart) writes:
When microsoft claims that they can support ROMable code, they probably
mean that since you have the source to the startup and exit routines, you
can force the generated code to be located at the address of the ROM and force
the data and stack to be where known RAM is, instead of letting the linker
choose the addresses.  I don't know if their linker will let you do this or
if you have to write your our linker from their documentation.  Possible, but
not trivial.

> Needless to say, my friend is more than annoyed, especially since there
> are existing compilers costing 75% less than MSC V4.0 that generate
> ROMable code.

MS-C may be very expensive, but it generates excellant code, enough so that
there is rarely a need to hand-code routines.  You could do better by hand
of course, but you're past the point of dimishing returns in most cases.  The
compiler is also slow compared to others I am told, but it is very complete,
and the source-level debugger that comes with it is outstanding (if it works
with your EGA - it doesn't work well with mine).  I am using it for Ultima IV
because of the code quality and the debugger.
-- 
James R. Van Artsdalen    ...!ut-ngp!utastro!osi3b2!james    Live Free or Die