English Amiga Board


Go Back   English Amiga Board > Support > support.Hardware

 
 
Thread Tools
Old 06 December 2009, 15:22   #1
Iznougoud
Quite the odd one
 
Iznougoud's Avatar
 
Join Date: Sep 2007
Location: Sweden
Posts: 180
Send a message via MSN to Iznougoud
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?
Iznougoud is offline  
Old 06 December 2009, 20:00   #2
cosmicfrog
The 1 who ribbits
 
cosmicfrog's Avatar
 
Join Date: Apr 2006
Location: leek, Staffs, UK
Age: 56
Posts: 3,557
Send a message via MSN to cosmicfrog
time of last file crated by anychance
cosmicfrog is offline  
Old 07 December 2009, 00:37   #3
Iznougoud
Quite the odd one
 
Iznougoud's Avatar
 
Join Date: Sep 2007
Location: Sweden
Posts: 180
Send a message via MSN to Iznougoud
Quote:
Originally Posted by cosmicfrog View Post
time of last file crated by anychance
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
Iznougoud is offline  
Old 07 December 2009, 19:53   #4
zipper
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)
zipper is offline  
Old 07 December 2009, 21:39   #5
Jope
-
 
Jope's Avatar
 
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.
Jope is offline  
Old 09 December 2009, 00:48   #6
Iznougoud
Quite the odd one
 
Iznougoud's Avatar
 
Join Date: Sep 2007
Location: Sweden
Posts: 180
Send a message via MSN to Iznougoud
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.
Iznougoud is offline  
Old 09 December 2009, 09:59   #7
thomas
Registered User
 
thomas's Avatar
 
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.
thomas is offline  
Old 09 December 2009, 11:27   #8
kriz
Junior Member
 
kriz's Avatar
 
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..
kriz is offline  
Old 09 December 2009, 16:25   #9
Iznougoud
Quite the odd one
 
Iznougoud's Avatar
 
Join Date: Sep 2007
Location: Sweden
Posts: 180
Send a message via MSN to Iznougoud
Quote:
Originally Posted by thomas View Post
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.
Still, can't be the last change of my only FFS-partition, which was created not one week ago. Nor is it 78-01-01. And quite frankly, it doesn't matter all that much in my particular case. Question is, how do I make Xopa - or any other uptime-utility - read the correct time after a cold reboot? MiamiDX sets the time via an AREXX-script. Using time servers. And is supposedly started before Xopa. So where does Xopa get it's information on uptime?!

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
Iznougoud is offline  
 


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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 17:52.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.08067 seconds with 13 queries