Make a new, bootable copy of your 1616 User disk, following the directions in your Users Manual. To ensure sufficient space, delete any obviously unwanted files you notice on the copy.

Copy the contents of your HiTech C distribution disk to the new disk, keeping the subdirectories the same as on the HiTech disk.

If you have received any updated C header files or other updates, copy these also to their respective subdirectories on your new disk.

Using edit, alter the xpath and assign commands in your autoexec.shell file in the root directory of your new disk.

Your xpath should include /F0/bin (if it is not already included).

Add the following lines to your autoexec.shell, to recreate the environment used by Tim
Ward when originally running these programs.

assign /hitech /f0/bin
assign /sys /f0/include
assign /temp /rd

This will allow code to be written without regard to where you actually put your files. If you are using a second drive, or a hard disk, simply change the assign to point /hitech to the correct drive. Ctends to use temporary files extensively. If you have sufficientmemory available on your ram disk, use /rd for temporary files. If not, use the current drive and directory, as indicated by the assign /temp .

Make sure you copy the new C preprocessor relcc.xrel from the user disk into the /bin
subdirectory of your new C disk. Note that relccexpects by default to find itsClibrary files on the current drive in the /hitech directory. It also expects to find its include files on the current drive in the /hitech/include directory. Wewill explain what this means later, and there is a detailed discussion of the HiTech C compiler at the end of the tutorial.

If all is correct, you can now compile a C file by typing
relcc -v file.c
The -v flag is to invoke the verbose mode, which produces the maximum information from the compiler.

If you are experimenting, you may prefer to capture any errors encountered in a file, for later study. If so, use
relcc -v file.c } errorfile