dinolt@wdl1.UUCP (12/04/87)
Several weeks ago I posted a request for information concerning the
use of the Mark Williams make program inside the GULAM shell.
Many thanks to all those 8 people who responded to my query, some with
several messages. I am now successfully running the Mark Williams
make program from Gulam. I have yet to sort out the time problems
also mentioned in that note. Below I summarize what I have learned.
My first question was how to configure the system so that Gulam would
run the Mark Williams make. The program would start up but then not
compile anything, failing with the error message "No shell".
The problem was fixed as follows:
1.) Remove the SHELL variable from the Gulam environment.
(actually I never setenv it)
2.) Make sure a copy of msh is in one of the directories of the PATH,
3.) I also set the environment style to the default gulam
environment. I don't think this is necessary but it certainly
doesn't hurt.
Several people suggested that I run with a ram disk. I now do this.
I have set up the ram disk to contain the passes of the C compiler and
space for the temporary files.
My ram disk is F: and I have directories F:\bin and F:\tmp. My PATH
environment variable includes F:\bin as well as my ``standard'' places
and my TMP environment variable is F:\tmp. This speeds up
compilations rather dramatically even over using my hard disk.
Several people asked why I use GULAM instead of the supplied MSH shell. The
reasons are as follows:
1.) The GULAM shell looks more like CSH on UNIX that I use at work
than MSH does,
2.) GULAM's filename completeion feature is very useful especially
in finding names of files when you don't remember all the
name,
3.) Gulam conatains a bultin EMACS like editor which comes up
instantly when called, can be suspended and returnted to, and
has most of the features one wants in an EMACs like editor. It
is not as powerful as MicoEmacs 3.? but it is adequate.
4.) The GULAM shell syntax although not completely like CSH seems
more natural to me than the syntax of MSH.
5.) GULAM maintains a hash table of all known commands
(.tos, .ttp, .gem, .g files) findable in the PATH
directories. This makes command starting much quicker than in
MSH which must do a physical search of these directories each
time a command is issued.
MSH has several features that GULAM does not, the most important of
them is the notion of ``pipes'' so occasionaly I do run MSH.
The time problem I have is that MSH does not set the time properly.
My hard disk drive controller has a battery backed up clock which is
used to set at least one of the (possibly 3) system clocks via a program
in my AUTO folder. This is fortunately the clock GULAM uses and also
the one used to set the modify dates on files. MSH, when it starts,
has a completely different idea of the time. I did receive several
suggestions of things to try to ensure that msh found the correct
time, but none of them worked.
There is a listing of a demonstration program in the MWC manual which
references the various CLOCKS on the ST. I have yet to get that
program to operate corretly. After I do, I am sure I will be able set
the clocks properly.
To all who responed thanks for your help. I hope the above is of some
interest to others on the net.
George Dinolt
dinolt@ford-wdl1.arpa, ...!sun!wdl1!dinolt