You are not logged in.
Pages: 1
Hey guys,
Its recommended in the install guide not to set the clock to "localtime", and in dual boot situations, and apply a registry edit hack to the windows installation instead.
However, Microsoft is recommending not set the RealTimeIsUniversal to 1. So, whats the solution if I don't want to compromise any of the OSes? And shouldn't the installation guide at least point out that what you are doing potentially will cause issues for the windows installation?
Why is using localtime a issue? Historically this has been the way to deal with dual boot systems in most other distributions i've been exposed to.
Offline
localtime may not be recommended but its still a valid option and it's what I currently use. I suppose to avoid this issue you could install Arch Linux and Windows to separate hard disks and just use BIOS to switch between them
Offline
I also use HARDWARECLOCK="localtime" in rc.conf. When daylight savings time kicks in (March and November), I boot up Windows XP and it fixes the tint2 (and system) clock in Arch.
It's ugly but at least it's twice a year... Not that big of a deal, IMO.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Is that article just saying that Windows will become unresponsive during the DST change (so 2am 2 days out of the year)? Doesn't make sense to me.
I use the registry hack and haven't had any problems with it, but then again I rarely ever boot into Windows 7.
Offline
I use the registry hack and haven't had any problems with it, but then again I rarely ever boot into Windows 7.
I do as well and I don't either
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Pages: 1