[ntp:questions] NTP client with ability to write Windows NT system time to hardware clock?
I run Windows 7 Professional IA-32 with RealTimeIsUniversal=1 on brolin-V13, my Dell Vostro V13 laptop. This means brolin-V13’s hardware clock (RTC) runs in UTC, as it should, instead of the local time zone, as Microsoft still uses for the completely illogical default configuration. RealTimeIsUniversal=1 is /finally/ fixed and fully working beginning in Windows Vista SP2 + Windows 7, but there is still a problem: When RealTimeIsUniversal=0, which is also used when the RealTimeIsUniversal key does not exist, Windows 7 writes the Windows NT system time to the hardware clock during the shut down process. When RealTimeIsUniversal=1, though, the Windows NT system time is never written to the hardware clock. Consequently, I have to boot Ubuntu from a USB flash drive (brolin-V13 has no optical disc drive (ODD).), then use ntpdate-debian + hwclock to synchronise the Linux system clock with an NTP server on the Internet, then write the sufficiently-accurate-for-me Linux system time to the hardware clock so Windows 7 will set the Windows NT system clock from the accurate time in the hardware clock. After some time (at least 1 week, not sure.), though, my hardware clock is approximately 2 minutes behind the correct time from an NTP server, but Windows 7 never writes the Windows NT system time to the hardware clock when RealTimeIsUniversal=1, so I have to use my Ubuntu USB flash drive again. I know the proper solution is to get Microsoft to change Windows 7 so it can write the Windows NT system time to the hardware clock even when RealTimeIsUniversal=1, but that has not yet happened. I have at least asked a Microsoft employee about it, though, so they know users (well, at least 1 user. :)) want the feature. I can use w32time to force a synchronisation, but then I have to do that every time I boot Windows 7. brolin-V13 travels with me between home and work, so it is not always running. Maybe this causes the hardware clock to fall behind, but I do not think I can prevent having to shut down and boot brolin-V13 on a daily basis. Since I do not know if Microsoft will ever enable Windows 7 to write the Windows NT system time to the hardware clock when RealTimeIsUniversal=1, the next best solution is probably to write a hwclock.exe application for Windows NT, but I am hoping someone has already implemented this functionality in an application such as an NTP client. Googling “hwclock.exe” returns lots of noise because some malware uses this file name, but I have not found any real hwclock.exe equivalent to hwclock used on Linux. So, is there an NTP client or any other application for Windows NT which can write the Windows NT system time to the hardware clock so I do not have to write hwclock.exe for Windows NT? Thanks for reading, Brolin ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP client with ability to write Windows NT system time to hardware clock?
Piece of feedback below. On 11/12/10 13:07, Brolin Empey wrote: I run Windows 7 Professional IA-32 with RealTimeIsUniversal=1 on brolin-V13, my Dell Vostro V13 laptop. This means brolin-V13’s hardware clock (RTC) runs in UTC, as it should, instead of the local time zone, as Microsoft still uses for the completely illogical default configuration. RealTimeIsUniversal=1 is /finally/ fixed and fully working beginning in Windows Vista SP2 + Windows 7, but there is still a problem: When RealTimeIsUniversal=0, which is also used when the RealTimeIsUniversal key does not exist, Windows 7 writes the Windows NT system time to the hardware clock during the shut down process. When RealTimeIsUniversal=1, though, the Windows NT system time is never written to the hardware clock. Consequently, I have to boot Ubuntu from a USB flash drive (brolin-V13 has no optical disc drive (ODD).), then use ntpdate-debian + hwclock to synchronise the Linux system clock with an NTP server on the Internet, then write the sufficiently-accurate-for-me Linux system time to the hardware clock so Windows 7 will set the Windows NT system clock from the accurate time in the hardware clock. After some time (at least 1 week, not sure.), though, my hardware clock is approximately 2 minutes behind the correct time from an NTP server, but Windows 7 never writes the Windows NT system time to the hardware clock when RealTimeIsUniversal=1, so I have to use my Ubuntu USB flash drive again. I know the proper solution is to get Microsoft to change Windows 7 so it can write the Windows NT system time to the hardware clock even when RealTimeIsUniversal=1, but that has not yet happened. I have at least asked a Microsoft employee about it, though, so they know users (well, at least 1 user. :)) want the feature. I can use w32time to force a synchronisation, but then I have to do that every time I boot Windows 7. brolin-V13 travels with me between home and work, so it is not always running. Maybe this causes the hardware clock to fall behind, but I do not think I can prevent having to shut down and boot brolin-V13 on a daily basis. Since I do not know if Microsoft will ever enable Windows 7 to write the Windows NT system time to the hardware clock when RealTimeIsUniversal=1, the next best solution is probably to write a hwclock.exe application for Windows NT, but I am hoping someone has already implemented this functionality in an application such as an NTP client. Googling “hwclock.exe” returns lots of noise because some malware uses this file name, but I have not found any real hwclock.exe equivalent to hwclock used on Linux. So, is there an NTP client or any other application for Windows NT which can write the Windows NT system time to the hardware clock so I do not have to write hwclock.exe for Windows NT? Thanks for reading, Brolin There's no way I'm going to read all that. If you have a question for us, please can you put it a little more succinctly? Thanks. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP client with ability to write Windows NT system time to hardware clock?
On 2010-12-11, Jan Ceuleers janspam.ceule...@skynet.be wrote: Piece of feedback below. On 11/12/10 13:07, Brolin Empey wrote: I run Windows 7 Professional IA-32 with RealTimeIsUniversal=1 on brolin-V13, my Dell Vostro V13 laptop. This means brolin-V13?s hardware clock (RTC) runs in UTC, as it should, instead of the local time zone, as Microsoft still uses for the completely illogical default configuration. RealTimeIsUniversal=1 is /finally/ fixed and fully working beginning in Windows Vista SP2 + Windows 7, but there is still a problem: When RealTimeIsUniversal=0, which is also used when the RealTimeIsUniversal key does not exist, Windows 7 writes the Windows NT system time to the hardware clock during the shut down process. When RealTimeIsUniversal=1, though, the Windows NT system time is never written to the hardware clock. Consequently, I have to boot Ubuntu from a USB flash drive (brolin-V13 has no optical disc drive (ODD).), then use ntpdate-debian + hwclock to synchronise the Linux system clock with an NTP server on the Internet, then write the sufficiently-accurate-for-me Linux system time to the hardware clock so Windows 7 will set the Windows NT system clock from the accurate time in the hardware clock. After some time (at least 1 week, not sure.), though, my hardware clock is approximately 2 minutes behind the correct time from an NTP server, but Windows 7 never writes the Windows NT system time to the hardware clock when RealTimeIsUniversal=1, so I have to use my Ubuntu USB flash drive again. I know the proper solution is to get Microsoft to change Windows 7 so it can write the Windows NT system time to the hardware clock even when RealTimeIsUniversal=1, but that has not yet happened. I have at least asked a Microsoft employee about it, though, so they know users (well, at least 1 user. :)) want the feature. I can use w32time to force a synchronisation, but then I have to do that every time I boot Windows 7. brolin-V13 travels with me between home and work, so it is not always running. Maybe this causes the hardware clock to fall behind, but I do not think I can prevent having to shut down and boot brolin-V13 on a daily basis. Since I do not know if Microsoft will ever enable Windows 7 to write the Windows NT system time to the hardware clock when RealTimeIsUniversal=1, the next best solution is probably to write a hwclock.exe application for Windows NT, but I am hoping someone has already implemented this functionality in an application such as an NTP client. Googling ?hwclock.exe? returns lots of noise because some malware uses this file name, but I have not found any real hwclock.exe equivalent to hwclock used on Linux. So, is there an NTP client or any other application for Windows NT which can write the Windows NT system time to the hardware clock so I do not have to write hwclock.exe for Windows NT? Thanks for reading, Brolin There's no way I'm going to read all that. If you have a question for us, please can you put it a little more succinctly? Thanks. To summarize as I understand it-- how do you keep the RTC synced to the true time under Windows? (System running ntp so assume that the system time is the true time). ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP client with ability to write Windows NT system time to hardware clock?
unruh wrote: On 2010-12-11, Jan Ceuleers janspam.ceule...@skynet.be wrote: Piece of feedback below. There's no way I'm going to read all that. If you have a question for us, please can you put it a little more succinctly? Thanks. That's not a good policy to encourage. You will get the common Subject: Help; It doesn't work. Fix it. postings common on many support groups. To summarize as I understand it-- how do you keep the RTC synced to the true time under Windows? (System running ntp so assume that the system time is the true time). He wants the RTC to contain UTC, even though Windows isn't in the GMT timezone with DST disabled. Windows normally stores the system wall clock time. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP client with ability to write Windows NT system time to hardware clock?
David Woolley wrote: unruh wrote: On 2010-12-11, Jan Ceuleers janspam.ceule...@skynet.be wrote: Piece of feedback below. There's no way I'm going to read all that. If you have a question for us, please can you put it a little more succinctly? Thanks. Actually, I /did/ write my question succinctly at the end of my post. To summarize as I understand it-- how do you keep the RTC synced to the true time under Windows? (System running ntp so assume that the system time is the true time). He wants the RTC to contain UTC, even though Windows isn't in the GMT timezone with DST disabled. Windows normally stores the system wall clock time. My RTC already runs in UTC, but my RTC is approximately 2 minutes behind because I have no way of writing the Windows NT system time to the hardware clock (RTC) after using an NTP client to synchronise the Windows NT system time. On Ubuntu, I use ntpdate-debian + hwclock, but I cannot find a real hwclock for Windows NT, only malware which uses the name hwclock.exe as a disguise. I need an hwclock.exe application for Windows NT so I can run “hwclock --utc --systohc” like on Ubuntu. I am asking in this group because I thought someone may know of an NTP client for Windows NT with this functionality, now that Microsoft has finally fully fixed support for RealTimeIsUniversal=1 beginning in Windows Vista SP2 + Windows 7. My original post (and this reply too) make perfect sense to me, but I suspect my readers did not have all of the required background knowledge. If you are not already familiar with Windows NT’s RealTimeIsUniversal registry key, please read http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html. If you are not already familiar with the hwclock command from the util-linux(-ng) package, please read http://manpages.ubuntu.com/manpages/lucid/man8/hwclock.8.html. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP client with ability to write Windows NT system time to hardware clock?
Brolin Empey bro...@brolin.be wrote in message news:nssmo.1329$317.1...@newsfe20.iad... [] My RTC already runs in UTC, but my RTC is approximately 2 minutes behind because I have no way of writing the Windows NT system time to the hardware clock (RTC) after using an NTP client to synchronise the Windows NT system time. On Ubuntu, I use ntpdate-debian + hwclock, but I cannot find a real hwclock for Windows NT, only malware which uses the name hwclock.exe as a disguise. I need an hwclock.exe application for Windows NT so I can run “hwclock --utc --systohc” like on Ubuntu. I am asking in this group because I thought someone may know of an NTP client for Windows NT with this functionality, now that Microsoft has finally fully fixed support for RealTimeIsUniversal=1 beginning in Windows Vista SP2 + Windows 7. Brolin, If it helps, here is rather old code for DOS for reading the RTC. I'm not sure how you would map the INT 26 (hex 1A) to Windows. You may also need to give the program port mapping capabilities. Cheers, David function from_bcd (bcd: byte): word; begin from_bcd := 10 * ((bcd and $F0) shr 4) + (bcd and $0F); end; procedure get_rtc_time (var h, m, s: word); var r: Registers; begin with r do begin ah := $02; Intr ($1A, r); h := from_bcd (ch); m := from_bcd (cl); s := from_bcd (dh); end; end; procedure get_rtc_date (var y, m, d: word); var r: Registers; begin with r do begin ah := $04; Intr ($1A, r); y := 100*from_bcd (ch) + from_bcd (cl); m := from_bcd (dh); d := from_bcd (dl); end; end; ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
