I run my machine on UCT, or something like it (timezone +0).  Every  time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
time.  I have no idea where it gets its idea of what the current time is.

What I'd like to know is, how can I keep Windows from messing with my
clock.  I'd really like it to just leave it alone.

-- hendrik

Archive: http://lists.debian.org/jhv83h$v9q$1*******

May be the problem is with your motherboard battery... not OS ...

--
Wishing you the very best of everything, always!!!
Kousik Maiti(কৌশিক মাইতি)
Registered Linux User #474025
Registered Ubuntu User # 28654

It's UTC.  Having the hardare clock in UTC is normal and standard.

   http://en.wikipedia.org/wiki/Coordinated_Universal_Time

The basic problem is that Windows keeps the hardware clock in
localtime but modern systems keep the hardware clock in UTC.  They are
fundamentally incompatible.

You can configure Debian's /etc/default/rcS to keep the hardware clock
in local time too.  (With UTC=no)  But if you only dual boot very
rarely then I wouldn't do it.  I would simply live with Windows having
messed up time.  It should be fine when you boot Debian.

It is fine when you boot Debian, right?  If not then install 'ntp' and
it will be fine.

Windows is just /displaying/ the clock as localtime, not setting the
clock, right?  That is what I see when I dual boot a machine.

By the way...  The date on your email is UTC.  Is that also your local
time zone too?

Bob

In windows open regedit go to:
HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
add a DWORD with name of "RealTimeIsUniversal" exactly as its entered
there and set the value to 1. Now you can have windows time play nice
with any linux distro, no matter if you use localtime or UTC.

Archive:  

Well, if you *didn't* boot into Windows once in a blue moon...  more
seriously, apparently there is a registry key.

http://weblogs.asp.net/dfindley/archive/2006/06/20/Set-hardw[..]

Archive:  

Tis the same info I just posted to the list on this question. though
using 00000001 is no longer considered to be the proper way in regedit.
You just want 1. The way I posted has worked for me since XP and
currently even on 7 and 8.

Archive:  

Oh and do not do the =dword part add in DWORD correctly.

Archive:  

That only manifests itself when he boots into Windows? No, this is a
well-known problem, it's Windows.

--
Jon Dowland

Archive:  

Windows initially gets the time from the hardware clock, but it may also
get the time from the internet (NTP protocol?). Since your hardware
clock is set to UTC and you want to keep it that way I suggest you
either tell Windows your timezone is UTC or disable the time update.

Of course, the registry hack should work as well, but you'll have to
remember to do it on the next re-install ;)

Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-[..]

It's SNTP nowadays, I believe.  Windows has never been big on timekeeping.

More like one should prepare a registry update file to set up some Windows
parameters to be less idiotic, and use it after every install.

Now, maybe we should provide a registry file to fix the Windows hardware
clock to UTC in our install media, and mention it in the install
instructions?

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Archive:  

Set your Windows clock timezone to "Universal Time Coordinated".

Correcting myself: under AD, it is real NTP.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Archive:  

Funny.
I was just translating the part of Raphael's book that addresses this
issue, yesterday.
He recommends disabling UTC in /etc/defauilt/rcS for any dual boot system
with Windows in the book.
The problem, according to Raphael, is that Windows keeps the CMOS locked
to local time (rather than updating from an NTP server), or some such
thing.
(more info on the book:  http://www.debian-handbook.info )

./tony
-- http://www.tonybaldwin.me
all tony, all the time!

Archive:  

It was brought to this thread that this is old information, and you can
instead tell Windows to use the hwclock on UTC through a registry key
change.

Barring any weird windows bugs, this would be a rather superior choice,
but one should test how Windows deals with an UTC hwclock during DST
changes to be sure.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Archive:  

or write a batch file that will do it ;)

Archive:  

Windows themselves recommends the method that i have now posted to this
list twice. That is the correct way. Once you change the registry, Linux
time will NEVER change due to Windows, other methods will still have
windows take control of the system time once you booth back into windows
after fixing time in Linux. Making a batch file makes it easy if you are
one of those that always reinstalls windows. But if you reinstalling
windows a ton then you have other issues to worry about in Windows than
you do time in general.

Archive:  

Please elucidate:  should "=dword" be replaced by "DWORD"  or what is
meant by "add in DWORD correctly"?  I don't want to have to
reinstall XP for some kind of screwup in the registry.
Thanx--doug

Archive:  

I'm confused.  In another post of a few minutes ago, I asked about this
dword (DWORD?) business.
Could you please post the entire string correctly, with whatever dword
or DWORD is supposed to be and 000001 or 1 or whatever
that's supposed to be.

Thank you.    --doug

--doug

Archive:  

For me and from my understanding the "windows" way to solve this is.
1.open regedit
2. go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\
3. Add in "RealTimeIsUniversal"
4. Give it a hex value of "1" -- this is the 'DWORD'
5. save
6. shutdown windows
7. profit ;)

Does this make sense now? If it does not a simple google of regedit
windows time linux gives lots of tutorials as a result. But giving it
the value in regedit makes it so no matter when you log in/boot Windows,
it will no longer mess with the time settings and any Linux OS can now
run as UTC or localtime with Windows no longer making changes to the
time that effect Linux.

HTH

Archive:  

Seems like this could be made easier by mailing the .reg file (or throwing
it in a webspace someplace) with the correct key and value already set.

If it does not a simple google of "regedit windows time linux" gives
lots of tutorials as a result. But giving

follow the step by step guides that are beyond numerous on google? I
have given the procedure to solve this 3 times through this thread. If
you're unfamiliar with regedit, then please read up on regedit. This is
a simple procedure to accomplish in Windows following what I have
already posted each of the 3 times.

Do not mean to sound rude, but I do not have a bigger spoon for feeding,
and am not a regular Debian user anymore, only replying to questions I
can answer in 1 post. I even gave you the exact terms to go do your own
research to verify I am not passing bad info, in the previous response
;). That is how I remember the terms to add in on a new install
(generally takes a minute to search and apply), doing that exact search,
or you could make a batch file to share with everyone else in the
future, if you wish to contribute in that manner.

RTM is always great advice ;)

Archive:  

Sure, you can just tell people to RTFM.  Or you can just post the patch.
The patch is naturally easier and takes substantially less effort to
create and post than being a dick about it on an internationally
distributed mailing list.

In accordance with Juan's instructions somewhere in this thread, I went
to Google
and got slightly more detailed instructions, which I am going to repeat
here, for
those who are as faked out as I was.  (I'm not a Windows expert--I'm not
really
a Linux expert, either, but I'm probably more familiar with PCLINUXOS
than with
XP.  So here it is, from "lifehacker.com/5742148. . . .

START>Type in "regedit.exe" >HKEY_LOCAL_MACHINE\SYSTEM\Current Control
Set\Control\Time Zone Information

Right click anywhere in the right-hand panel, select NEW>DWORD Value
Type in the box (no spaces, no quotes) "RealTimeIsUniversal"> double click,
change value from 0 to 1, select hexadecimal if not already selected.
Close window--you're done.

It's real easy, but you have to actually do it to realize that.

Thank you to Mr. deJuan for finding this fix and passing it on.

--doug

Archive:  

Or behave like you and calling me childish names, or you still in high
school? Fricken read what I posted 3 times oh brilliant one. And IF YOU
wish to contribute a patch to MS for that or to the list then PLEASE do
so. I CHOOSE NOT TO. I spoon fed you 3 times grow up and read, follow
posted instructions that had been repeated AND DO ACTUAL RESEARCH.
Thanks for confirming why I left debian in the dust!

RTM as I stated without the need for swearing, is a valid thing for me
to state if after 3 times you can not grasp a SIMPLE regedit on your own
NOR follow guides online, or even the simple numbered steps I gave you!
Honestly though there is no need for a patch, it takes no time to enter
the 2 strings of info, are you that lazy you can not create your own if
you are so caring of your precious patch? I mean how hard is it really
to do a little work on your end, when you numerously showed you can not
grasp or follow your basic responses to simple questions, nor follow the
recommendation of what to actually search for on google and come to YOUR
own conclusion on the best way to handle YOUR issue!

Archive:  

Well you are more of an expert than Paul Johnson :D LOL

Archive:  

Since you will not keep this in the public list I will forward your
emails to it.

my 'tude' is less damaging to a group, than someone who resorts to
attacks of such an immature nature who can not simply demonstrate they
this and got this error or do not grasp something stated even after I
read this, then OK more info should be given and help. But you refused
to show you were even reading what I stated and wanted some "patch" when
its just as simple for you to actually do it on your own machine, then
for me to write a patch test it then upload it to the list. That would
take WAY more time as I would not just throw out some "patch" nor would
I upload a batch file to the list just to help 1 person who can't follow
a couple simple steps nor show they are even trying what was stated
numerous times.

Also since when is trying to get someone to demonstrate they are
actually trying to help themselves showing an attitude. You disregarding
previous directions and then after numerously repeating them you just
want me to create something for you that really is pointless that you
can make if you actually took the time to actually read everything I
stated in my responses.

My last point to this to feed further into your assumptions, actually no
it would take YOU less time to actually have just followed my steps the
first time then it would have been for me to create something for you
that I did not already have. So you're saying 1 minute of your time is
more than you posting BS back and not just following the steps the first
time and not asking for further help and having to have it repeated
numerous times?  I only continue this banter because I find your
assumptions and responses to be hilarious, already been forwarded around
work. Please keep your witty, brilliant responses coming as to why I was
such the "dick" with this major "tude" as you say.

Archive:  

Dude, chill.

--
Chris

Archive:  

Please don't, we're not interested. If someone mails you privately with
something you find disagreeable please deal with it yourself.

Archive: