🚀 go-pugleaf

In article <1991Feb22.155750.1404@wuphys.wustl.edu> marty@wuphys.UUCP (Marty Olevitch) writes:
>We have an application that runs on a PC from ROM. Up until now, we have
>been using Aztec C to create the romable code, but now we are thinking of
>switching to Microsoft C for a number of reasons. Looking over the
>documentation, there is nothing on creating romable code with MSC. Can it be
>done?  Is it necessary to buy a separate linker or "locater", or can the MS
>link program be used?
>
>I am specifically looking for either some kind of instructions on creating
>romable code using the standard MSC tools, or a pointer to some literature
>on that topic. If a commercial linker/locater is the way to go, does anyone
>have recommendations for particular products (good experiences, stuff to
>avoid, etc).

Try Systems and Software link and locate products, their product contains
everything necessary for generating ROMable code. It is fashioned on the old
MDS-ISIS products and thus allows complete control over code/data placement. It also
generates Intel Hex files for downloading to your EPROM blower.

I don't think it is possible to generate ROMable code without a product like this.
I know for certain that MS-Link is not up to the job.

Also if at all possible change C compilers! Microsoft C has stack checking embedded
in many of its library routines, which ain't much use in a stand alone system. I
have used Turbo C and Turbo C++ and they work very well. If you insist on staying
with Microsoft C I suggest forking out for the library sources, they will save you
money in the long run.


Michael Traub
BT Customer Systems, Brighton Systems Centre. traub@rtf.bt.co.uk