🚀 go-pugleaf

I use this procedure, and it works most of the time :

 1) first, I compiled the source file on the BOOT DISK.  The output is
    hello.asm.
 2) Hello.asm now must be moved to C WORK DISK for assembling.  If you didn't
   do this, you would get the message 'can't remount volume'.
 3) WORK DISK must contain the folder ASM stuff for the assembler to work.
 4) When you run the ASSEMBLER, the output file is hello.rel.
 5) I create a hello.link which looks like the following :

      !Start
       
      hello
      cclib

      $

 6) Now this link file must also be moved to WORK DISK; otherwise it won't work.
 7) Now, I am ready to link.  This is where complication begins. 
    First, you must have a folder containing library REL files such as
    cclib.REL, cv7lib.REL etc., on the WORK DISK.  Then when I LINK the file
    SOMETIMES it works; if it doesn't work the first time, try again.
    If it still does not work, then you need some statement at the top of
    your program like :

         #include <stdio.h>

    depending on which libraries you want to use.  If this is the case, then
    the files HEADERs must also be moved to WORK DISK.

    I spent two nights to compile a small example program DEGREE.C on the disk.
    and came up with this procedure by trial and error.  Obviously this is
    not my idea of user-friendly.  
    Let me know if this works.  Also please post further techniques you might
    receive on the net.  I am also exasperated by the excessive disk swapping
    for such a small program like hello.c ( I own a 128 Mac )
    Thanks.

    I tried mailing this but couldn't.