time difference with dual boot

[B612]

Hi, guys.

 

Well, I have a dual boot with MAC OS x86 10.4.5 Native and Windows XP PRO. Everything works fine... but the time! Every time I boot my XP PRO after using MAC OS, I have to re-set the time, which becomes one hour back.

 

I've always had this problem, even when I used to run MAC 10.4.3. So I don't think it's a question of drivers etc. It must be that MAC and Windows communicate differently with the BIOS...

 

Does any of you know a possible solution?

[Janis Jansons]

I'm using 10.4.3 & XP Pro and my clocks differ by 2 hours. I've not also found any solution to this problem..

[phor2zero]

it's easy to fix... just tell mac os x that your time zone is GMT.

[B612]

it's easy to fix... just tell mac os x that your time zone is GMT.

 

Sorry, but I was smart enough to think about this solution. In fact, this would not be a solution, because it would just avoid the problem. Moreover, if I did so, I could not automatically update the time through the web, because it would update to the time of GMT, which is not mine.

[calmesal]

I have searched allmost every forums on the web regarding this topic problem. I have found that this is a kernel issue. The linux kernel(wich OSX build on, BSD) doesnt reset the BIOS clock to local time setting according. In linux, and windows , it is possible to set the time to local, but not in OSX. The choice is eithe UCT or GMT, during restart and shutdown, the system clock will be reset accordinly. This coause the problem on time sync in both OSes.

 

Appologize if I couldnt explane better couse I am not English speaker.

[thrunner]

I'm using 10.4.3 & XP Pro and my clocks differ by 2 hours. I've not also found any solution to this problem..

Create a batch file with the following:

w32tm /resync

exit

 

Assuming you have network and internet, running this on WinXP in the startup folder will sync correct time.timesync.zip

[B612]

Create a batch file with the following:

w32tm /resync

exit

 

Assuming you have network and internet, running this on WinXP in the startup folder will sync correct time.timesync.zip

 

Thank you very much. I've solved this problem easily and fastly!

[errandwolfe]

I have searched allmost every forums on the web regarding this topic problem. I have found that this is a kernel issue. The linux kernel(wich OSX build on, BSD) doesnt reset the BIOS clock to local time setting according. In linux, and windows , it is possible to set the time to local, but not in OSX. The choice is eithe UCT or GMT, during restart and shutdown, the system clock will be reset accordinly. This coause the problem on time sync in both OSes.

 

Appologize if I couldnt explane better couse I am not English speaker.

Thanks, sometimes an explination to a problem is more satisfying then a solution. Back when I dual booted, that always bothered me a bit, but usually stayed in either Windows or OS X long enough not to be bothered by restetting the clock on reboot. Always drove me nuts trying to figure out WHY it would do that. The time gain/loss was always too even to be a clock timing issue.

[skn]

Another solution would be to tell Windows the clock runs in Universal Time by creating and setting the following (undocumented) registry entry to "1":

 

HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal

 

For further info refer to the following link:

 

http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html

[kikos]

Another solution would be to tell Windows the clock runs in Universal Time by creating and setting the following (undocumented) registry entry to "1":

 

HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal

 

For further info refer to the following link:

 

http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html

 

 

From that linked site:

 

"I got a reply from someone in Microsoft's Base Kernel Team who got interested in RealTimeIsUniversal and they had a look at the relevant parts of the NT kernel source code. The RealTimeIsUniversal flag is there (a leftover from the days when NT still ran on RISC machines with UTC RTCs), but its implementation seems now incomplete and it is currently not covered by Microsoft's documentation and regression test suite, therefore using it is not recommended at this time. A couple of potential RealTimeIsUniversal bugs have been identified over the past few days, there might be more."

[domino]

The only problem with changing Mac to GMT is when I receive emails, the time is offset to what ever you set your local time and the differece to GMT. Still haven't found a way around that. It's a {censored} when you receive current mail dated 8hrs ago.

[B612]

Believe me, guys, the solution is the one by thrunner!

It's a bit obvious, but it works well.

 

Create a batch file with the following:

w32tm /resync

exit

 

Assuming you have network and internet, running this on WinXP in the startup folder will sync correct time. timesync.zip ( 141bytes )

[belgrano]

sorry if this is a stupid question but where is the startup folder? is it just C: ?

Put 'timesync.bat' wherever you like (let's say C:), then create a shortcut for it and place it in

C:\Documents and Settings\YOUR_USER_NAME\Start Menu\Programs\Startup

If you have more than 1 user on windows, place the shortcut in

C:\Documents and Settings\All Users\Start Menu\Programs\Startup

That is if you're running WinXP...

Make sure you have 'show hidden files and folders' enabled in Folder Options.

[mergedallhere]

what should i do if i have no network and internet?

[belgrano]

Set the correct time in Win then just uncheck 'Set date & time automatically' (in OS X) and set the Time Zone so it will match the real time.

[caladan1810]

Create a batch file with the following:

w32tm /resync

exit

 

Assuming you have network and internet, running this on WinXP in the startup folder will

sync correct time.timesync.zip

 

one slight problem. I get the following response:

w32tm /resync

Sending resync command to local computer...

The computer did not resync because no time data was available.

 

I looked at the syntax of w32tm and noticed I could enter the computer name and have a

no wait state something like this:

w32tm /resync /computer:[computername] /nowait

 

once I had entered the /computer:computername switch and the /nowait switch

my clock did a resync with no problems. for some strange reason it did not want to

do a sync with just w32tm /resync.

 

just something you may want to be aware of .

[Tom H]

There actually is an ugly, more "Windowsy" thing you can do: edit your Windows registry with Start->Run regedit.exe

 

This has been referenced before. You need a little registry editing jargon: "HKLM" is displayed as "HKEY_LOCAL_MACHINE", once you navigate to (and select) TimeZoneInformation (in the left column), go to the edit menu and click New->DWORD. Edit the name to "RealTimeIsUniversal" and double-click it and set the numeric value to 1.

 

Oh, strongly recommended before doing that is navigating the Start->Help and Support->System Restore menu and creating a new "Restore Point", this will allow you to undo any mistakes editing the infamous Windows registry.

 

Unfortunately, this only fixes the Windows kernel. On non-XP Home systems you should also divine Start->Programs->System Administration->Computer Management->Services and "Stop" and "Disable" the "Windows Time" service. (I'm not sure how to on non-media center, non-pro versions - but I assume there's a way).

 

All of this will let the CMOS RTC remain on UTC, and Windows time to be displayed correctly except after going to sleep and, perhaps, and after DST / standard time changes. The sleep problem is an issue, but it's a damn Mac! Why put it into Windows sleep!

[Vas]

Hi,

 

had same problem and all i had done is

 

1. enter bios & set time and date to current.

2. boot into mac, oh no time wrong (don't stress)

3. open time and date and select location

4. now don't use your local location, go through it and select one which changes the time and date to correct date & time without change the time manualy. might be on ther side of world but hey worked for me.

5. reboot into windows and notice will say your local time and location correctly

 

(just make sure the dates are the same as you have am & pm around world at same time. you don't want windows saying am and mac saying pc) lol

 

the only thing is that time zone location in mac wont be your real location.

 

i live in australia nsw sydney set current time & date in bios then reboot into mac

and set time zone location to "Ponta Delgada - Portugal"

 

all time and dates work fine & are all identical like i said except mac time zone.

 

let me know if it works for you.

 

Vas

[cbmkgd]

@vas: I posted a similar solution but in the french forum about a month ago, and can confirm it works.

When 'daylight saving' time shift will occur, we'll have to let only one be the master though (true also for dual booting any other os).

[kakayo]

I've done the batch file solution, but at startup it loads befores internet wifi lan connection starts up and therefore doesn't sync, if I do it after then it works fine. Any one know how I can delay the running of the batch file automatically at start up.

[belgrano]

kakayo, this is your lucky day - Delay Run

[helob]

Another solution is to use a third freeware program called "EMSA Time Synchronizer". You can config it to run at startup and/or update at certain frequencies/intervals.

It works well for me. Give it a try and share your results here.

Thanks

[Mebster]

I download your attachment and put it into the startup folder. Everytime turn on computer, the batch file works automatic, but the problem is still NOT solved!!!

Maybe I missed some thing? Or we should find another ways?

yerp.. same problem here.. hoping for another solution!

 

thanks in advance.

I used to get the same issue and then I started using my ethernet modem which would be on almost all the time (as opposed to the USB modem). This I later noticed solved the problem, although it did it without me actually knowing what I was doing.

 

The explanation I have for this is simple. When the batch file loads up, it attempts to synchronise your system speed with the internet time. If you use a USB modem you need to manually log in and so isn't instant and therefore the batch file is unable to synchronise the system time. When you use an ethernet modem which is always on, it's always connected to the internet, even when your pc is off. So when you switch your pc on it's able to sync at once.

 

So to get around the problem, get an ethernet modem or an ethernet router.

 

Another option may be to delay the loading of the batch file. Use Delay Run. Edit the delayrun.ini file to something like this

30
C:\XP-Mac Time Sync\timesync.bat

Here the 30 is the delay time. Change this to however long you need to get on the internet too. 30 seconds should be enough.

My batch file is on a folder in "C:\XP-Mac Time Sync\" and I’ve put the delayrun folder in the same folder.

Remember now to put a shortcut of the DelayRun.exe program in Startup and make sure to remove the timesync.bat shortcut from there so that it doesn't load twice.

 

Hope this helps clear the issue.

 

- AcePlayer

timesync.zip

delayrun.zip

[cbmkgd]

Some have reported this too.

 

Check the time zone solution:

http://forum.insanelymac.com/index.php?s=&...st&p=194346

 

You'll have to change this twice a year, depending on whether it's daylight saving period or not; presently it's London (and similar) time zone that gives good solution; when daylight saving time is passed, you get back to "Ponta Delgada" a bit westward.

 

/edit: check also this following thread, especially posts #4 and #5 for a comment and another solution.

Edited February 25, 2007 by cbmkgd

[offall]

Thanks Cbmkgd,

The post you mentioned is not a "real" solution, basiclly set mac to wrong timeregion to make it "same"

 

In my problem, I set windows that way that it will automatic sync to correct time upon boot

 

but since time is corrected after sync

 

I am surprise why it will still jump back after a few hours without changing or shuting down windows.

 

 

It is strange and I want to know why this behavior happens

Edited February 26, 2007 by offall