Jump to content
13 posts in this topic

Recommended Posts

Lots of Dual-booters out there are complaining about the time while switching between Mac and Windows, because OS X assumes that the hardware clock is set to UTC but Windows assumes it to be local time. Unfortunately there wasn't an option in OS X to set the hardware clock to local time like Linux.

 

Me, like some of those people, prefer to 'fix' this problem on the Windows side rather than the OS X side, by adding 'RealTimeIsUniversal' in the registry. However this doesn't solve the problem because Windows will still reset itself to the hardware clock, which is already set to UTC.

 

What can be done, is to run 'w32tm /resync' a couple times so that the time will be constantly synchronized. I added it to Task Scheduler so to automate it every 10 minutes.

 

While I am not going to show it step by step on how to accomplish this, I am sure some other people will be happy to do so. I am just sharing the idea.

 

cheers.. =)

Link to comment
https://www.insanelymac.com/forum/topic/99752-ultimate-fix-for-the-time-issue/
Share on other sites

Why don't you just set the right time in Windows and uncheck the "Set date & time automatically" in Mac then they will always be in sync!

Once you start using Mac more of the time, you can do the reverse!

 

 

SticMAN

Why don't you just set the right time in Windows and uncheck the "Set date & time automatically" in Mac then they will always be in sync!

Once you start using Mac more of the time, you can do the reverse!

SticMAN

 

Because we want it to be in sync both in windows and osx. Also it is better to have the computer on UTC time and just let the OS offset to the correct timezone. It is how unix is designed to run, so if you don't you break some network/posix implementations. Of course it is not interesting if you're not using stuff like kerberos or other tools which use timing.

If I don't prefer to fix it from the Windows side, what can I do in OS X then? Some sort of terminal/plist fix?

I ask only becuase I primarily use OS X, while the rest of the family mainly uses Vista. Plus, there has to be a better way to achieve the same thing in windows.

 

Wouldn't syncing both OS's to the internet achieve the same thing?

If I don't prefer to fix it from the Windows side, what can I do in OS X then? Some sort of terminal/plist fix?

I ask only becuase I primarily use OS X, while the rest of the family mainly uses Vista. Plus, there has to be a better way to achieve the same thing in windows.

 

Wouldn't syncing both OS's to the internet achieve the same thing?

 

This fix is the same thing.

 

When vista syncs (depending if it is in a domain or standalone) it is first attempting to sync to a internet ntp/ntp/domain server, and then to the bios. If it is not in a domain this sync happens like once in a week. When you set RealTimeIsUniversal the pc clock is in UTC. (which is an implementation from nt4, which havent been bugfixed, i.e. after a sleep or screensaver and other it will read the time believing it is not in UTC but in local timezone)

I just set my timezone to some crazy zone where the time happens to be correct when compared to Windows.. problem solved.

I don't really think this solves the problem, as some parts of the world have Daylight Savings Time, starting from different times.

 

If you are not from a place with Daylight Savings, you are ok with that solution.

But it will!

 

If one is set to sync and the other just uses the onboard clock in the bios they should at all times be not more than 2 minutes apart! Unless there is something REALLY wrong with your BIOS clock!

 

SticMAN

 

 

Because we want it to be in sync both in windows and osx. Also it is better to have the computer on UTC time and just let the OS offset to the correct timezone. It is how unix is designed to run, so if you don't you break some network/posix implementations. Of course it is not interesting if you're not using stuff like kerberos or other tools which use timing.
But it will!

 

If one is set to sync and the other just uses the onboard clock in the bios they should at all times be not more than 2 minutes apart! Unless there is something REALLY wrong with your BIOS clock!

 

SticMAN

 

I don't know where you get two minutes from, but that is way too much. Two seconds as well. Anyway, I will not force you to use my option, but I prefer my option as I am able to be in sync both when running windows and osx. Taste one word... usage pattern (ok two words)...

×
×
  • Create New...