Path: utzoo!attcan!uunet!husc6!m2c!wpi!greyelf From: greyelf@wpi.wpi.edu (Michael J Pender) Newsgroups: comp.sys.apple Subject: Re: HyperC Message-ID: <8272@wpi.wpi.edu> Date: 14 Feb 90 17:28:18 GMT References: <1361@crash.cts.com> <1990Feb4.102221.23801@ux1.cso.uiuc.edu> <90039.215754ART100@PSUVM.BITNET> <90040.003515BRL102@PSUVM.BITNET> Reply-To: greyelf@wpi.wpi.edu (Michael J Pender) Organization: Worcester Polytechnic Institute, Worcester ,MA Lines: 27 In article <90040.003515BRL102@PSUVM.BITNET> BRL102@psuvm.psu.edu (Ben Liblit) writes: >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. (Look in the _ProDOS_Technical_Reference_ >_Manual_ for details.) > >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. It not that big a deal, a system file has to load in and be prepared to run at $2000, Hyperc creates it object files to run there anyways... It have to install its system version number in the global page. You write one value to one place. Big Deal. It has to be able to execute an MLI quit call when done. Once again, big deal. Thats about ten bytes you have to program. The big problem we all run into is how do we save the image of the file along with its runtime libraries... In other words, how do we create a file, whether it be binary or system that can run outside of the HyperC environment?