Xref: utzoo comp.os.msdos.programmer:3555 comp.sys.ibm.pc.hardware:5868 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tut.cis.ohio-state.edu!n8emr!bluemoon!andy From: andy@bluemoon.uucp (Andy Vaught) Newsgroups: comp.os.msdos.programmer,comp.sys.ibm.pc.hardware Subject: Re: Romable code with Microsoft C? Message-ID: Date: 23 Feb 91 21:05:30 GMT References: <1991Feb22.155750.1404@wuphys.wustl.edu> Sender: bbs@bluemoon.uucp (BBS Login) Organization: Blue Moon BBS ((614) 868-9980/2/4) Lines: 14 marty@wuphys.wustl.edu (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? There was an article in a recent Dr. Dobb's Journal. Basically, what you did was create and debug the program with MSC, then when you were ready to ROM the code, you put the EXE file through what amounted to a loader that resolved DOS fixups to the place you wanted to ROM the code at, and save the binary image. "Recent" is within two years-- they do tend to pile up.