jwana@pro-harvest.cts.com (John Wana) (01/04/91)
I believe that somebody had this problem with hyper c...it's actually pretty simple to do.. 1) Copy the files C.SYSTEM and OPSYS and your program to whatever disk along with the file prodos of course 2) Now rename your program to SHELL There ya go! I'm sure that there's a way to do it directly... HyperC translates the source into it's own strange assembly code and then assembles that and then links it to the c libraries... If someone could figure out the assembly code (to get it, just go to the cc batch file and then get rid of the line that's something like "rm blah.s" this way it won't erase the source file) and then write the libraries out, it may just work ________________________ __________________________ | ProLine: jwana@pro-harvest | | Internet: jwana@pro-harvest.cts.com | | UUCP: crash!pro-harvest!jwana | | ARPA: crash!pro-harvest!jwana@nosc.mil | |_______________ BITNET: jwana%pro-harvest.cts.com@nosc.mil _________________|
ericmcg@pnet91.cts.com (Eric Mcgillicuddy) (01/07/91)
>I'm sure that there's a way to do it directly... HyperC translates the source >into it's own strange assembly code and then assembles that and then links it >to the c libraries... Almost. Using 'cc', HyerpC compiles the C source to p-code and then interprets it. This makes for very small programs. Using 'ccn' will generate native 6502 (and 65c02 if a lnk flag is set) code. Howeever it does not link in the libraries, it assumes that some of them are present in the opsys file. I/O mostly I believe which is redundant code with the shell active. UUCP: bkj386!pnet91!ericmcg INET: ericmcg@pnet91.cts.com