Re: New cam

"BoyPete" <petcrow@xxxxxxxxxxx> wrote in message
news:3v427hF1498ikU1@xxxxxxxxxxxxxxxxx
> wally wrote:
>> Bought a new camera today, a Fuji FinePix S5600.
>> Seems to be quite good so far, when I lean to drive it properly
>> I'll put some samples on my site.
>>
>> A problem had just come up, I have just installed a new HDD
<snip>
> Mefinks Wally's clock is screwy? :)

LOL!
Yep - he's just done a Re-Install of windoze & fallen into the classic
Pitfall/Gotcha of not Setting the *TimeZone* right!...

Many people never bother to change the Time Zone at the pointy in the
Installation where it asks you to change the Time Zone.

<quote from the Headers of his Post>
Date: Tue, 29 Nov 2005 21:54:58 -0800
<quote>

His *Clock* is Set right - it's just the Time Zone that is wrong -
It's set to the windoze Default of GMT - 8 Hours (Pacific Time)

So that means that the Time (on his Clock) will show up OK on his PC,
(so he won't realise that the Settings are wrong), but that when he
Sends any Messages, they have that 8 Hour Offset from GMT in the
"Date: " Header, which means that when any News (or eMail) Client
looks at the Message, it will adjust the Time that is *shown*, to take
account of the different Time Zone & show (what it thinks) is the time
of it in the Local Time Zone, so (here, in the UK) it adds 8 Hours on
(in the winter) & 9 Hours in the Summer (when we are on Daylight Saving
Time BST - though I think that if Pacific time also has Daylight Saving
Time, then *his* PC will put in the Offset from GMT as being 9 Hours in
the summer, so it still shows up the same).

HTH

--
pmj


.

Relevant Pages

  • TIP #173: Internationalisation and Refactoring of the clock Command
    ... The [clock] command provides Tcl's fundamental facilities for computing ... {locale era, locale year, month, day of month}: ... If the given format does not include a time zone, ...
    (comp.lang.tcl)
  • Re: Event ID 13548 ntfrs
    ... Check that the time zone and system clock are correctly set on both ... replicate with its partner computer because the difference in clock ... all the servers in Aus have their correct time ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 13548 ntfrs
    ... zones are set correctly for the servers in UK and Australia (GMT and +10 ... Check that the time zone and system clock are correctly set on both ... replicate with its partner computer because the difference in clock ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 13548 ntfrs
    ... zones are set correctly for the servers in UK and Australia (GMT and +10 ... Check that the time zone and system clock are correctly set on both ... replicate with its partner computer because the difference in clock times ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clock ALWAYS resetting itself 1 hour ahead
    ... roland did some thinking and came up ... > weather station data software and it reported the correct time. ... > moment of checking weather conditions I noticed the clock was exactly ... >> I suspect some software is configured for the wrong time zone. ...
    (microsoft.public.windowsxp.general)