Wow. I just figured out why I couldn't post using AIOE news server yesterday
and today. This past Saturday was the old time of time change. I kept
posting and kept getting "time in header over one hour old" refusal
messages.

So I just set my computer clock back one hour and now I can post.
Until next Sat/Sun when the official time change occurs, my posting time
will show one hour early. No big deal but I'm glad that I finally figured
out the problem. If any of you others can't post, just change your time
back an hour.

Gary :-)

"Gary" > wrote in message ...
> Wow. I just figured out why I couldn't post using AIOE news server
> yesterday
> and today. This past Saturday was the old time of time change. I kept
> posting and kept getting "time in header over one hour old" refusal
> messages.
>
> So I just set my computer clock back one hour and now I can post.
> Until next Sat/Sun when the official time change occurs, my posting time
> will show one hour early. No big deal but I'm glad that I finally figured
> out the problem. If any of you others can't post, just change your time
> back an hour.
>
> Gary :-)


reminds me of the time bounce
https://www.youtube.com/watch?v=WUGYwNzez3g

On Mon, 29 Oct 2012 07:16:32 -0500, Gary > wrote:

> Wow. I just figured out why I couldn't post using AIOE news server yesterday
> and today. This past Saturday was the old time of time change. I kept
> posting and kept getting "time in header over one hour old" refusal
> messages.
>
> So I just set my computer clock back one hour and now I can post.
> Until next Sat/Sun when the official time change occurs, my posting time
> will show one hour early. No big deal but I'm glad that I finally figured
> out the problem. If any of you others can't post, just change your time
> back an hour.
>

My news reader allows me to work "off line" and send later, which is
what I do when I don't have wifi access. So, I suppose AIOE wouldn't
let me send anything I'd already composed if I used it while on a car
trip.

--
I take life with a grain of salt, a slice of lemon and a shot of tequila

Sqwertz wrote:
>
> On Mon, 29 Oct 2012 07:16:32 -0500, Gary wrote:
>
> > Wow. I just figured out why I couldn't post using AIOE news server yesterday
> > and today. This past Saturday was the old time of time change. I kept
> > posting and kept getting "time in header over one hour old" refusal
> > messages.
> >
> > So I just set my computer clock back one hour and now I can post.
> > Until next Sat/Sun when the official time change occurs, my posting time
> > will show one hour early. No big deal but I'm glad that I finally figured
> > out the problem. If any of you others can't post, just change your time
> > back an hour.
>
> Uh, didn't you set your clock to the RIGHT time? Why would it be an
> hour early?
>
> This is what you get for using Windows 98.

Hi Steve, My clock was always set to the RIGHT time but for some reason
last sunday I couldn't post until I figured out (on Monday) that I had to
set it back an hour. Last weekend was the OLD time change weekend. I
turned off the automatic adjust for time change years ago, so my computer
did nothing different this past weekend. I can only assume that the AIOE
news server changed the time a week too early.

In order to post here now, I have to keep my clock set to an hour early.
Windows98 problem? Don't know but I don't know why my old software would
cause this problem since my time never changed.

Regardless, next weekend the time will officially change and I'll be posting
with authentic time once again. Posting this at 7:00 eastern officially,
but my clock is set to 6am in order to post this.

sigh!

On Wed, 31 Oct 2012 02:44:38 +0000, MotoFox >
wrote:

>And it came to pass that Gary delivered the following message unto the
>people, saying~
>
>> Wow. I just figured out why I couldn't post using AIOE news server
>> yesterday and today. This past Saturday was the old time of time change.
>> I kept posting and kept getting "time in header over one hour old" refusal
>> messages.
>>
>> So I just set my computer clock back one hour and now I can post. Until
>> next Sat/Sun when the official time change occurs, my posting time will
>> show one hour early. No big deal but I'm glad that I finally figured out
>> the problem. If any of you others can't post, just change your time back
>> an hour.
>>
>> Gary :-)
>
>Time to go to Eternal-September....

They also have their own shortcomings. Just saying.

On Wed, 31 Oct 2012 02:44:38 +0000, MotoFox >
wrote:

> And it came to pass that Gary delivered the following message unto the
> people, saying~
>
> > Wow. I just figured out why I couldn't post using AIOE news server
> > yesterday and today. This past Saturday was the old time of time change.
> > I kept posting and kept getting "time in header over one hour old" refusal
> > messages.
> >
> > So I just set my computer clock back one hour and now I can post. Until
> > next Sat/Sun when the official time change occurs, my posting time will
> > show one hour early. No big deal but I'm glad that I finally figured out
> > the problem. If any of you others can't post, just change your time back
> > an hour.
> >
> > Gary :-)
>
> Time to go to Eternal-September....

Eternal-September decided to go rogue. Wouldn't take my password - so
I'm done with it.

--
Food is an important part of a balanced diet.

sf > wrote in
:

> On Wed, 31 Oct 2012 02:44:38 +0000, MotoFox >
> wrote:
>
>> And it came to pass that Gary delivered the following message unto
>> the people, saying~
>>
>> > Wow. I just figured out why I couldn't post using AIOE news server
>> > yesterday and today. This past Saturday was the old time of time
>> > change. I kept posting and kept getting "time in header over one
>> > hour old" refusal messages.
>> >
>> > So I just set my computer clock back one hour and now I can post.
>> > Until next Sat/Sun when the official time change occurs, my posting
>> > time will show one hour early. No big deal but I'm glad that I
>> > finally figured out the problem. If any of you others can't post,
>> > just change your time back an hour.
>> >
>> > Gary :-)
>>
>> Time to go to Eternal-September....
>
> Eternal-September decided to go rogue. Wouldn't take my password - so
> I'm done with it.
>


I haven't had any problems with aioe... unlike my 'local' news servers :-/



Peter
back in Brisbane
Australia

"sf" > wrote in message
...

> Eternal-September decided to go rogue. Wouldn't take my password - so
> I'm done with it.

A couple weeks ago, it stopped taking my password too. I hadn't changed
anything; just hadn't use it a couple days. So I did the password reset
thing and it sent me a new password and still didn't work. Ended up
creating a new account with different email, and that worked fine. I
emailed their support about the first account two weeks ago, but never heard
back.

Gary wrote:
>
> Wow. I just figured out why I couldn't post using AIOE news server yesterday
> and today. This past Saturday was the old time of time change. I kept
> posting and kept getting "time in header over one hour old" refusal
> messages.
>
> So I just set my computer clock back one hour and now I can post.
> Until next Sat/Sun when the official time change occurs, my posting time
> will show one hour early. No big deal but I'm glad that I finally figured
> out the problem. If any of you others can't post, just change your time
> back an hour.

You run old an Windows version, right? Checking if you have run Windows
Update by hand and loaded not just all of the critical updates but also
all of the optional ones. One of the optional ones should include up to
date time zone files.

That and/or you can set the time by hand to the correct time.

Doug Freyburger wrote:
>
> Gary wrote:
> >
> > Wow. I just figured out why I couldn't post using AIOE news server yesterday
> > and today. This past Saturday was the old time of time change. I kept
> > posting and kept getting "time in header over one hour old" refusal
> > messages.
> >
> > So I just set my computer clock back one hour and now I can post.
> > Until next Sat/Sun when the official time change occurs, my posting time
> > will show one hour early. No big deal but I'm glad that I finally figured
> > out the problem. If any of you others can't post, just change your time
> > back an hour.
>
> You run old an Windows version, right? Checking if you have run Windows
> Update by hand and loaded not just all of the critical updates but also
> all of the optional ones. One of the optional ones should include up to
> date time zone files.
>
> That and/or you can set the time by hand to the correct time.

Thanks for the info, Doug. I wasn't aware that Window98 put out an update
for the time changes, once the official date change a few years ago. Once
that happened, I just turned off the option to "adjust for daylight savings
time" and I've set it myself twice a year.

Evidently though, my newserver is still using that old date too. In old
years the time changed last weekend and I could no longer post. I have
played with the date thing and even if I set mine back to "adjust for DLST"
it still changes my time to an hour early.

No worries. For the next few days, my posting time will show an hour early.
Next Sunday, all will be fixed and I'll be able to post with the correct
time. The newserver just won't allow posting *from the future*. I'm
posting this at 5:08 but my headers will show 4:08

Gary

Sqwertz wrote:
>
> On Wed, 31 Oct 2012 16:09:01 -0500, Gary wrote:
>
> > No worries. For the next few days, my posting time will show an hour early.
>
> For the second time:
>
> I guarantee that your news server is NOT using the wrong date.
> Thousands of people did not have to change their computers clock to
> post correctly through AIOE. You need to change your time zone.
>
> -sw

Well, Steve, I was about ready to yield to you today. Even though I
manually change my time/date settings, you are correct that for the next two
days I should be showing gmt -4 hours. But it's a minor detail, imo.
Regardless, my time and time zone will show up correct in a little over 2
days.

That said, I do think you were wrong this time. Today, I'm again able to
post using my correct time (but still with the gmt -5 hours, rather than the
correct gmt -4 hours. Evidently, "thousands of people" DID have a problem
with the AIOE server. They must use old software too but they did fix that
today.

I've been posting since Daylight Savings Time went into effect last spring
with the wrong time zone and never a problem

Today, I can now post using my correct time. (but not the correct time
zone). Evidently, AIOE fixed THEIR problem.

G.