Not Spam, but Notice to change links

[Guest PCR]

Re: Not Spam, but Notice to change links

 

Rick Chauvin wrote:

| "PCR" <pcrrcp@netzero.net> wrote in message

| news:e98QjBDIJHA.2272@TK2MSFTNGP04.phx.gbl

| [....]

|

|> You are welcome. Looks to me that did it...!...

|>

|> Fri, 26 Sep 2008 18:32:44 -0400 9/26/08 6:32 PM

|>

|> Now I see your OE header date & my OE "sent" column date of your post

|> match. That is as it should be, because we are in the same time

|> zone. It didn't occur to me you had the auto time adjustment turned

|> off & did it manually. Good thinking on Blanton's part as usual. OK,

|> I'm taking you off my naughty list, Chauvin-- for posting responses

|> before the OP has posted as you did in an earlier thread!

|

| Excellent, great, and thanks PCR for sticking to your guns on this

| one, and you're effort.

 

You are welcome. But it wouldn't have taken much for you to convince me

mine was the wacky one, until MEB & Blanton dropped in anyhow.

 

| Another MVP mentioned on this forum he last year that my date stamp

| was off, I think it was Jeff maybe, but I discounted it at the time

| and thought it was just my isp server issue; sorry about that Jeff.

 

Richards is a sharp one. I must have been there too, & it explains why I

dimly recall this has all happened before.

 

|> I've never noticed my own Desktop got mussed over that the auto date

|> change. Next time I'll have to go look! But you always could just

|> have used something like WinTidy to fix that.

|

| I've always seen everyone elses do it on 9x. I personally had lots of

| shortcuts in a particular order there, and was a pita to put them

| back the way I wanted. I used to take a screenshot of the desktop

| order now and then, and save it, so I would have what it was and was

| quite fussy about it. I've never liked the idea of installing a

| third party program to keep track of my desktop icons, although I

| tested a number of them, but never found one I wanted. I don't have

| to worry about it anymore anyway so it's a null point.

 

WinTidy2 (Neil J. Rubenking) is pretty nice. I don't keep it running,

but only start it when necessary. I haven't noticed it to be necessary

except after I've been to Safe Mode & back-- that what musses icon

positions for me for sure.

 

| Thanks for the reply PCR, and MEB too.

 

You are welcome.

 

| Have a good one.

 

You too. Glad to have been of assistance. It's been a mind-twister. But

Blanton dropped in with the explanation before it was twisted dry!

 

| Rick

|

|> --

|> Thanks or Good Luck,

|> There may be humor in this post, and,

|> Naturally, you will not sue,

|> Should things get worse after this,

|> PCR

|> pcrrcp@netzero.net

 

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

[Guest Bill Blanton]

Re: Not Spam, but Notice to change links

 

"MEB" <meb@not here@hotmail.com> wrote in message news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> | > | GMT/UTC is still a constant. The time at longitude 0.

> | > | The (manipulative) variable is the "time zone" factor of the equation.

> | > |

> | > | If you are calculating your geographic location, you need to adjust

> | > | accordingly.

> | >

> | > Then what you suggest is that mariners and aviators adjust their

> | > chronometer to DST [should that be required] adding that calculation to the

> | > equation to determine position?

> |

> |

> | I'm not suggesting they do or don't adjust to DST. But yeah, whatever your

> | clock's offset to the constant, you'd have to calculate that in. There is only

> | the one "point in time", no matter what the clock reads.

> |

>

> So we come full circle, to how easy, yet sloppy, this time adjustment

> method is. The ONLY way to allow this {for this to work} using this method,

> is to modify EVERY computer and network around the world each and every time

> some modification is made.

 

I don't see it as sloppy really. You have the agreed upon "constant" GMT, and

then you modify that according to your "zone". Add or subtract the offset

from the "clock" to determine "universal time".

 

What's the alternative? We could all use the GMT/UTC. (I wouldn't have to go

to work until noon, though the sun would be rising).

 

> A failure ANYWHERE throws the entire system off.

 

It does in a way... though it wasn't too catastrophic in this case.

 

> This also would seem to allow some vulnerabilities to occur. Server

> identifiers, DNS, registrar services, message headers, IP packet formation,

> and other, could, potentially, be affected due to actual physical location

> variances.

 

That's soemthing to think about...however;

 

The variances (or offsets of) the "physical location" don't matter as long as

you resolve correctly to the constant..

 

Where you are doesn't matter as long as your time offset to GMT is correct. I

could set my clock forward 9 more minutes EST/DST, and then fly to the Pacific

coast. As long as I adjust my offset accordingly, say GMT -03:51, and my clock

is still at EST/DST+00:09, then it will resolve to GMT correctly. And if I'm

navigating I need to take that offset into consideration to get the time at

longitude zero.

[Guest Bill Blanton]

Re: Not Spam, but Notice to change links

 

 

"Rick Chauvin" <justask@nospamz.com> wrote in message news:%232yqdWMIJHA.3496@TK2MSFTNGP05.phx.gbl...

>

>

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> news:uhxwnELIJHA.1304@TK2MSFTNGP02.phx.gbl

>> "Rick Chauvin" <justask@nospamz.com> wrote in message

>> news:erWETfCIJHA.4240@TK2MSFTNGP02.phx.gbl...

>>>

>>>

>>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

>>> news:eYM%23VE4HJHA.2296@TK2MSFTNGP03.phx.gbl

>>>

>>> [...]

>>>

>>>> Rick, I don't think your system is on daylight savings time? EST should

>>>> be GMT-400 during DST, and -500 when not.

>>

>>

>>>> It could be that he turned off the "auto adjust" and set his clock back

>>>> manually. The clocks right, but offset is off.

>>>

>>> [...]

>>>

>>> Hi Bill,

>>>

>>> You are quite right on all counts Bill.

>>> I am in EST but as you said my computer is set GMT-0500 and yes I do

>>> have Auto Adjust turned off and always have set it manually the first

>>> of the year. I've done that since Win9x because back then it drove me

>>> crazy when auto adjust was on it would scramble my Desktop icons when

>>> it auto adjusted, and so out of habit right along had set my W2K/WXP

>>> that way too, and have been staying booted and posting with XP this

>>> year anyway. I assume XP/2K never scrambles desktop icons after an

>>> time auto adjust?

>>

>> I've never seen XP scramble (or unscramble) desktop icons for that

>> reason, though I have a vague recollection of what you mention on some 9x

>> systems.

>

> Okay good, but I've seen XP scramble the order of them in another instance

> anyway.

>

>

>> On a side note; if you have any volumes formatted as NTFS, the displayed

>> file timestamps will be adjusted when the time offset changes. NTFS

>> stores timestamps at UTC, and computes in the offset for the display.

>

> Okay, good to know.

>

>

>>> I just now check marked the box to Auto Adjust, and my time jumped

>>> ahead an hour which is incorrect, so I manually adjusted the clock back

>>> an hour but leaving the box checkmarked; I hope this solves the problem.

>

>> I can't vouch for the clock ;-) , but the offset now looks good..

>

> Okay Bill, thank you very much for posting to solve the issue.

>

> I've much appreciated your valuable input over the years.

>

> Rick

>

> ..it's almost November, so get your 10 gal frylator out.

 

Already?.. It seems like I just got rid of the oil from last year ;-)

[Guest MEB]

time offset, adjustments, and related discussions

 

time offset, adjustments, and related discussions

 

 

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:e6$%23lXXIJHA.1308@TK2MSFTNGP02.phx.gbl...

| "MEB" <meb@not here@hotmail.com> wrote in message

news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...

| > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

|

| > | > | GMT/UTC is still a constant. The time at longitude 0.

| > | > | The (manipulative) variable is the "time zone" factor of the

equation.

| > | > |

| > | > | If you are calculating your geographic location, you need to

adjust

| > | > | accordingly.

| > | >

| > | > Then what you suggest is that mariners and aviators adjust their

| > | > chronometer to DST [should that be required] adding that calculation

to the

| > | > equation to determine position?

| > |

|

| > |

| > | I'm not suggesting they do or don't adjust to DST. But yeah, whatever

your

| > | clock's offset to the constant, you'd have to calculate that in. There

is only

| > | the one "point in time", no matter what the clock reads.

| > |

| >

| > So we come full circle, to how easy, yet sloppy, this time adjustment

| > method is. The ONLY way to allow this {for this to work} using this

method,

| > is to modify EVERY computer and network around the world each and every

time

| > some modification is made.

|

| I don't see it as sloppy really. You have the agreed upon "constant" GMT,

and

| then you modify that according to your "zone". Add or subtract the offset

| from the "clock" to determine "universal time".

|

| What's the alternative? We could all use the GMT/UTC. (I wouldn't have to

go

| to work until noon, though the sun would be rising).

|

|

| > A failure ANYWHERE throws the entire system off.

|

| It does in a way... though it wasn't too catastrophic in this case.

|

|

| > This also would seem to allow some vulnerabilities to occur. Server

| > identifiers, DNS, registrar services, message headers, IP packet

formation,

| > and other, could, potentially, be affected due to actual physical

location

| > variances.

|

| That's soemthing to think about...however;

|

| The variances (or offsets of) the "physical location" don't matter as long

as

| you resolve correctly to the constant..

|

| Where you are doesn't matter as long as your time offset to GMT is

correct. I

| could set my clock forward 9 more minutes EST/DST, and then fly to the

Pacific

| coast. As long as I adjust my offset accordingly, say GMT -03:51, and my

clock

| is still at EST/DST+00:09, then it will resolve to GMT correctly. And if

I'm

| navigating I need to take that offset into consideration to get the time

at

| longitude zero.

|

 

Yes that would work for you, but you ONLY. It would NOT work for the

airline, terminal, flight controllers, or others around you either where you

took off or where you landed.. Nor would it work personally if you needed to

be somewhere at a specific time, UNLESS you constantly adjusted real time to

your private time in addition to any real time offsets [having not further

changed your personal watch/clock].

 

Need we re-review the [projected and at times real] panic that ensued

during the millenium change over and the BIOS, OS, and related issues [such

as 1999 - 999 - 99]. I think not, as they where reviewed and documented on

hundreds of sites, government bulletins, software updates, BIOS and other

related... what COULD have happened is also well documented, moreover, these

DID cause numerous issues, from electric supply failures, to system and

network crashes, Internet interruption, to numerous others. Of course we

made it through those times... but they DO display both the vulnerabilities

AND other related to any such issues.

 

Think that might help explain why XP and VISTA use GMT/UTC? And why I think

this is zone shift a sloppy way to provide the changes?

 

--

MEB

http://peoplescounsel.org

a Peoples' counsel

_ _

~~

[Guest Rick Chauvin]

Re: Not Spam, but Notice to change links

 

 

 

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:ecYMpXXIJHA.4280@TK2MSFTNGP04.phx.gbl

 

[....]

>> ..it's almost November, so get your 10 gal frylator out.

> Already?.. It seems like I just got rid of the oil from last year ;-)

 

I was told the older you get the faster time seems to go by.

 

I've found it to be true! The years are flying by way to fast.

 

One more question about the time thing. When I had check marked the box to

Auto Adjust DST the other day my clock immediately moved ahead a hour, and

so I had to move it back and hour to be correct, now this does not mean

that come 1/1/09 when it changes automatically it's going to be off an hour

again? I assume it will change itself correctly now? Thinking of which,

since I live in NH we have this thing where they do DST a few weeks earlier

than normal, how is that going to work? I never bothered with paying much

attention to all these patches to fix this and that with the time thing,

and just assumed it was included in SP3.

 

Rick

[Guest PCR]

Re: Not Spam, but Notice to change links

 

Rick Chauvin wrote:

| "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

| news:ecYMpXXIJHA.4280@TK2MSFTNGP04.phx.gbl

|

| [....]

|

|>> ..it's almost November, so get your 10 gal frylator out.

|

|> Already?.. It seems like I just got rid of the oil from last year ;-)

|

| I was told the older you get the faster time seems to go by.

|

| I've found it to be true! The years are flying by way to fast.

|

| One more question about the time thing. When I had check marked the

| box to Auto Adjust DST the other day my clock immediately moved ahead

| a hour, and so I had to move it back and hour to be correct, now this

| does not mean that come 1/1/09 when it changes automatically it's

| going to be off an hour again? I assume it will change itself

| correctly now? Thinking of which, since I live in NH we have this

| thing where they do DST a few weeks earlier than normal, how is that

| going to work? I never bothered with paying much attention to all

| these patches to fix this and that with the time thing, and just

| assumed it was included in SP3.

 

That's right-- DST is plus one hour. When DST is over, your clock will

go back an hour. Very good! But verify your dates are correct (as

Blanton pointed out currently there is overlap with the old dates-- BOTH

are in DST now!) using TZEdit.

 

Run TZEdit, Chauvin, if it will work in XP...

http://www.softshape.com/cham/manual/tzedit.htm

TZEdit.

 

Set it to comply with the following, if it isn't already so...

http://www.timeanddate.com/worldclock/city.html?n=68

Current local time in Concord

......Quote...................

UTC/GMT Offset

Standard time zone: UTC/GMT -5 hours

Daylight saving time: +1 hour

Current time zone offset: UTC/GMT -4 hours

Time zone abbreviation: EDT - Eastern Daylight Time

 

Daylight Saving Time

DST started on Sunday, March 9, 2008 at 2:00 AM local standard time

DST ends on Sunday, November 2, 2008 at 2:00 AM local daylight time

......EOQ.....................

 

Set it to start on the SECOND Sunday of March & end on the FIRST Sunday

in November. (The precise day won't matter-- TZEdit goes by 1st & 2nd.)

 

That's the same for everyone, though, who is in DST-- not just New

Hamshire. Maybe they've stopped the foolishness of doing it weeks

earlier since the big change back in '07.

 

| Rick

 

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

[Guest Bill Blanton]

Re: time offset, adjustments, and related discussions

 

Re: time offset, adjustments, and related discussions

 

 

"MEB" <meb@not here@hotmail.com> wrote in message news:uSMgkeaIJHA.4836@TK2MSFTNGP03.phx.gbl...

>

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> news:e6$%23lXXIJHA.1308@TK2MSFTNGP02.phx.gbl...

> | "MEB" <meb@not here@hotmail.com> wrote in message

> news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...

> | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> |

> | > | > | GMT/UTC is still a constant. The time at longitude 0.

> | > | > | The (manipulative) variable is the "time zone" factor of the

> equation.

> | > | > |

> | > | > | If you are calculating your geographic location, you need to

> adjust

> | > | > | accordingly.

> | > | >

> | > | > Then what you suggest is that mariners and aviators adjust their

> | > | > chronometer to DST [should that be required] adding that calculation

> to the

> | > | > equation to determine position?

> | > |

> |

> | > |

> | > | I'm not suggesting they do or don't adjust to DST. But yeah, whatever

> your

> | > | clock's offset to the constant, you'd have to calculate that in. There

> is only

> | > | the one "point in time", no matter what the clock reads.

> | > |

> | >

> | > So we come full circle, to how easy, yet sloppy, this time adjustment

> | > method is. The ONLY way to allow this {for this to work} using this

> method,

> | > is to modify EVERY computer and network around the world each and every

> time

> | > some modification is made.

> |

> | I don't see it as sloppy really. You have the agreed upon "constant" GMT,

> and

> | then you modify that according to your "zone". Add or subtract the offset

> | from the "clock" to determine "universal time".

> |

> | What's the alternative? We could all use the GMT/UTC. (I wouldn't have to

> go

> | to work until noon, though the sun would be rising).

> |

> |

> | > A failure ANYWHERE throws the entire system off.

> |

> | It does in a way... though it wasn't too catastrophic in this case.

> |

> |

> | > This also would seem to allow some vulnerabilities to occur. Server

> | > identifiers, DNS, registrar services, message headers, IP packet

> formation,

> | > and other, could, potentially, be affected due to actual physical

> location

> | > variances.

> |

> | That's soemthing to think about...however;

> |

> | The variances (or offsets of) the "physical location" don't matter as long

> as

> | you resolve correctly to the constant..

> |

> | Where you are doesn't matter as long as your time offset to GMT is

> correct. I

> | could set my clock forward 9 more minutes EST/DST, and then fly to the

> Pacific

> | coast. As long as I adjust my offset accordingly, say GMT -03:51, and my

> clock

> | is still at EST/DST+00:09, then it will resolve to GMT correctly. And if

> I'm

> | navigating I need to take that offset into consideration to get the time

> at

> | longitude zero.

> |

>

> Yes that would work for you, but you ONLY. It would NOT work for the

> airline, terminal, flight controllers, or others around you either where you

> took off or where you landed.. Nor would it work personally if you needed to

> be somewhere at a specific time, UNLESS you constantly adjusted real time to

> your private time in addition to any real time offsets [having not further

> changed your personal watch/clock].

 

I don't want to belabor this.. if you know the time at point zero on a sphere,

and the angle of the sun, you can calculate your latitude.

 

I don't know enough about sextants, chronometers, and the positions of the

stars to explain it any better.

 

As far as the aviation industry, I'm pretty sure they use GPS.

 

 

 

> Need we re-review the [projected and at times real] panic that ensued

> during the millenium change over and the BIOS, OS, and related issues [such

> as 1999 - 999 - 99]. I think not, as they where reviewed and documented on

> hundreds of sites, government bulletins, software updates, BIOS and other

> related... what COULD have happened is also well documented, moreover, these

> DID cause numerous issues, from electric supply failures, to system and

> network crashes, Internet interruption, to numerous others. Of course we

> made it through those times... but they DO display both the vulnerabilities

> AND other related to any such issues.

>

> Think that might help explain why XP and VISTA use GMT/UTC? And why I think

> this is zone shift a sloppy way to provide the changes?

 

So again, what do you propose as an alternative?

[Guest Bill Blanton]

Re: Not Spam, but Notice to change links

 

"Rick Chauvin" <justask@nospamz.com> wrote in message news:O$apdOdIJHA.468@TK2MSFTNGP06.phx.gbl...

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> news:ecYMpXXIJHA.4280@TK2MSFTNGP04.phx.gbl

>

> [....]

> One more question about the time thing. When I had check marked the box to

> Auto Adjust DST the other day my clock immediately moved ahead a hour, and

> so I had to move it back and hour to be correct, now this does not mean

> that come 1/1/09 when it changes automatically it's going to be off an hour

> again? I assume it will change itself correctly now? Thinking of which,

> since I live in NH we have this thing where they do DST a few weeks earlier

> than normal, how is that going to work? I never bothered with paying much

> attention to all these patches to fix this and that with the time thing,

> and just assumed it was included in SP3.

 

Yes, it will adjust automatically, though I have no idea about the NH rule.

It (the NH zone) doesn't appear in my XP-SP3 system, as does IN, which

I think also has its own rules.

 

SP3 includes the patch to modify the date on which the zones change, so

it may be as PCR says?

[Guest FromTheRafters]

Re: Not Spam, but Notice to change links

 

Thanks a lot guys - I used to think I knew what time it was,

now I'm not so sure. :o\

 

....and I gotta be at work at 8:30 AM Eastern Daylight New Hampshire

Savings Time (I think?). Keene, not Spofford but I don't think I cross

any timezones on my commute. So when do I go to Eastern Daylight

New Hampshire Wastings Time?

[Guest MEB]

Re: time offset, adjustments, and related discussions

 

Re: time offset, adjustments, and related discussions

 

 

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:uQoaEdpIJHA.2208@TK2MSFTNGP02.phx.gbl...

|

| "MEB" <meb@not here@hotmail.com> wrote in message

news:uSMgkeaIJHA.4836@TK2MSFTNGP03.phx.gbl...

| >

| > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

| > news:e6$%23lXXIJHA.1308@TK2MSFTNGP02.phx.gbl...

| > | "MEB" <meb@not here@hotmail.com> wrote in message

| > news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...

| > | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

| > |

| > | > | > | GMT/UTC is still a constant. The time at longitude 0.

| > | > | > | The (manipulative) variable is the "time zone" factor of the

| > equation.

| > | > | > |

| > | > | > | If you are calculating your geographic location, you need to

| > adjust

| > | > | > | accordingly.

| > | > | >

| > | > | > Then what you suggest is that mariners and aviators adjust their

| > | > | > chronometer to DST [should that be required] adding that

calculation

| > to the

| > | > | > equation to determine position?

| > | > |

| > |

| > | > |

| > | > | I'm not suggesting they do or don't adjust to DST. But yeah,

whatever

| > your

| > | > | clock's offset to the constant, you'd have to calculate that in.

There

| > is only

| > | > | the one "point in time", no matter what the clock reads.

| > | > |

| > | >

| > | > So we come full circle, to how easy, yet sloppy, this time

adjustment

| > | > method is. The ONLY way to allow this {for this to work} using this

| > method,

| > | > is to modify EVERY computer and network around the world each and

every

| > time

| > | > some modification is made.

| > |

| > | I don't see it as sloppy really. You have the agreed upon "constant"

GMT,

| > and

| > | then you modify that according to your "zone". Add or subtract the

offset

| > | from the "clock" to determine "universal time".

| > |

| > | What's the alternative? We could all use the GMT/UTC. (I wouldn't have

to

| > go

| > | to work until noon, though the sun would be rising).

| > |

| > |

| > | > A failure ANYWHERE throws the entire system off.

| > |

| > | It does in a way... though it wasn't too catastrophic in this case.

| > |

| > |

| > | > This also would seem to allow some vulnerabilities to occur. Server

| > | > identifiers, DNS, registrar services, message headers, IP packet

| > formation,

| > | > and other, could, potentially, be affected due to actual physical

| > location

| > | > variances.

| > |

| > | That's soemthing to think about...however;

| > |

| > | The variances (or offsets of) the "physical location" don't matter as

long

| > as

| > | you resolve correctly to the constant..

| > |

| > | Where you are doesn't matter as long as your time offset to GMT is

| > correct. I

| > | could set my clock forward 9 more minutes EST/DST, and then fly to the

| > Pacific

| > | coast. As long as I adjust my offset accordingly, say GMT -03:51, and

my

| > clock

| > | is still at EST/DST+00:09, then it will resolve to GMT correctly. And

if

| > I'm

| > | navigating I need to take that offset into consideration to get the

time

| > at

| > | longitude zero.

| > |

| >

| > Yes that would work for you, but you ONLY. It would NOT work for the

| > airline, terminal, flight controllers, or others around you either where

you

| > took off or where you landed.. Nor would it work personally if you

needed to

| > be somewhere at a specific time, UNLESS you constantly adjusted real

time to

| > your private time in addition to any real time offsets [having not

further

| > changed your personal watch/clock].

|

| I don't want to belabor this.. if you know the time at point zero on a

sphere,

| and the angle of the sun, you can calculate your latitude.

|

| I don't know enough about sextants, chronometers, and the positions of the

| stars to explain it any better.

|

| As far as the aviation industry, I'm pretty sure they use GPS.

|

|

|

|

| > Need we re-review the [projected and at times real] panic that ensued

| > during the millenium change over and the BIOS, OS, and related issues

[such

| > as 1999 - 999 - 99]. I think not, as they where reviewed and documented

on

| > hundreds of sites, government bulletins, software updates, BIOS and

other

| > related... what COULD have happened is also well documented, moreover,

these

| > DID cause numerous issues, from electric supply failures, to system and

| > network crashes, Internet interruption, to numerous others. Of course we

| > made it through those times... but they DO display both the

vulnerabilities

| > AND other related to any such issues.

| >

| > Think that might help explain why XP and VISTA use GMT/UTC? And why I

think

| > this is zone shift a sloppy way to provide the changes?

|

| So again, what do you propose as an alternative?

|

 

Ah how about something more appropriate, like a TIME change.. you know,

uhoh, here's the date, here's the change, one hour back on the clock....

UHOH, here's the date, here's the change, one hour up on the clock. Isn't

that what you do with your watch and clocks?

 

But wait you say, how would I synchronize with the Atomic clocks I

contact,,, they work only from actual time adjusted to offset.... hmmm,

how about, uhoh, here's the date, here's the change, all automatic [network]

modifications are so adjusted.. makes the need adjusted properly to the

clock control program or other control... keeps you GPS located and makes

the network fully synced.... wacha tink, do da servers uz DST zone shift er

GMT/UTC offset wif clock change

 

--

MEB

http://peoplescounsel.org

a Peoples' counsel

_ _

~~

[Guest MEB]

Re: Not Spam, but Notice to change links

 

That's easy, when you go home........

 

--

MEB

http://peoplescounsel.org

a Peoples' counsel

_ _

~~

"FromTheRafters" <erratic@nomail.afraid.org> wrote in message

news:%23xpzynpIJHA.3680@TK2MSFTNGP04.phx.gbl...

| Thanks a lot guys - I used to think I knew what time it was,

| now I'm not so sure. :o\

|

| ...and I gotta be at work at 8:30 AM Eastern Daylight New Hampshire

| Savings Time (I think?). Keene, not Spofford but I don't think I cross

| any timezones on my commute. So when do I go to Eastern Daylight

| New Hampshire Wastings Time?

|

|

[Guest Bill Blanton]

Re: time offset, adjustments, and related discussions

 

Re: time offset, adjustments, and related discussions

 

 

"MEB" <meb@not here@hotmail.com> wrote in message news:eTPJ9spIJHA.4568@TK2MSFTNGP06.phx.gbl...

>

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> news:uQoaEdpIJHA.2208@TK2MSFTNGP02.phx.gbl...

> |

> | "MEB" <meb@not here@hotmail.com> wrote in message

> news:uSMgkeaIJHA.4836@TK2MSFTNGP03.phx.gbl...

> | >

> | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> | > news:e6$%23lXXIJHA.1308@TK2MSFTNGP02.phx.gbl...

> | > | "MEB" <meb@not here@hotmail.com> wrote in message

> | > news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...

> | > | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

> | > |

> | > | > | > | GMT/UTC is still a constant. The time at longitude 0.

> | > | > | > | The (manipulative) variable is the "time zone" factor of the

> | > equation.

> | > | > | > |

> | > | > | > | If you are calculating your geographic location, you need to

> | > adjust

> | > | > | > | accordingly.

> | > | > | >

> | > | > | > Then what you suggest is that mariners and aviators adjust their

> | > | > | > chronometer to DST [should that be required] adding that

> calculation

> | > to the

> | > | > | > equation to determine position?

> | > | > |

> | > |

> | > | > |

> | > | > | I'm not suggesting they do or don't adjust to DST. But yeah,

> whatever

> | > your

> | > | > | clock's offset to the constant, you'd have to calculate that in.

> There

> | > is only

> | > | > | the one "point in time", no matter what the clock reads.

> | > | > |

> | > | >

> | > | > So we come full circle, to how easy, yet sloppy, this time

> adjustment

> | > | > method is. The ONLY way to allow this {for this to work} using this

> | > method,

> | > | > is to modify EVERY computer and network around the world each and

> every

> | > time

> | > | > some modification is made.

> | > |

> | > | I don't see it as sloppy really. You have the agreed upon "constant"

> GMT,

> | > and

> | > | then you modify that according to your "zone". Add or subtract the

> offset

> | > | from the "clock" to determine "universal time".

> | > |

> | > | What's the alternative? We could all use the GMT/UTC. (I wouldn't have

> to

> | > go

> | > | to work until noon, though the sun would be rising).

> | > |

> | > |

> | > | > A failure ANYWHERE throws the entire system off.

> | > |

> | > | It does in a way... though it wasn't too catastrophic in this case.

> | > |

> | > |

> | > | > This also would seem to allow some vulnerabilities to occur. Server

> | > | > identifiers, DNS, registrar services, message headers, IP packet

> | > formation,

> | > | > and other, could, potentially, be affected due to actual physical

> | > location

> | > | > variances.

> | > |

> | > | That's soemthing to think about...however;

> | > |

> | > | The variances (or offsets of) the "physical location" don't matter as

> long

> | > as

> | > | you resolve correctly to the constant..

> | > |

> | > | Where you are doesn't matter as long as your time offset to GMT is

> | > correct. I

> | > | could set my clock forward 9 more minutes EST/DST, and then fly to the

> | > Pacific

> | > | coast. As long as I adjust my offset accordingly, say GMT -03:51, and

> my

> | > clock

> | > | is still at EST/DST+00:09, then it will resolve to GMT correctly. And

> if

> | > I'm

> | > | navigating I need to take that offset into consideration to get the

> time

> | > at

> | > | longitude zero.

> | > |

> | >

> | > Yes that would work for you, but you ONLY. It would NOT work for the

> | > airline, terminal, flight controllers, or others around you either where

> you

> | > took off or where you landed.. Nor would it work personally if you

> needed to

> | > be somewhere at a specific time, UNLESS you constantly adjusted real

> time to

> | > your private time in addition to any real time offsets [having not

> further

> | > changed your personal watch/clock].

> |

> | I don't want to belabor this.. if you know the time at point zero on a

> sphere,

> | and the angle of the sun, you can calculate your latitude.

> |

> | I don't know enough about sextants, chronometers, and the positions of the

> | stars to explain it any better.

> |

> | As far as the aviation industry, I'm pretty sure they use GPS.

> |

> |

> |

> |

> | > Need we re-review the [projected and at times real] panic that ensued

> | > during the millenium change over and the BIOS, OS, and related issues

> [such

> | > as 1999 - 999 - 99]. I think not, as they where reviewed and documented

> on

> | > hundreds of sites, government bulletins, software updates, BIOS and

> other

> | > related... what COULD have happened is also well documented, moreover,

> these

> | > DID cause numerous issues, from electric supply failures, to system and

> | > network crashes, Internet interruption, to numerous others. Of course we

> | > made it through those times... but they DO display both the

> vulnerabilities

> | > AND other related to any such issues.

> | >

> | > Think that might help explain why XP and VISTA use GMT/UTC? And why I

> think

> | > this is zone shift a sloppy way to provide the changes?

> |

> | So again, what do you propose as an alternative?

> |

>

> Ah how about something more appropriate, like a TIME change.. you know,

> uhoh, here's the date, here's the change, one hour back on the clock....

> UHOH, here's the date, here's the change, one hour up on the clock. Isn't

> that what you do with your watch and clocks?

 

Why should it be the "same time" on the East side of the zone as the West

side of the zone? Maybe we should all be on sidereal time?

http://tycho.usno.navy.mil/sidereal.html

 

> But wait you say, how would I synchronize with the Atomic clocks I

> contact,,, they work only from actual time adjusted to offset.... hmmm,

> how about, uhoh, here's the date, here's the change, all automatic [network]

> modifications are so adjusted.. makes the need adjusted properly to the

> clock control program or other control... keeps you GPS located and makes

> the network fully synced.... wacha tink, do da servers uz DST zone shift er

> GMT/UTC offset wif clock change

 

I really have no idea what you're trying to say...

[Guest Bill Blanton]

Re: Not Spam, but Notice to change links

 

Does anybody really know what time it is...

Does anybody really care... [Chicago]

 

 

"FromTheRafters" <erratic@nomail.afraid.org> wrote in message news:%23xpzynpIJHA.3680@TK2MSFTNGP04.phx.gbl...

> Thanks a lot guys - I used to think I knew what time it was,

> now I'm not so sure. :o\

>

> ...and I gotta be at work at 8:30 AM Eastern Daylight New Hampshire

> Savings Time (I think?). Keene, not Spofford but I don't think I cross

> any timezones on my commute. So when do I go to Eastern Daylight

> New Hampshire Wastings Time?

>

[Guest MEB]

Re: time offset, adjustments, and related discussions

 

Re: time offset, adjustments, and related discussions

 

 

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:uUjBU9pIJHA.788@TK2MSFTNGP06.phx.gbl...

|

| "MEB" <meb@not here@hotmail.com> wrote in message

news:eTPJ9spIJHA.4568@TK2MSFTNGP06.phx.gbl...

| >

| > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

| > news:uQoaEdpIJHA.2208@TK2MSFTNGP02.phx.gbl...

| > |

| > | "MEB" <meb@not here@hotmail.com> wrote in message

| > news:uSMgkeaIJHA.4836@TK2MSFTNGP03.phx.gbl...

| > | >

| > | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

| > | > news:e6$%23lXXIJHA.1308@TK2MSFTNGP02.phx.gbl...

| > | > | "MEB" <meb@not here@hotmail.com> wrote in message

| > | > news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...

| > | > | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

| > | > |

| > | > | > | > | GMT/UTC is still a constant. The time at longitude 0.

| > | > | > | > | The (manipulative) variable is the "time zone" factor of

the

| > | > equation.

| > | > | > | > |

| > | > | > | > | If you are calculating your geographic location, you need

to

| > | > adjust

| > | > | > | > | accordingly.

| > | > | > | >

| > | > | > | > Then what you suggest is that mariners and aviators adjust

their

| > | > | > | > chronometer to DST [should that be required] adding that

| > calculation

| > | > to the

| > | > | > | > equation to determine position?

| > | > | > |

| > | > |

| > | > | > |

| > | > | > | I'm not suggesting they do or don't adjust to DST. But yeah,

| > whatever

| > | > your

| > | > | > | clock's offset to the constant, you'd have to calculate that

in.

| > There

| > | > is only

| > | > | > | the one "point in time", no matter what the clock reads.

| > | > | > |

| > | > | >

| > | > | > So we come full circle, to how easy, yet sloppy, this time

| > adjustment

| > | > | > method is. The ONLY way to allow this {for this to work} using

this

| > | > method,

| > | > | > is to modify EVERY computer and network around the world each

and

| > every

| > | > time

| > | > | > some modification is made.

| > | > |

| > | > | I don't see it as sloppy really. You have the agreed upon

"constant"

| > GMT,

| > | > and

| > | > | then you modify that according to your "zone". Add or subtract the

| > offset

| > | > | from the "clock" to determine "universal time".

| > | > |

| > | > | What's the alternative? We could all use the GMT/UTC. (I wouldn't

have

| > to

| > | > go

| > | > | to work until noon, though the sun would be rising).

| > | > |

| > | > |

| > | > | > A failure ANYWHERE throws the entire system off.

| > | > |

| > | > | It does in a way... though it wasn't too catastrophic in this

case.

| > | > |

| > | > |

| > | > | > This also would seem to allow some vulnerabilities to occur.

Server

| > | > | > identifiers, DNS, registrar services, message headers, IP packet

| > | > formation,

| > | > | > and other, could, potentially, be affected due to actual

physical

| > | > location

| > | > | > variances.

| > | > |

| > | > | That's soemthing to think about...however;

| > | > |

| > | > | The variances (or offsets of) the "physical location" don't matter

as

| > long

| > | > as

| > | > | you resolve correctly to the constant..

| > | > |

| > | > | Where you are doesn't matter as long as your time offset to GMT is

| > | > correct. I

| > | > | could set my clock forward 9 more minutes EST/DST, and then fly to

the

| > | > Pacific

| > | > | coast. As long as I adjust my offset accordingly, say GMT -03:51,

and

| > my

| > | > clock

| > | > | is still at EST/DST+00:09, then it will resolve to GMT correctly.

And

| > if

| > | > I'm

| > | > | navigating I need to take that offset into consideration to get

the

| > time

| > | > at

| > | > | longitude zero.

| > | > |

| > | >

| > | > Yes that would work for you, but you ONLY. It would NOT work for the

| > | > airline, terminal, flight controllers, or others around you either

where

| > you

| > | > took off or where you landed.. Nor would it work personally if you

| > needed to

| > | > be somewhere at a specific time, UNLESS you constantly adjusted real

| > time to

| > | > your private time in addition to any real time offsets [having not

| > further

| > | > changed your personal watch/clock].

| > |

| > | I don't want to belabor this.. if you know the time at point zero on a

| > sphere,

| > | and the angle of the sun, you can calculate your latitude.

| > |

| > | I don't know enough about sextants, chronometers, and the positions of

the

| > | stars to explain it any better.

| > |

| > | As far as the aviation industry, I'm pretty sure they use GPS.

| > |

| > |

| > |

| > |

| > | > Need we re-review the [projected and at times real] panic that

ensued

| > | > during the millenium change over and the BIOS, OS, and related

issues

| > [such

| > | > as 1999 - 999 - 99]. I think not, as they where reviewed and

documented

| > on

| > | > hundreds of sites, government bulletins, software updates, BIOS and

| > other

| > | > related... what COULD have happened is also well documented,

moreover,

| > these

| > | > DID cause numerous issues, from electric supply failures, to system

and

| > | > network crashes, Internet interruption, to numerous others. Of

course we

| > | > made it through those times... but they DO display both the

| > vulnerabilities

| > | > AND other related to any such issues.

| > | >

| > | > Think that might help explain why XP and VISTA use GMT/UTC? And why

I

| > think

| > | > this is zone shift a sloppy way to provide the changes?

| > |

| > | So again, what do you propose as an alternative?

| > |

| >

| > Ah how about something more appropriate, like a TIME change.. you know,

| > uhoh, here's the date, here's the change, one hour back on the clock....

| > UHOH, here's the date, here's the change, one hour up on the clock.

Isn't

| > that what you do with your watch and clocks?

|

| Why should it be the "same time" on the East side of the zone as the West

| side of the zone? Maybe we should all be on sidereal time?

| http://tycho.usno.navy.mil/sidereal.html

|

|

| > But wait you say, how would I synchronize with the Atomic clocks I

| > contact,,, they work only from actual time adjusted to offset.... hmmm,

| > how about, uhoh, here's the date, here's the change, all automatic

[network]

| > modifications are so adjusted.. makes the need adjusted properly to the

| > clock control program or other control... keeps you GPS located and

makes

| > the network fully synced.... wacha tink, do da servers uz DST zone shift

er

| > GMT/UTC offset wif clock change

|

| I really have no idea what you're trying to say...

|

 

Okay then, let's get down to it::::

 

ALL of the issues have already been set forth and resolved when dealing

with the Internet, time, connected networks, protocol formation and

requirements, and pretty much everything else.. of course always open to

modification and updates, but the basics must be followed

 

Start here:

http://www.ietf.org/rfc/rfc2616.txt - Hypertext Transfer Protocol -- HTTP/1.1

popover here generally:

http://www.w3.org/TR/NOTE-datetime

add this in:

http://www.ietf.org/rfc/rfc2396.txt - Uniform Resource Identifiers (URI):

Generic Syntax

notice this:

http://www.w3.org/XML/Schema -

consider this:

http://www.w3.org/TR/1999/REC-xml-names-19990114/Overview.html - Namespaces

in XML, and modifications

you might cruise around over here:

http://www.cni.org/ - the Coalition for Networked Information

 

Of course there are dozens more, but this should provide a base to work

from....

 

Oh, don't forget this since nothing happens out here without it:

http://www.sans.org/info/3871 - TCP/IP handbook in PDF

http://www.cisco.com/en/US/docs/internetworking/technology/handbook/Internet-Protocols.html -

Cisco - Internet Protocols

 

And if you feel up to it, compare IPv6 to IPv4....

 

 

--

MEB

http://peoplescounsel.org

a Peoples' counsel

_ _

~~

[Guest MEB]

Re: Not Spam, but Notice to change links

 

oh yeahhhhh

 

ahhh, there's someone over in win98.disks.general looking for help, I'm

going to direct them here since no-one appears to be monitoring that group

[except me]..... crosspost attempt... kill the crosspost if it gets here...

 

--

MEB

http://peoplescounsel.org

a Peoples' counsel

_ _

~~

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:O15tX%23pIJHA.1156@TK2MSFTNGP04.phx.gbl...

| Does anybody really know what time it is...

| Does anybody really care... [Chicago]

|

|

| "FromTheRafters" <erratic@nomail.afraid.org> wrote in message

news:%23xpzynpIJHA.3680@TK2MSFTNGP04.phx.gbl...

| > Thanks a lot guys - I used to think I knew what time it was,

| > now I'm not so sure. :o\

| >

| > ...and I gotta be at work at 8:30 AM Eastern Daylight New Hampshire

| > Savings Time (I think?). Keene, not Spofford but I don't think I cross

| > any timezones on my commute. So when do I go to Eastern Daylight

| > New Hampshire Wastings Time?

| >

|

|

[Guest Etal]

Re: time offset, adjustments, and related discussions

 

Re: time offset, adjustments, and related discussions

 

Bill Blanton wrote:

>

> So again, what do you propose as an alternative?

>

 

That's easy. Just abolish the ludicrous construct known as

'Daylight Savings Time' (DST).

 

Timezones are necessary because we're on a globe spinning

around its axis. Agreeing on one zone being Zero and others

offset to that is logical. These are determined and set once and

for all (for the foreseeable future).

 

But we can't save time.

And we can't save daylight.

We can however try to fool ourselves .. with DST.

 

¿Merchants selling more when the sun is up.?

¿Laborers wanting more pay before or after a certain fixed hour.?

¿Inter-national trade-competition.?

DST, is illogical modifications changing from country to

country withing one timezone, and changing from year to year

within one country only to causing problems and misunderstandings.

DST is totally unnecessary. Instead allow for business to be

open, and employers to work, at different hours during the course

of the year if that works better, but stop trying to fool us that

we save daylight and or time.

 

(Rant over)

[Guest Rick Chauvin]

Re: Not Spam, but Notice to change links

 

 

"PCR" <pcrrcp@netzero.net> wrote in message

news:edzoVcoIJHA.1160@TK2MSFTNGP05.phx.gbl

> Rick Chauvin wrote:

>| "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

>| news:ecYMpXXIJHA.4280@TK2MSFTNGP04.phx.gbl

>|

>| [....]

>|

>|>> ..it's almost November, so get your 10 gal frylator out.

>|

>|> Already?.. It seems like I just got rid of the oil from last year ;-)

>|

>| I was told the older you get the faster time seems to go by.

>|

>| I've found it to be true! The years are flying by way to fast.

>|

>| One more question about the time thing. When I had check marked the

>| box to Auto Adjust DST the other day my clock immediately moved ahead

>| a hour, and so I had to move it back and hour to be correct, now this

>| does not mean that come 1/1/09 when it changes automatically it's

>| going to be off an hour again? I assume it will change itself

>| correctly now? Thinking of which, since I live in NH we have this

>| thing where they do DST a few weeks earlier than normal, how is that

>| going to work? I never bothered with paying much attention to all

>| these patches to fix this and that with the time thing, and just

>| assumed it was included in SP3.

>

> That's right-- DST is plus one hour. When DST is over, your clock will

> go back an hour. Very good! But verify your dates are correct (as

> Blanton pointed out currently there is overlap with the old dates-- BOTH

> are in DST now!) using TZEdit.

>

> Run TZEdit, Chauvin, if it will work in XP...

> http://www.softshape.com/cham/manual/tzedit.htm

> TZEdit.

>

> Set it to comply with the following, if it isn't already so...

> http://www.timeanddate.com/worldclock/city.html?n=68

> Current local time in Concord

> .....Quote...................

> UTC/GMT Offset

> Standard time zone: UTC/GMT -5 hours

> Daylight saving time: +1 hour

> Current time zone offset: UTC/GMT -4 hours

> Time zone abbreviation: EDT - Eastern Daylight Time

>

> Daylight Saving Time

> DST started on Sunday, March 9, 2008 at 2:00 AM local standard time

> DST ends on Sunday, November 2, 2008 at 2:00 AM local daylight time

> .....EOQ.....................

>

> Set it to start on the SECOND Sunday of March & end on the FIRST Sunday

> in November. (The precise day won't matter-- TZEdit goes by 1st & 2nd.)

>

> That's the same for everyone, though, who is in DST-- not just New

> Hamshire. Maybe they've stopped the foolishness of doing it weeks

> earlier since the big change back in '07.

 

Thanks PCR for gathering that info, and I've downloaded

TZEdit to do later when I have more time to play more than the moment.

 

Actually now that I've downloaded it I see that I already have it on my

drive in the W98SE partition under tools\reskit\config folder, which came

from the Retail SE CD itself that I had copied over to

c:\windows\options\cabs..

 

Anyway, thanks again for looking up that info which I've saved it all in

its folder.

 

Rick

 

PCR's new name handle is the Timeman :)

>

> --

> Thanks or Good Luck,

> There may be humor in this post, and,

> Naturally, you will not sue,

> Should things get worse after this,

> PCR

> pcrrcp@netzero.net

[Guest Rick Chauvin]

Re: Not Spam, but Notice to change links

 

 

 

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:OOARKdpIJHA.1156@TK2MSFTNGP05.phx.gbl

> "Rick Chauvin" <justask@nospamz.com> wrote in message

> news:O$apdOdIJHA.468@TK2MSFTNGP06.phx.gbl...

>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

>> news:ecYMpXXIJHA.4280@TK2MSFTNGP04.phx.gbl

>>

>> [....]

>

>> One more question about the time thing. When I had check marked the box

>> to Auto Adjust DST the other day my clock immediately moved ahead a

>> hour, and so I had to move it back and hour to be correct, now this

>> does not mean that come 1/1/09 when it changes automatically it's going

>> to be off an hour again? I assume it will change itself correctly now?

>> Thinking of which, since I live in NH we have this thing where they do

>> DST a few weeks earlier than normal, how is that going to work? I

>> never bothered with paying much attention to all these patches to fix

>> this and that with the time thing, and just assumed it was included in

>> SP3.

>

> Yes, it will adjust automatically, though I have no idea about the NH

> rule. It (the NH zone) doesn't appear in my XP-SP3 system, as does IN,

> which

> I think also has its own rules.

>

> SP3 includes the patch to modify the date on which the zones change, so

> it may be as PCR says?

 

 

Okay then, thanks

[Guest PCR]

Re: Not Spam, but Notice to change links

 

Rick Chauvin wrote:

| "PCR" <pcrrcp@netzero.net> wrote in message

| news:edzoVcoIJHA.1160@TK2MSFTNGP05.phx.gbl

|> Rick Chauvin wrote:

|>| "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

|>| news:ecYMpXXIJHA.4280@TK2MSFTNGP04.phx.gbl

|>|

|>| [....]

|>|

|>|>> ..it's almost November, so get your 10 gal frylator out.

|>|

|>|> Already?.. It seems like I just got rid of the oil from last year

|>|> ;-)

|>|

|>| I was told the older you get the faster time seems to go by.

|>|

|>| I've found it to be true! The years are flying by way to fast.

|>|

|>| One more question about the time thing. When I had check marked the

|>| box to Auto Adjust DST the other day my clock immediately moved

|>| ahead a hour, and so I had to move it back and hour to be correct,

|>| now this does not mean that come 1/1/09 when it changes

|>| automatically it's going to be off an hour again? I assume it will

|>| change itself correctly now? Thinking of which, since I live in NH

|>| we have this thing where they do DST a few weeks earlier than

|>| normal, how is that going to work? I never bothered with paying

|>| much attention to all these patches to fix this and that with the

|>| time thing, and just assumed it was included in SP3.

|>

|> That's right-- DST is plus one hour. When DST is over, your clock

|> will go back an hour. Very good! But verify your dates are correct

|> (as Blanton pointed out currently there is overlap with the old

|> dates-- BOTH are in DST now!) using TZEdit.

|>

|> Run TZEdit, Chauvin, if it will work in XP...

|> http://www.softshape.com/cham/manual/tzedit.htm

|> TZEdit.

|>

|> Set it to comply with the following, if it isn't already so...

|> http://www.timeanddate.com/worldclock/city.html?n=68

|> Current local time in Concord

|> .....Quote...................

|> UTC/GMT Offset

|> Standard time zone: UTC/GMT -5 hours

|> Daylight saving time: +1 hour

|> Current time zone offset: UTC/GMT -4 hours

|> Time zone abbreviation: EDT - Eastern Daylight Time

|>

|> Daylight Saving Time

|> DST started on Sunday, March 9, 2008 at 2:00 AM local standard time

|> DST ends on Sunday, November 2, 2008 at 2:00 AM local daylight time

|> .....EOQ.....................

|>

|> Set it to start on the SECOND Sunday of March & end on the FIRST

|> Sunday in November. (The precise day won't matter-- TZEdit goes by

|> 1st & 2nd.)

|>

|> That's the same for everyone, though, who is in DST-- not just New

|> Hamshire. Maybe they've stopped the foolishness of doing it weeks

|> earlier since the big change back in '07.

|

| Thanks PCR for gathering that info, and I've downloaded

| TZEdit to do later when I have more time to play more than the moment.

 

You are welcome. I'm beginning to remember it shouldn't be necessary to

do it oneself, if one has XP. There was a patch in XP for those new time

zone dates that started in 2007, which Terhune converted to something

that would run in Win98. Terhune's thing fixes the dates for every

possible time zone at once. TZEdit does it on a per time zone basis.

IOW, to do them all with TZEdit (instead of just your own), you'd have

to switch to each of the million time zones one at a time & input the

new dates individually for each one. But it can't hurt to run TZEdit to

verify your particular dates, if it will run in XP. I think you're

probably fine now, but Blanton will know best, until Terhune climbs back

out his latest earthquake. Then, he'll know best.

 

| Actually now that I've downloaded it I see that I already have it on

| my drive in the W98SE partition under tools\reskit\config folder,

| which came from the Retail SE CD itself that I had copied over to

| c:\windows\options\cabs..

|

| Anyway, thanks again for looking up that info which I've saved it all

| in its folder.

 

You are welcome. Good luck with it.

 

| Rick

|

| PCR's new name handle is the Timeman :)

 

:-).

 

|>

|> --

|> Thanks or Good Luck,

|> There may be humor in this post, and,

|> Naturally, you will not sue,

|> Should things get worse after this,

|> PCR

|> pcrrcp@netzero.net

 

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

[Guest PCR]

Re: Not Spam, but Notice to change links

 

FromTheRafters wrote:

| Thanks a lot guys - I used to think I knew what time it was,

| now I'm not so sure. :o\

|

| ...and I gotta be at work at 8:30 AM Eastern Daylight New Hampshire

| Savings Time (I think?). Keene, not Spofford but I don't think I cross

| any timezones on my commute. So when do I go to Eastern Daylight

| New Hampshire Wastings Time?

 

Wastings Time is always the same in all the zones I've been in! Don't

worry about that!

 

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net