On Tue, 21 Feb 2012 22:31:38 -0500, Doug wrote:
> On 02/21/2012 08:36 PM, Don deJuan wrote:
>>>
>>> In windows open regedit go to:
>>> HKLM\SYSTEM\CurrentControlSet\__Control
\TimeZoneInformation
>>> add a DWORD with name of "RealTimeIsUniversal" exactly as
>>>
On 22/02/12 03:54, Don deJuan wrote:
Since you will not keep this in the public list I will forward your
emails to it.
Please don't, we're not interested. If someone mails you privately with
something you find disagreeable please deal with it yourself.
--
To UNSUBSCRIBE, email to debian-use
On Tue, Feb 21, 2012 at 10:03 PM, Don deJuan wrote:
>
> 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
On 02/21/2012 06:24 PM, Paul Johnson wrote:
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.
On Tue, Feb 21, 2
that you
can make if you actually took the time to actually read everything I
stated in my responses.
Original Message ----
Subject: Re: Windows screws up Linux's clock
Date: Tue, 21 Feb 2012 19:45:12 -0800
From: Paul Johnson
To: Don deJuan
Don't let
On 02/21/2012 07:31 PM, Doug wrote:
On 02/21/2012 08:36 PM, Don deJuan wrote:
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 t
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 ins
On 02/21/2012 08:36 PM, Don deJuan wrote:
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
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.
On Tue, Feb 21, 2012 at 5:36 PM, Don deJuan wrote:
>
> Seriousl
On 02/21/2012 05:25 PM, Paul Johnson wrote:
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.
On Tue, Feb 21, 2012 at 4:06 PM, Don deJuan mailto:donjuans...@gmail.com>> wrote:
On 02/21/2012 03:5
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.
On Tue, Feb 21, 2012 at 4:06 PM, Don deJuan wrote:
> On 02/21/2012 03:58 PM, Doug wrote:
>
>> On 2/21/2012 1:00 AM, Don deJuan wrote:
>>
>>> On 02/20
On 02/21/2012 03:58 PM, Doug wrote:
On 2/21/2012 1:00 AM, Don deJuan wrote:
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikip
On 2/21/2012 1:00 AM, Don deJuan wrote:
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every
time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki/Coordinated_Unive
On 2/21/2012 1:26 AM, Don deJuan wrote:
On 02/20/2012 09:55 PM, Joe Pfeiffer wrote:
Hendrik Boom writes:
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 th
On 02/21/2012 10:52 AM, Henrique de Moraes Holschuh wrote:
On Tue, 21 Feb 2012, Tony Baldwin wrote:
On Tue, Feb 21, 2012 at 04:55:14AM +, Hendrik Boom wrote:
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 moo
On 02/21/2012 03:42 AM, Andrei POPESCU wrote:
On Ma, 21 feb 12, 04:55:14, Hendrik Boom wrote:
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
On Tue, 21 Feb 2012, Tony Baldwin wrote:
> On Tue, Feb 21, 2012 at 04:55:14AM +, Hendrik Boom wrote:
> > 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 a
On Tue, Feb 21, 2012 at 04:55:14AM +, Hendrik Boom wrote:
> 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
On Tue, 21 Feb 2012, Henrique de Moraes Holschuh wrote:
> On Tue, 21 Feb 2012, Andrei POPESCU wrote:
> > Windows initially gets the time from the hardware clock, but it may also
> > get the time from the internet (NTP protocol?). Since your hardware
>
> It's SNTP nowadays, I believe. Windows ha
On Mon, Feb 20, 2012 at 8:55 PM, Hendrik Boom wrote:
> 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 id
On Tue, 21 Feb 2012, Andrei POPESCU wrote:
> Windows initially gets the time from the hardware clock, but it may also
> get the time from the internet (NTP protocol?). Since your hardware
It's SNTP nowadays, I believe. Windows has never been big on timekeeping.
> Of course, the registry hack s
On Ma, 21 feb 12, 04:55:14, Hendrik Boom wrote:
> 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
On 21/02/12 05:00, Kousik Maiti wrote:
May be the problem is with your motherboard battery... not OS ...
That only manifests itself when he boots into Windows? No, this is a
well-known problem, it's Windows.
--
Jon Dowland
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On 02/20/2012 09:55 PM, Joe Pfeiffer wrote:
Hendrik Boom writes:
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 ha
On 02/20/2012 09:55 PM, Joe Pfeiffer wrote:
Hendrik Boom writes:
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 ha
Hendrik Boom writes:
> 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
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
I boot to Windows XP (which I
Hendrik Boom wrote:
> I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
> I boot to Windows XP (which I need to do once in a blue moon) Windows
>
May be the problem is with your motherboard battery... not OS ...
On Tue, Feb 21, 2012 at 10:25 AM, Hendrik Boom wrote:
> 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 m
29 matches
Mail list logo
