- This topic has 5 replies, 2 voices, and was last updated Jan 26-9:53 am by psionl0.
-
Posts
-
psionl0
Every time I boot into antiX it resets the internal clock on my PC to the wrong time. If I boot into antiX at 1200 UTC the clock will be reset to 0800 UTC and the task bar displays 1600 AWST (UTC + 8 hrs).
Is there any way I can stop antiX resetting the time or get it to set the time correctly?
BobC
I wonder if you have a Windows machine being used for Linux? Windows sets the clock differently.
When you boot from the flashdrive, on the F4 Miscellaneous options screen you will see the hwclock options that you can set. You could also type that option in at the boot command line so its set when you boot. Mine was a Windows machine in its former life, so I use hwclock=local, otherwise the time gets set for Greenwich England, I think.
Another way to get it set right is to get the system to set the time from the internet. There is a Set Time and Date option on the System tab of the antiX Control Centre which is on the main menu.
BTW: You probably could have used your web browser search to find these answers using a search string like this:
site:antixforum.com set date time to local for windows
The first thread on the list that pops up has the correct answers, even better than mine.
Mine is a dual boot machine but I boot into antiX from a thumb drive and have the have the persistance files set up (and regularly updated).
F4 works but this is not much better than resetting the time after boot up (from the terminal).
I have never been able to get the Set Time and Date options to work properly.
Did you look at the other thread?
If I read it right, you could change your Windows setting to UTC and then it would work right for both?
Another possibility is that if you use persistence, you could change it like it says in the other thread, and it would be saved.
Or if you don’t want to save things, you could just make that change and remaster the USB so it gets saved, and then comes up that way from then on.
It looks like the problem is solved. Perhaps I didn’t have persistence enabled when I originally tried to set the time. So it kept reverting to an incorrect setting. Thank you for your help.
- You must be logged in to reply to this topic.
