🚀 go-pugleaf

rjk752@uxf.cso.uiuc.edu writes:


>	I am a registered MWC purchaser also, and I recieved no notification.
>I have heard *rumors only* that there may even be an ANSI "C" version on the
>way.  Any confirmation ?
>	As far as apparent bugs.  I typed the line setting the environmental
>variable TIMEZONE for the Chicago area into my profile.  The example given
>is for Chicago, but it didn't work even though my built-in clock was set
>properly and I typed the example in verbatim.  It was off by several hours.
>I even had the year set correctly.  I found that if I ignored TIMEZONE in
>my profile, then it would work properly.
>	I have version 3.0.5

What's going on here is simple ;-) Chicago is 6 hours west of
Greenwich.  I bet it said the time was six hours early??  Try this:
set your hardware clock to Greenwich Mean Time (a good source would be
WWV on 5, 10, or 15 MHz, or CHU @ 7.335 and 14.670 MHz) and set the
TIMEZONE variable correctly.  MWC is attempting to emulate the Un*x
way of setting clocks, in that all timestamps are carried internally
in GMT, and adjusted _for display purposes only_ by the TZ variable.

	Ross