Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > aus.computers > #73990 > unrolled thread

Re: Where full incompetence meets rabid hate dogma

Back to article view | Back to aus.computers

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-03 13:55 +1000
    Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-03 18:26 +1000
      Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-04 02:43 +1000
        Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-04 11:52 +1000
          Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-04 12:34 +1000
            Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-04 12:46 +1000
        Re: Where full incompetence meets rabid hate dogma nb <deletethis@invalid.lan> - 2026-06-05 08:06 +1000
          Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-05 08:31 +1000
          Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 11:33 +1000
            Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-05 12:45 +1000
              Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 20:48 +1000
                Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 02:52 +1000
                  Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-06 09:49 +1000
                    Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 10:50 +1000
            Re: Where full incompetence meets rabid hate dogma Axel <none@not.here> - 2026-06-07 21:15 +1000
              Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-08 10:50 +1000
          Re: Where full incompetence meets rabid hate dogma Axel <none@not.here> - 2026-06-07 21:13 +1000
            Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-08 11:05 +1000
              Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-08 13:58 +1000
              Re: Where full incompetence meets rabid hate dogma Axel <none@not.here> - 2026-06-08 15:43 +1000
                Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-08 17:31 +1000
                  Re: Where full incompetence meets rabid hate dogma Axel <none@not.here> - 2026-06-08 20:49 +1000
                Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-08 19:12 +1000
      Re: Where full incompetence meets rabid hate dogma nb <deletethis@invalid.lan> - 2026-06-05 08:03 +1000
        Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 12:09 +1000
          Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-05 13:46 +1000
            Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 20:50 +1000
              Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 02:53 +1000
    Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 11:09 +1000
      Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-05 12:37 +1000
        Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 20:58 +1000
          Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 02:57 +1000
          Re: Where full incompetence meets rabid hate dogma Daniel70 <daniel47@nomail.afraid.org> - 2026-06-06 20:19 +1000
            Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-07 06:38 +1000
              Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-07 08:13 +1000
              Re: Where full incompetence meets rabid hate dogma Axel <none@not.here> - 2026-06-07 21:38 +1000
                Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-08 10:08 +1000
            Re: Where full incompetence meets rabid hate dogma The Newsgroup Devil <Devil@Hell.biz> - 2026-06-07 00:59 +0200
              Re: Where full incompetence meets rabid hate dogma Daniel70 <daniel47@nomail.afraid.org> - 2026-06-08 18:09 +1000
                Re: Where full incompetence meets rabid hate dogma The Newsgroup Devil <Devil@Hell.biz> - 2026-06-09 01:29 +0200
                  Re: Where full incompetence meets rabid hate dogma Daniel70 <daniel47@nomail.afraid.org> - 2026-06-09 18:41 +1000
      Re: Where full incompetence meets rabid hate dogma Daniel70 <daniel47@nomail.afraid.org> - 2026-06-05 17:58 +1000
        Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-05 21:14 +1000
          Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 03:02 +1000
            Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-06 05:58 +1000
              Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 06:55 +1000
                Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-06 09:10 +1000
                  Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-06 09:16 +1000
                    Re: Where full incompetence meets rabid hate dogma Petzl <petzlx@gmail.com> - 2026-06-07 15:36 +1000
                      Re: Where full incompetence meets rabid hate dogma "Rod Speed" <rod.speed.aaa@gmail.com> - 2026-06-07 15:59 +1000
            Re: Where full incompetence meets rabid hate dogma Peter Jason <pj@jostle.com> - 2026-06-06 08:54 +1000
          Re: Where full incompetence meets rabid hate dogma Daniel70 <daniel47@nomail.afraid.org> - 2026-06-06 20:27 +1000

Page 3 of 3 — ← Prev page 1 2 [3]

#74041

On 9/06/2026 9:29 am, The Newsgroup Devil wrote:
> # /This is a reply to pre-filtered & auto edited post/
> # /All quoted inputs by kill-file residents have been expunged/
> 
> Daniel70
>> Ördög
>>
>>>> Now my memory isn't the sharpest so, sometimes, I might forget to 
>>>> turn off the Wi-Fi .... but the Wi-Fi seems to be ON to often!!
>>>
>>> How about getting a timer switch for the power outlet connected to 
>>> your Wi-Fi router, Daniel??? That would solve your problem instantly.
>>>
>> But that would also take out the Landline phone also connected to the 
>> Wi-Fi box. ;-P
> 
> True. That is a clearly the down side of that solution.
> But it also stops instantly those 3-5 seconds long randomly incoming 
> (automated?) calls where no one seems to say anything on the other side 
> of the line waiting for someone verifying that the dialled number is 
> real (fishing-scamming galore). When I retire for the night I don't need 
> such nonsense disturbing my peace whatsoever! And those legit people 
> whom I happy to speak to can surely wait till the next morning!
> (I never go to bed earlier than 11 pm at night and no friends of mine 
> will ever call me later than that.)
> 
Correct. Correct. Correct.

For some reason, my Phone Line socket is in my main bedroom. When I 
first moved here, when the phone rang, it would be a mad dash from the 
lounge to the bedroom .... only to find it was some Robo-dialler trying 
to make contact.

Now, if the phone rings, I just let it ring .... until I hear some Human 
trying to leave a message .... then I might answer it!
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#74005

On 5/06/2026 11:09 am, Petzl wrote:
> On Wed, 03 Jun 2026 13:55:09 +1000, "Rod Speed"
> <rod.speed.aaa@gmail.com> wrote:
>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>> Petzl <petzlx@gmail.com> wrote
>>>> Petzl <petzlx@gmail.com> wrote
>>
>>>>> Set time was switched on but a Windows downgrade turned it off
>>
>>>> It may not of been Microsoft?
>>>> HP updated it's CMOS which may or may not of caused
>>>> "Set Time Zone Automatically"??
>>
>>> That doesn't happen
>>
>>> https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8
>>
> I know for a fact my computer changed correctly without me touching
> the settings last daylight saving time change,  Sunday, 4 October 2026
> at 2:00 AM local standard time, clocks went or were set forward by
> 1 hour to 3:00 AM.

"Sunday, 4 October *2026* at 2:00 AM local standard time, clocks *went* 
or *were set forward* by 1 hour to 3:00 AM." .... well, Petzl, I always 
thought you were a bit 'out there' .... but NEVER realised you were that 
far 'out there'!!

-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#74009

On Fri, 5 Jun 2026 17:58:05 +1000, Daniel70
<daniel47@nomail.afraid.org> wrote:

>On 5/06/2026 11:09 am, Petzl wrote:
>> On Wed, 03 Jun 2026 13:55:09 +1000, "Rod Speed"
>> <rod.speed.aaa@gmail.com> wrote:
>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>> Petzl <petzlx@gmail.com> wrote
>>>>> Petzl <petzlx@gmail.com> wrote
>>>
>>>>>> Set time was switched on but a Windows downgrade turned it off
>>>
>>>>> It may not of been Microsoft?
>>>>> HP updated it's CMOS which may or may not of caused
>>>>> "Set Time Zone Automatically"??
>>>
>>>> That doesn't happen
>>>
>>>> https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8
>>>
>> I know for a fact my computer changed correctly without me touching
>> the settings last daylight saving time change,  Sunday, 4 October 2026
>> at 2:00 AM local standard time, clocks went or were set forward by
>> 1 hour to 3:00 AM.
>
>"Sunday, 4 October *2026* at 2:00 AM local standard time, clocks *went* 
>or *were set forward* by 1 hour to 3:00 AM." .... well, Petzl, I always 
>thought you were a bit 'out there' .... but NEVER realised you were that 
>far 'out there'!!
>
Well it worked  Sunday, October 5, 2025.At 2:00 AM that morning,
clocks were turned forward one hour to 3:00 AM as well
Then
Auto adjusted as it did Sunday, 5 April 2026, when clocks shifted back
an hour from 3:00 am AEDT to 2:00 am AEST
-- 
"To err is human, 
but to really foul things up requires a computer."
 English poet Alexander Pope 1711.

[toc] | [prev] | [next] | [standalone]

#74013

Petzl <petzlx@gmail.com> wrote
> Daniel70 <daniel47@nomail.afraid.org> wrote
>> Petzl wrote
>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>>> Petzl <petzlx@gmail.com> wrote
>>>>>> Petzl <petzlx@gmail.com> wrote

>>>>>>> Set time was switched on but a Windows downgrade turned it off

>>>>>> It may not of been Microsoft?
>>>>>> HP updated it's CMOS which may or may not of caused
>>>>>> "Set Time Zone Automatically"??

>>>>> That doesn't happen

>>>>> https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8

>>> I know for a fact my computer changed correctly without me touching
>>> the settings last daylight saving time change,  Sunday, 4 October 2026
>>> at 2:00 AM local standard time, clocks went or were set forward by
>>> 1 hour to 3:00 AM.

>> "Sunday, 4 October *2026* at 2:00 AM local standard time, clocks *went*
>> or *were set forward* by 1 hour to 3:00 AM." .... well, Petzl, I always
>> thought you were a bit 'out there' .... but NEVER realised you were that
>> far 'out there'!!

> Well it worked  Sunday, October 5, 2025.At 2:00 AM that morning,
> clocks were turned forward one hour to 3:00 AM as well
> Then
> Auto adjusted as it did Sunday, 5 April 2026, when clocks shifted back
> an hour from 3:00 am AEDT to 2:00 am AEST

When whatever is fiddling with your settings fiddled
with that setting and it wasnt Win11 and you are too
fucking stupid to check the system log to see what
did that even when you know when it happened so
you can remove whatever did that from your system

[toc] | [prev] | [next] | [standalone]

#74014

On Sat, 06 Jun 2026 03:02:02 +1000, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:

>Petzl <petzlx@gmail.com> wrote
>> Daniel70 <daniel47@nomail.afraid.org> wrote
>>> Petzl wrote
>>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>>>> Petzl <petzlx@gmail.com> wrote
>>>>>>> Petzl <petzlx@gmail.com> wrote
>
>>>>>>>> Set time was switched on but a Windows downgrade turned it off
>
>>>>>>> It may not of been Microsoft?
>>>>>>> HP updated it's CMOS which may or may not of caused
>>>>>>> "Set Time Zone Automatically"??
>
>>>>>> That doesn't happen
>
>>>>>> https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8
>
>>>> I know for a fact my computer changed correctly without me touching
>>>> the settings last daylight saving time change,  Sunday, 4 October 2026
>>>> at 2:00 AM local standard time, clocks went or were set forward by
>>>> 1 hour to 3:00 AM.
>
>>> "Sunday, 4 October *2026* at 2:00 AM local standard time, clocks *went*
>>> or *were set forward* by 1 hour to 3:00 AM." .... well, Petzl, I always
>>> thought you were a bit 'out there' .... but NEVER realised you were that
>>> far 'out there'!!
>
>> Well it worked  Sunday, October 5, 2025.At 2:00 AM that morning,
>> clocks were turned forward one hour to 3:00 AM as well
>> Then
>> Auto adjusted as it did Sunday, 5 April 2026, when clocks shifted back
>> an hour from 3:00 am AEDT to 2:00 am AEST
>
>When whatever is fiddling with your settings fiddled
>with that setting and it wasnt Win11 and you are too
>fucking stupid to check the system log to see what
>did that even when you know when it happened so
>you can remove whatever did that from your system
>
You picked up my Winll clock not only unchecked 
"Set time zone Automatically" it reverted the time to Summer.
Again thanks for telling me.

The "Set time zone Automatically" has been working for at least 3
previous daylight saving including the latest my HP computer is around
18 months old.

Although Grok claimed my HP CMOS/BIOS being updated the day before
would nor do this, 
<https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8>
it was the exact time my Win11 time reverted to summer. 
"Set time zone Automatically" was clicked off and not by me.
Came right as soon as I turned it back on, as soon as you told me.
Were not going to pander to going through Windows log files which have
told me sweet fuck all in the past.
-- 
"To err is human, 
but to really foul things up requires a computer."
 English poet Alexander Pope 1711.

[toc] | [prev] | [next] | [standalone]

#74015

Petzl <petzlx@gmail.com> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote
>> Petzl <petzlx@gmail.com> wrote
>>> Daniel70 <daniel47@nomail.afraid.org> wrote
>>>> Petzl wrote
>>>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>>>>> Petzl <petzlx@gmail.com> wrote
>>>>>>>> Petzl <petzlx@gmail.com> wrote

>>>>>>>>> Set time was switched on but a Windows downgrade turned it off

>>>>>>>> It may not of been Microsoft?
>>>>>>>> HP updated it's CMOS which may or may not of caused
>>>>>>>> "Set Time Zone Automatically"??

>>>>>>> That doesn't happen

>>>>>>> https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8

>>>>> I know for a fact my computer changed correctly without me touching
>>>>> the settings last daylight saving time change,  Sunday, 4 October  
>>>>> 2026
>>>>> at 2:00 AM local standard time, clocks went or were set forward by
>>>>> 1 hour to 3:00 AM.

>>>> "Sunday, 4 October *2026* at 2:00 AM local standard time, clocks  
>>>> *went*
>>>> or *were set forward* by 1 hour to 3:00 AM." .... well, Petzl, I  
>>>> always
>>>> thought you were a bit 'out there' .... but NEVER realised you were  
>>>> that
>>>> far 'out there'!!

>>> Well it worked  Sunday, October 5, 2025.At 2:00 AM that morning,
>>> clocks were turned forward one hour to 3:00 AM as well
>>> Then   Auto adjusted as it did Sunday, 5 April 2026, when clocks 
>>> shifted back   an hour from 3:00 am AEDT to 2:00 am AEST

>> When whatever is fiddling with your settings fiddled
>> with that setting and it wasnt Win11 and you are too
>> fucking stupid to check the system log to see what
>> did that even when you know when it happened so
>> you can remove whatever did that from your system

> You picked up my Winll clock not only unchecked
> "Set time zone Automatically" it reverted the time to Summer.
> Again thanks for telling me.

> The "Set time zone Automatically" has been working for at least 3
> previous daylight saving including the latest my HP computer is around
> 18 months old.

And now you managed to fuck that up by either
being stupid enough to fuck over your system
or are running something that is doing that

> Although Grok claimed my HP CMOS/BIOS being updated the day before
> would nor do this,
> <https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8>
> it was the exact time my Win11 time reverted to summer.

  As grok told you, the cmos can't change win11 settings like that

> "Set time zone Automatically" was clicked off and not by me.
> Came right as soon as I turned it back on, as soon as you told me.

> Were not going to pander to going through Windows log files which have
> told me sweet fuck all in the past.

More fool you. It will tell you when that
setting was changed and what changed it

[toc] | [prev] | [next] | [standalone]

#74017

On Sat, 06 Jun 2026 06:55:53 +1000, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:

>> The "Set time zone Automatically" has been working for at least 3
>> previous daylight saving including the latest my HP computer is around
>> 18 months old.
>
>And now you managed to fuck that up by either
>being stupid enough to fuck over your system
>or are running something that is doing that
>
Yes it's the spyware called WIN11.
Just found in Galleries all the photos stored in their unasked for
unwanted Galleries (Cloud),
 by deleting them also deleted the originals. 
What happens with self appointed know alls know nothings back Win11.
-- 
"To err is human, 
but to really foul things up requires a computer."
 English poet Alexander Pope 1711.

[toc] | [prev] | [next] | [standalone]

#74018

Petzl <petzlx@gmail.com> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote

>>> The "Set time zone Automatically" has been working for at least 3
>>> previous daylight saving including the latest my HP computer is around
>>> 18 months old.

>> And now you managed to fuck that up by either
>> being stupid enough to fuck over your system
>> or are running something that is doing that

> Yes it's the spyware called WIN11.

How odd that it doesn't happen on my Win11

> Just found in Galleries all the photos stored in their unasked for
unwanted Galleries (Cloud),
>  by deleting them also deleted the originals.

How odd that it doesn't happen on my Win11

[toc] | [prev] | [next] | [standalone]

#74026

On Sat, 06 Jun 2026 09:16:19 +1000, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:
Snip
>
>> Yes it's the spyware called WIN11.
>
>How odd that it doesn't happen on my Win11
>
>> Just found in Galleries all the photos stored in their unasked for
>unwanted Galleries (Cloud),
>>  by deleting them also deleted the originals.
>
>How odd that it doesn't happen on my Win11
>
Your Windows 11 contected to WI-FI or Ethernet Cable?
Just recived a 20 metre Ethernet Cable from TEMU AU$12.69
https://ibb.co/0pZhBShY
Might make WIN11 behave?
-- 
"To err is human, 
but to really foul things up requires a computer."
 English poet Alexander Pope 1711.

[toc] | [prev] | [next] | [standalone]

#74027

Petzl <petzlx@gmail.com> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote:

>>> Yes it's the spyware called WIN11.

>> How odd that it doesn't happen on my Win11

>>> Just found in Galleries all the photos stored in their unasked for
>> unwanted Galleries (Cloud),
>>>  by deleting them also deleted the originals.

>> How odd that it doesn't happen on my Win11

> Your Windows 11 contected to WI-FI or Ethernet Cable?

WiFi

> Just recived a 20 metre Ethernet Cable from TEMU AU$12.69
> https://ibb.co/0pZhBShY
> Might make WIN11 behave?

Mine always behaves fine

[toc] | [prev] | [next] | [standalone]

#74016

>
>When whatever is fiddling with your settings fiddled
>with that setting and it wasnt Win11 and you are too
>fucking stupid to check the system log to see what
>did that even when you know when it happened so
>you can remove whatever did that from your system

Anyway, just another example caused by the wholly unnatural,
contrived, populist-inspired, madness, kooky. left-wing abomination
that is Daylight Saving.    Do Western Cozies have these problems?

[toc] | [prev] | [next] | [standalone]

#74022

On 5/06/2026 9:14 pm, Petzl wrote:
> On Fri, 5 Jun 2026 17:58:05 +1000, Daniel70 
> <daniel47@nomail.afraid.org> wrote:
>> On 5/06/2026 11:09 am, Petzl wrote:
>>> On Wed, 03 Jun 2026 13:55:09 +1000, "Rod Speed" 
>>> <rod.speed.aaa@gmail.com> wrote:
>>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>>> Petzl <petzlx@gmail.com> wrote
>>>>>> Petzl <petzlx@gmail.com> wrote
>>>> 
>>>>>>> Set time was switched on but a Windows downgrade turned 
>>>>>>> it off
>>>> 
>>>>>> It may not of been Microsoft? HP updated it's CMOS which 
>>>>>> may or may not of caused "Set Time Zone Automatically"??
>>>> 
>>>>> That doesn't happen
>>>> 
>>>>> https://grok.com/share/bGVnYWN5_b69601de-9d9a-44f7-a7b6-b7a4ca282ef8
>>>>
>>> I know for a fact my computer changed correctly without me
>>> touching the settings last daylight saving time change,  Sunday,
>>> 4 October 2026 at 2:00 AM local standard time, clocks went or
>>> were set forward by 1 hour to 3:00 AM.
>> 
>> "Sunday, 4 October *2026* at 2:00 AM local standard time, clocks 
>> *went* or *were set forward* by 1 hour to 3:00 AM." .... well, 
>> Petzl, I always thought you were a bit 'out there' .... but NEVER 
>> realised you were that far 'out there'!!
>> 
> Well it worked  Sunday, October 5, *2025* .At 2:00 AM that morning,

Very good, Petzl! Do you see how THAT Date/Time Group *DIFFERS* to the
Date/Time Group you posted previously??

> clocks were turned forward one hour to 3:00 AM as well Then Auto 
> adjusted as it did Sunday, 5 April 2026, when clocks shifted back an 
> hour from 3:00 am AEDT to 2:00 am AEST
> 
-- 
Daniel70

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | aus.computers

csiph-web