Xref: utzoo comp.sys.amiga:1452 comp.lang.modula2:561 Path: utzoo!utgpu!water!watmath!clyde!rutgers!umd5!trantor.umd.edu!louie From: louie@trantor.umd.edu (Louis A. Mamakos) Newsgroups: comp.sys.amiga,comp.lang.modula2 Subject: Re: M2Amiga, another bunch of answers Message-ID: <2140@umd5.umd.edu> Date: 16 Dec 87 14:28:20 GMT References: <1221@sugar.UUCP> <2916@cbmvax.UUCP> <1256@sugar.UUCP> Sender: ris@umd5.umd.edu Reply-To: louie@trantor.umd.edu (Louis A. Mamakos) Organization: University of Maryland, College Park Lines: 11 Actually, its fairly trivial to produce the ROMTag structure, etc in a little assembly language stub, and then call your C routine to do the real work. I've done this both in a stand-alone driver that lives in DEVS:, as well as a device which installs itself using MakeLibrary() from inside an application program. Is this real difficult to do in Modula-2? It was pretty easy in Aztec-C. Louis A. Mamakos WA3YMH Internet: louie@TRANTOR.UMD.EDU University of Maryland, Computer Science Center - Systems Programming