🚀 go-pugleaf

I recently, last weekend, broke down and bought a "real C compiler"
for my 1040 ST.  I purchased the Mark Williams compiler since it
seemed to be getting the most use and best reviews on the net.  The
documentation organization takes a little getting used to but all and
in I only have found two problems I haven't been able to deal with.

The first is very strange.  I have a BMS hard disk which includes a
battery backed clock.  As part of my bootup process, I run a program
called setclock (in the auto folder) which sets the system clock to
the "correct" date and time.  The GULAM shell, the file system dates
and other programs all have a realistic notion of the time after boot.
MSH (the shell supplied with MW Compiler) is completely confused about
the time. (MSH thinks the date is in the 21st century on a consistent
basis).  I thought that maybe it was getting its idea of the current
time from the keyboard clock since that survives resets, so I wrote a
program to transfer the system time to the keyboard time.  I ran this
program before I used the MSH date function.  That had no effect.  I
am very confused.  Anyone have any other ideas?  

The second problem involves the MAKE program supplied with the MWC
compiler.  If I run MAKE under MSH everthing works like a champ.
If I run MAKE under the GULAM shell (lattest distribution from
comp.binaries.atari.st, thanks Turner et al) I get the message

Shell not found 

after make prints out the cc command line it is planning to execute. 
When I run the MAKE program with the -d option, all the all the
environment variables seem to be set correctly, including 
SHELL=d:\bin\msh.prg

The CC command itself works fine under GULAM.  A version of the public
domain program MAKE which was on the net a few months ago also works
fine under both SHELLs.  The other bit of evidence I have is that when
I run XPROLOG, posted in comp.binaries.atari.st I found exactly the
same symptoms.  XPROLOG could not find the SHELL when running under
GULAM but could find the SHELL when running under MSH.  

Obviously something is wrong with my environment, but I haven't been
able to figure it out yet.  Anybody have any ideas?

Please send responses to me and I will post if there is sufficient
interest.

Regards,
George Dinolt (dinolt@ford-wdl1.arpa, ...!sun!ford-wdl1!dinolt)