I have Boot Camp on my iMac. When I go onto the Windows partition then come back to the Mac, the time is 7 hours behind. For example, if the time is actually 1:39 PM, the clock will show 6:39 AM. This causes Safari to not show websites. Even when I change the clock to the correct time, it still does not work until I close all Applications then open up Safari again. How can I prevent this from happening?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Return from Boot Camp, 7 hours back in time
- Thread starter swb1192
- Start date
- Sort by reaction score
Wish I could help you.
I had this problem for a long time, everytime I came back from windows I would just open 'date & time' and wait about 20 seconds, and it would sync with Apple and set it back to right. I never had the Safari trouble you speak of though.
After I installed Leopard it started resetting the time back to normal after so long, which was nice.
The last couple times I have launched into windows, the windows time has been 6 hours behind, and when I reboot into Leopard the time is right.
I don't know what causes the problem or how to fix it, but you aren't the only one it is happening to.
I had this problem for a long time, everytime I came back from windows I would just open 'date & time' and wait about 20 seconds, and it would sync with Apple and set it back to right. I never had the Safari trouble you speak of though.
After I installed Leopard it started resetting the time back to normal after so long, which was nice.
The last couple times I have launched into windows, the windows time has been 6 hours behind, and when I reboot into Leopard the time is right.
I don't know what causes the problem or how to fix it, but you aren't the only one it is happening to.
If I had to hazard a guess, I would say that OS X stores its internal clock in UTC, and then adjusts by an offset. Most unixlike OSes do this. However Windows sets the internal clock to local time, instead of using an offset. Not certain, but that sounds like the problem to me. There may be an option in one OS or the other to store the time internally the other way, but I haven't tried looking it up.