Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uwvax!astroatc!nicmad!madnix!jason From: jason@madnix.UUCP (Jason Blochowiak) Newsgroups: comp.sys.apple Subject: Re: HyperC Message-ID: <1109@madnix.UUCP> Date: 14 Feb 90 00:27:38 GMT References: <1361@crash.cts.com> <1990Feb4.102221.23801@ux1.cso.uiuc.edu> <90039.215754ART100@PSUVM.BITNET> <90040.003515BRL102@PSUVM.BITNET> Reply-To: jason@madnix.UUCP (Jason Blochowiak) Organization: ARP Software, Madison, WI Lines: 40 In article <90040.003515BRL102@PSUVM.BITNET> BRL102@psuvm.psu.edu (Ben Liblit) writes: >In article <90039.215754ART100@PSUVM.BITNET>, Andy Tefft >says: >> [Said something about mksys not changing a Hyper C executable into a >> working SYS file] >Creating a system file is much more complex than creating something to run, >say, in the shell or under BASIC.SYSTEM. There are atrocious, though necessary >protocols that must be followed. Atrocious? Last time I looked (about 10 seconds ago), you just have to locate the program at $2000 (but you can easily prepend something to move it up or down), and then make a QUIT call. Granted, making a quit call from a high-level language isn't the easiest thing in the world, but I don't think they called it the MLI (Machine Language Interface) for nothing. Of course, if you want to start providing extra features to the user, you have to do some extra coding. This doesn't seem particularly bizarre to me. >It would be *nice* if Hyper C would take care of all of these formalities for >you, but it doesn't look like that's the case. Want to write a system file? >Grab yourself a copy of the _PTRM_ and start coding. Do what you can in C, but >realize that you're going to have to do the nitty gritty in assembly and link >it in. Btw, the appropriate info is on page 86. The nitty gritty stuff will almost certainly be no longer than 30 lines (this would include moving the program around in memory and the quit call). It wouldn't even be necessary to link the stuff in - it could be written with a different assembler, and you'd just have to write a program to stick your start-up code and the program in question together. > Ben Liblit > BRL102 @ psuvm.bitnet -- BRL102 @ psuvm.psu.edu -- Jason Blochowiak - jason@madnix.UUCP or, try: astroatc!nicmad!madnix!jason@spool.cs.wisc.edu "Education, like neurosis, begins at home." - Milton R. Saperstein