06 December 2009, 15:22 | #1 |
Quite the odd one
|
Minor inconvenience (setting clock)
I removed the battery from my A2000 some time ago, and never bothered replacing it. Instead, I'm setting the time using time servers at bootup. However, it makes my "uptime" to go bonkers, unless I make a warm reboot once the time is set. For some reason, it uses the old value - which means that value must be read and stored somewhere during bootup, and I don't know where to look. This is an annoyance, that I really would like to get rid of (and I do set the time BEFORE I run - in this case Xopa). Any ideas, anyone?
|
06 December 2009, 20:00 | #2 |
The 1 who ribbits
|
time of last file crated by anychance
|
07 December 2009, 00:37 | #3 |
Quite the odd one
|
Hopefully not. And I don't think it is either, given uptime-values Xopa sets after a cold reboot. Could be worth a closer look just the same though, given I have no other options at the moment.
Edit: Nope. The time is approximately 9.5 years off. Which leaves us around the year of 2000. A clue of sorts. To what, I have no idea. Last edited by Iznougoud; 07 December 2009 at 04:09. Reason: Additional info |
07 December 2009, 19:53 | #4 |
Registered User
Join Date: Mar 2004
Location: finland
Posts: 1,843
|
Look at if it's the date the HD has been prepped (date of disk.info or something)
|
07 December 2009, 21:39 | #5 |
-
Join Date: Jul 2003
Location: Helsinki / Finland
Age: 43
Posts: 9,911
|
The boot disk's format time is indeed the default time if the machine's clock doesn't work.
|
09 December 2009, 00:48 | #6 |
Quite the odd one
|
The plot thickens. The boot-HDD underwent a change of filesystem and a reformat no more than a couple of days ago, so I doubt it can be held responsible. Unless there is some other data on it, originating from factory settings.
|
09 December 2009, 09:59 | #7 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,026
|
The file system is responsible to set the system time. It depends on the file system and on the order in which partitions are mounted which time is used. Usually it's the last changed time of the first FFS partition which is mounted. The SetClock command in Startup-Sequence then reads the hardware clock and sets the system time accordingly. If the hardware clock has lost its time, the system date and time is set to 01-jan-1978 00:00. If no hardware clock is found the system date remains unchanged.
|
09 December 2009, 11:27 | #8 |
Junior Member
Join Date: Sep 2001
Location: No(R)Way
Age: 42
Posts: 3,222
|
If you have it connected to the internet you can update automaticly after every boot..
|
09 December 2009, 16:25 | #9 | |
Quite the odd one
|
Quote:
Then again, there may be no solution to this other than not powering off, or getting a new battery, but I have to admit; I'm slightly annoyed not knowing what's happening here |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
What's the recent minor update to ClassicWB? | MethodGit | project.ClassicWB | 1 | 04 April 2010 13:57 |
Minor request (1 minute change). | Jim | project.EAB | 1 | 11 December 2004 23:43 |
A minor error in the database... | Shoonay | HOL data problems | 2 | 20 August 2004 14:15 |
Minor Bug | Skumball | support.WinUAE | 0 | 29 February 2004 09:56 |
WinUAE minor problems with XP | icreadence | support.WinUAE | 0 | 22 November 2002 05:05 |
|
|