Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!osupyr.mast.ohio-state.edu!vkr
From: vkr@osupyr.mast.ohio-state.edu (Vidhyanath K. Rao)
Newsgroups: comp.sys.amiga
Subject: Re: Internal Clock Question.
Message-ID: <1259@osupyr.mast.ohio-state.edu>
Date: 30 Mar 89 19:26:26 GMT
References: <8903291457.AA06725@jade.berkeley.edu> <430@antares.UUCP>
Reply-To: vkr@osupyr.mast.ohio-state.edu (Vidhyanath K. Rao)
Organization: Dept of Math, Ohio St U at Newark, Newark, OH 43055
Lines: 15

In article <430@antares.UUCP> jms@antares.UUCP (Joe Smith) writes:
>When AmigaDOS boots up, it gets the date/time from the most recently modified
>file on the boot disk.  Since the .info file and the directory creation date
>are always being updated, the time will be set to the time when you powered
>down.  Therefore you cannot assume that the battery is not dead in your case.

Yes. But, there must be a program that reads the real time clock and sets
up the DOS internals. In the case of the CBM supplied clock for 500, the
program is called `setclock'. My startup-sequence contains a line
	setclock >NIL: opt load
Barring a few occassions, I have not had any trouble. (knock on wood :-)
having the right date and time set up when the boot-up process ends.
-- 
It is the man, not the method, that               Nath
solves the problem.                     vkr@osupyr.mast.ohio-state.edu
	-Poincare.                             (614)-366-9341