Clock shows wrong time when dual booting Windows and Linux (*nix)

Everybody dual booting Windows and Linux (or any other *nix derivative) surely has different hours when booting back to Windows from Linux.
Well, that's because Windows manages the clock in "local time" instead of UTC which is what most other OSes do (such as Linux).
According to this Lifehack (http://lifehacker.com/5742148/fix-windows-clock-issues-when-dual-booting-with-os-x) there's a workaround in order to force Windows to use UTC. It's a simple registry entry that starts working as soon as you reboot your PC back into Windows.
I'll copy it here for posterity in case LH ever runs into trouble and disappears.
Search for:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Right click anywhere in the right pane and hit "New > DWORD (32-bit) Value".
Name it "RealTimeIsUniversal".
Double click on it and give it a value of "1".
That's it. Just reboot back into Windows and check that (if your clock was out of sync) it should now be perfectly in sync and you can now freely boot between Linux and Windows with no worries.

Comments

Post a Comment

Popular posts from this blog

Headless home server - Setting up Dynamic DNS (FreeDNS) and IPv6 tunnel (HE.net)

Every time I install a PlugComputer I setup a Dynamic DNS service so that I can access it's shell and apps/services from the Internet easily. My preferred Dynamic DNS service is FreeDNS which is very easy to install and setup. Plus, it's working on FreeBSD servers :-P Setting up an account at FreeDNS is fairly simple and it is also simple to setup a subdomain in the form of an A NAME with them. A subdomain is basically something that looks like aname.domain.com . Whatever! So after setting up your A NAME, you need to configure the headless server so that it frequently checks your public IP address. If it has changed from the last time it checked, it then has to register the new public IP address with your A NAME. Most Dynamic DNS services make this easy for us in the form of a URL that we can visit. And since the headless server doesn't run a proper web browser we can use WGET. Frequent checks are configured in the form of a script that is run every, say, 5 minutes. ...
Read more

[Howto] USB sniffing

SniffUSB tool: http://www.pcausa.com/Utilities/UsbSnoop/ Important blog article by crope: http://blog.palosaari.fi/2013/07/generating-rtl2832u-driver-code.html IRC log with crope and mchehab about USB sniffing: [11:06am] crope_: mchehab: ping. I have one RTL2830 driver 3.12 regression. I suspect it is coming from I2C changes, but problem is here that I2C subsystem maintainer has not answered to mails.... [11:07am] crope_: it is that https://patchwork.kernel.org/patch/3079491/ [11:07am] crope_: maybe it could be still safe to marge that patch even I am not sure why it is needed [11:16am] dddtest_e9d3d joined the chat room. [11:24am] mchehab: crope_: hmm... khali is on this channel [11:27am] mchehab: if just re-adding "priv->tuner_i2c_adapter.dev.parent = &i2c->dev;" is enough to fix it, go for it [11:37am] crope_: mchehab: I2C maitainer *just* replied [11:37am] crope_: and he says there should be parent, but it is unclear why it has not been crashed earli...
Read more

Headless home server - Boot via GPT/EFI UUID

My Headless home server (Seagate Dockstar) doesn't have a standard boot manager. It simply boots a uBoot image, either from it's NAND or from an external HDD. All this is set up in it's BIOS. Unfortunately it doesn't have a iLO/DRAC/SIMC/IPMI so that I can control the BIOS over a network connection. Anyway, this amazingly cheap/"low power" device comes with a crippled OS and I like ArchLinux ARM a lot better. Since ALARM (short for ArchLinux ARM) doesn't fit in the small NAND I have to setup the BIOS to point it to an external USB device. But there's a downside to this. Since the PlugPC has 4 USB ports and since the HDD's don't always take the same amount of time handshaking with the BIOS on boot-up, what happens is that sometimes disk A is sda and disk B is sdb but some other times disk A is sdb and disk B is sda. Rather confusing...for us and for the small server too. And worst of all, when the change happens the device won't boot u...
Read more