🚀 go-pugleaf

Dr John Stockton <jrs@merlyn.demon.co.uk> writes:

> My program, at
> http://www.merlyn.demon.co.uk/programs/clokchek.pas  and  *.exe
> merely checks the present MSDOS date+time against the date+time
> when it was last run, and warns if the change is (adjustably)
> unreasonable.  One can put it in AUTOEXEC.BAT.  It uses one entry
> in C:\ (32 bytes).

hmm.  I have a similar routine, in tPascal, called `sanetime'.  you
pass it the filename (and the maximum tolerance of days since the
last run) on the command-line.  (I don't like extra things on my
c:\, personally).

if it's just after midnight on the same day it was last run (i.e.,
the clock didn't advance the day), it fixes it.  it also checks
for going backwards in time (like the three times I set my clock
to 1995 instead of 1996).

I thought it was part of my uufree package, but I don't know if I
have it up for access anywhere.

usage:

sanetime - do a simple sanity-check on the time

usage: sanetime filename [days]

if the time looks sane (within `days' days (default=2) or so
of the timestamp on the file `filename') it'll update the
timestamp on the file and continue with errorlevel 0.  if
the date is in the past, or way in the future, it will return
with an errorlevel of 2.  any error (such as this one) results
in an errorlevel of 1.  date checking is approximate - the date
and hours are checked, but not the minute

the contents of `filename' may be overwritten - use with a file
that no other procedure or process modifies at all
-- 
Russell_Schulz@locutus.ofB.ORG  Shad 86c