There was a solution provided for 10.5 which was a PKG and worked. For 10.6, people found a trick, something to add in the windows registry. It worked sometimes, but now it doesn't, maybe cause updated to 10.6.4? Anyway i need a solution cause it's really annoying as you can imagine (or know)... Thanks!
9 replies to this topic
#1
Posted 24 July 2010 - 12:12 PM
#2
Posted 24 July 2010 - 04:10 PM
This question comes up often enough that perhaps it should be made sticky.
Some background about the problem:
The computer's real time clock (RTC) doesn't specify the time zone, and the problem between Windows and OS X is because they interpret the RTC differently.
When Windows starts and reads the time from the RTC, it assumes that it is the local time, so it does not need to make any adjustment for time zone. If you change the time zone setting in Windows, it will adjust its time accordingly and then write the new local time to the RTC. When syncing time from the internet, Windows keeps the RTC updated to your local time.
On the other hand, when OS X starts and reads the time from the RTC, it assumes that it is Universal Time Coordinated (UTC), aka GMT. OS X then uses your time zone preference to calculate the local time. If you change the time zone preference in OS X, it calculates a new local time, but it does not have to adjust the RTC. When syncing time from the internet, OS X keeps the RTC updated to UTC.
The two approaches are opposite but equal and each one obviously works as designed, but they will conflict as soon as you try to multi-boot between them.
Linux also stores time the same as OS X so it has the same issue, however multi-booting between Windows and Linux has become common enough that many Linux distributions can be configured to interpret the RTC as local time to stay consistent with Windows. Some distros even ask whether the time is local or UTC during installation. However, OS X doesn't offer a similar compromise.
Windows has a registry setting that will make it read and store UTC the same as Linux and OS X. It seems Microsoft didn't officially support it on past versions of Windows, and there were certain instances where it did not work properly, for example when resuming from sleep or hibernate. But that particular bug is apparently fixed in Vista SP2 and in Windows 7.
In Regedit, go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Create a DWORD named RealTimeIsUniversal and set its value to 1
Boot into OS X and correct the time, then boot back into Windows and it should also have the correct time. You can even change the time zone on one and it won't affect the other.
Some background about the problem:
The computer's real time clock (RTC) doesn't specify the time zone, and the problem between Windows and OS X is because they interpret the RTC differently.
When Windows starts and reads the time from the RTC, it assumes that it is the local time, so it does not need to make any adjustment for time zone. If you change the time zone setting in Windows, it will adjust its time accordingly and then write the new local time to the RTC. When syncing time from the internet, Windows keeps the RTC updated to your local time.
On the other hand, when OS X starts and reads the time from the RTC, it assumes that it is Universal Time Coordinated (UTC), aka GMT. OS X then uses your time zone preference to calculate the local time. If you change the time zone preference in OS X, it calculates a new local time, but it does not have to adjust the RTC. When syncing time from the internet, OS X keeps the RTC updated to UTC.
The two approaches are opposite but equal and each one obviously works as designed, but they will conflict as soon as you try to multi-boot between them.
Linux also stores time the same as OS X so it has the same issue, however multi-booting between Windows and Linux has become common enough that many Linux distributions can be configured to interpret the RTC as local time to stay consistent with Windows. Some distros even ask whether the time is local or UTC during installation. However, OS X doesn't offer a similar compromise.
Windows has a registry setting that will make it read and store UTC the same as Linux and OS X. It seems Microsoft didn't officially support it on past versions of Windows, and there were certain instances where it did not work properly, for example when resuming from sleep or hibernate. But that particular bug is apparently fixed in Vista SP2 and in Windows 7.
In Regedit, go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Create a DWORD named RealTimeIsUniversal and set its value to 1
Boot into OS X and correct the time, then boot back into Windows and it should also have the correct time. You can even change the time zone on one and it won't affect the other.
#3
Posted 25 July 2010 - 01:32 AM
#4
Posted 25 July 2010 - 04:31 AM
Between reboots, check the time in BIOS setup. It should be UTC before and after each operating system. Also make sure you have the correct time zone in both Windows and OS X.
Different HDs won't affect how it works. I use two different HDs for OS X and Windows in my system, Windows has the registry change, and both have the correct time.
Different HDs won't affect how it works. I use two different HDs for OS X and Windows in my system, Windows has the registry change, and both have the correct time.
#5
Posted 24 August 2010 - 03:57 AM
Ok so there's this trick for Win7 but what about XP? The same registry modification would work to, or is there another thing to do?
#6
Posted 24 August 2010 - 05:33 PM
The same registry change should work in Windows XP and Vista, with the caveat that the time will become wrong again when resuming Windows from sleep or hibernate.
#7
Posted 28 August 2010 - 10:01 PM
Do you mean if we go to sleep under Windows, at wake up it will have +2 or -2 hours and then need to fix it manually?
#8
Posted 28 August 2010 - 10:05 PM
A quick way to fix this without messing with Windows is opening the Date and Time preference panel, setting Reykjavik, Iceland as your location and disable automatic time synchronization. Then set the time manually. This is a good solution if you're running XP or Vista.
If you're dual booting OS X and Windows 7 the registry patch is obviously the superior solution.
After applying the registry fix don't adjust the time in your BIOS, it's supposed to be "wrong" because it is now UTC instead of local time.
If you're dual booting OS X and Windows 7 the registry patch is obviously the superior solution.
After applying the registry fix don't adjust the time in your BIOS, it's supposed to be "wrong" because it is now UTC instead of local time.
#9
Posted 30 August 2010 - 07:49 AM
I use NTP Clock sync. Works perfectly sits on the Mac side.
Then use Boot Picker to choose OSx or Windows XP works also with win7
Then use Boot Picker to choose OSx or Windows XP works also with win7
#10
Posted 23 August 2012 - 07:38 PM
just simply use the DualBoot Timefix (local time toggle).
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users



Sign In
Create Account









