Half an hour to go.Goodbye everyone, it's been fun crunching with you all. :-)

---

Half an hour to go.Goodbye everyone, it's been fun crunching with you all. :-)

I am ready for rapture, my friends.........2 seconds to go.

---

"Time is simply the mechanism that keeps everything from happening all at once."

That's perfect Julie, I want to be on that party. :))

Being dead feels really weird...

---

Hmm bit of an anti-climax!!

Still the suns over the yardarm so must be time for a quick tot to celebrate still being here!!

---

Already on my second :-)

I just think it totally amazing that the media are reporting, that all around the world, 10% of people were genuinely worried about today. We always knew the wackos and conspiracy theorists would come out in force, but what about the rest of the people? Reports of panic food buying and sales of personal survival shelters abound. I find it all a bit worrying actually. Not surprising that if ET were ever found, judging by this they would keep the lid on it.

Well, the sky is falling here right now in a form of heavy rain LOL

MMM
All I can say is
I GOT WU's.

---

Pluto will always be a planet to me.

Seti Ambassador
Not to late to order an Anni Shirt

Already on my second :-)

I just think it totally amazing that the media are reporting, that all around the world, 10% of people were genuinely worried about today. We always knew the wackos and conspiracy theorists would come out in force, but what about the rest of the people? Reports of panic food buying and sales of personal survival shelters abound. I find it all a bit worrying actually. Not surprising that if ET were ever found, judging by this they would keep the lid on it.

Follow the kitties.......
They know full well that if we ever here on Seti found the WOW signal........
It would be suppressed by our government here.

Because that simply would do away with their way of doing thingys.

Heck, I might not pay my taxes nest year.



Anybody feeling more feathery now?

The kitties did not even panic a bit.........still smiling and bouncy.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Already on my second :-)

I just think it totally amazing that the media are reporting, that all around the world, 10% of people were genuinely worried about today. We always knew the wackos and conspiracy theorists would come out in force, but what about the rest of the people? Reports of panic food buying and sales of personal survival shelters abound. I find it all a bit worrying actually. Not surprising that if ET were ever found, judging by this they would keep the lid on it.

They will have to wait another 13000 boctoon's then LOL

Already on my second :-)

I just think it totally amazing that the media are reporting, that all around the world, 10% of people were genuinely worried about today. We always knew the wackos and conspiracy theorists would come out in force, but what about the rest of the people? Reports of panic food buying and sales of personal survival shelters abound. I find it all a bit worrying actually. Not surprising that if ET were ever found, judging by this they would keep the lid on it.

I am a bit more worried about some other dates. The first was Y2K, but a lot of people put a lot of work into making certain that one went past without too much trouble. Unfortunately, many other people do not realize the amount of work that went on behind the scenes and are basically saying that nothing can go wrong when any of the next technological problem dates rolls around...

---

BOINC WIKI

Hey..... no problemo here.
The kitties are running XP.
The last true OS since NT.

When it dies, so do I.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Well the next problem may well be this

Unix time runs out

---

Well the next problem may well be this

Unix time runs out

Followed shortly there after by MSDOS times runs out in 2044.

---

BOINC WIKI

Remember Y2k

Well it's not over:

2020: January 1: Systems still using 1920 as pivot date fail; Macintoshes running System 6.0.4 or earlier - correct date can no longer be set in Date & Time Control Panel

2030: January 1: Systems still using 1930 as pivot date fail.

2036: January 1: Burroughs Unisys A Series system date fails?

2036: February 6: 2^32 seconds from Jan 1, 1900.

2037: January 1: Rollover date for NTP systems

2038: January 19: Unix: 2^31 seconds from Jan 1, 1970

2040: February 6: At 06:28:16, old Macs' longword seconds from Jan 1, 1904 overflow.

2042: September 17: IBM 370 TOD clock overflows. One source lists this as the 18th (?)

2044: January 1: MS-DOS: 2^6 years from 1980, setting the most significant bit (MSB). Signed variables using this get a negative date.

2046: January 1: Amiga system date failure

2046: June 8: Some Unix password aging fails; 62^2 weeks from 1970.

2049: December 31: Microsoft Project 95 limit.

2078: December 31: MS Excel 7.0 - the last day

2079: June 6: 2^16 days from January 1, 1900

2080: January 1: MS-DOS file dates, displayed with two-digit years, become ambiguous.

2100: Y2.1K; most current PC BIOSes run out of dates; MS-DOS <DIR> renders the file-date years 2100 through 2107 as 99.

2100: February 28: last day of February - NOT a leap year

2106: February 7: Unix: 2^32 seconds from Jan 1, 1970; time overflows at 06:28:16.

2108: January 1: MS-DOS 2^7 years from 1980; file date overflows

2738: November 28: Approximate day of A.D. 1 million (days)

4338: November 28: COBOL-85 integer day 1,000,000 (10^6) exceeds six-digit field

9999: HTTP caching fails.

10000: January 1: Y10K!! Four-digit years fail. More time will elapse between the time this document was written and this date than has elapsed from the beginning of modern human civilization until now.

29602: January 1: MS Windows NT File Systems (NTFS) fails.

29940: New Macs' signed 64-bit time fails (has been OK since 30,081 B.C.!!)

31086: July 31: Internal DEC VMS time fails at 02:48:05.47

60056: Win32 64-bit time fails (started from Jan 1, 1601)

---

That's perfect Julie, I want to be on that party. :))

I'd say, join the party, Grant:)

---

rOZZ
Music
Pictures

---

With each crime and every kindness we birth our future.

Remember Y2k

Well it's not over:

2020: January 1: Systems still using 1920 as pivot date fail; Macintoshes running System 6.0.4 or earlier - correct date can no longer be set in Date & Time Control Panel

2030: January 1: Systems still using 1930 as pivot date fail.

2036: January 1: Burroughs Unisys A Series system date fails?

2036: February 6: 2^32 seconds from Jan 1, 1900.

2037: January 1: Rollover date for NTP systems

2038: January 19: Unix: 2^31 seconds from Jan 1, 1970

2040: February 6: At 06:28:16, old Macs' longword seconds from Jan 1, 1904 overflow.

2042: September 17: IBM 370 TOD clock overflows. One source lists this as the 18th (?)

2044: January 1: MS-DOS: 2^6 years from 1980, setting the most significant bit (MSB). Signed variables using this get a negative date.

2046: January 1: Amiga system date failure

2046: June 8: Some Unix password aging fails; 62^2 weeks from 1970.

2049: December 31: Microsoft Project 95 limit.

2078: December 31: MS Excel 7.0 - the last day

2079: June 6: 2^16 days from January 1, 1900

2080: January 1: MS-DOS file dates, displayed with two-digit years, become ambiguous.

2100: Y2.1K; most current PC BIOSes run out of dates; MS-DOS <DIR> renders the file-date years 2100 through 2107 as 99.

2100: February 28: last day of February - NOT a leap year

2106: February 7: Unix: 2^32 seconds from Jan 1, 1970; time overflows at 06:28:16.

2108: January 1: MS-DOS 2^7 years from 1980; file date overflows

2738: November 28: Approximate day of A.D. 1 million (days)

4338: November 28: COBOL-85 integer day 1,000,000 (10^6) exceeds six-digit field

9999: HTTP caching fails.

10000: January 1: Y10K!! Four-digit years fail. More time will elapse between the time this document was written and this date than has elapsed from the beginning of modern human civilization until now.

29602: January 1: MS Windows NT File Systems (NTFS) fails.

29940: New Macs' signed 64-bit time fails (has been OK since 30,081 B.C.!!)

31086: July 31: Internal DEC VMS time fails at 02:48:05.47

60056: Win32 64-bit time fails (started from Jan 1, 1601)

OMG OMG OMG.........I have so many party dates to attend.......
What's a kitty to do?

---

"Time is simply the mechanism that keeps everything from happening all at once."

What do the Kitties do?

Make sure there is a plentiful supply of bottle/tin openers...

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

What do the Kitties do?

Make sure there is a plentiful supply of bottle/tin openers...

LOL...
I actually went to market and stocked up on multiple tins of kitty food on Wednesday.

I am having some difficulty in teaching them how to open the tins themselves, however.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Remember Y2k

Well it's not over:

2020: January 1: Systems still using 1920 as pivot date fail; Macintoshes running System 6.0.4 or earlier - correct date can no longer be set in Date & Time Control Panel

2030: January 1: Systems still using 1930 as pivot date fail.

2036: January 1: Burroughs Unisys A Series system date fails?

2036: February 6: 2^32 seconds from Jan 1, 1900.

2037: January 1: Rollover date for NTP systems

2038: January 19: Unix: 2^31 seconds from Jan 1, 1970

2040: February 6: At 06:28:16, old Macs' longword seconds from Jan 1, 1904 overflow.

2042: September 17: IBM 370 TOD clock overflows. One source lists this as the 18th (?)

2044: January 1: MS-DOS: 2^6 years from 1980, setting the most significant bit (MSB). Signed variables using this get a negative date.

2046: January 1: Amiga system date failure

2046: June 8: Some Unix password aging fails; 62^2 weeks from 1970.

2049: December 31: Microsoft Project 95 limit.

2078: December 31: MS Excel 7.0 - the last day

2079: June 6: 2^16 days from January 1, 1900

2080: January 1: MS-DOS file dates, displayed with two-digit years, become ambiguous.

2100: Y2.1K; most current PC BIOSes run out of dates; MS-DOS <DIR> renders the file-date years 2100 through 2107 as 99.

2100: February 28: last day of February - NOT a leap year

2106: February 7: Unix: 2^32 seconds from Jan 1, 1970; time overflows at 06:28:16.

2108: January 1: MS-DOS 2^7 years from 1980; file date overflows

2738: November 28: Approximate day of A.D. 1 million (days)

4338: November 28: COBOL-85 integer day 1,000,000 (10^6) exceeds six-digit field

9999: HTTP caching fails.

10000: January 1: Y10K!! Four-digit years fail. More time will elapse between the time this document was written and this date than has elapsed from the beginning of modern human civilization until now.

29602: January 1: MS Windows NT File Systems (NTFS) fails.

29940: New Macs' signed 64-bit time fails (has been OK since 30,081 B.C.!!)

31086: July 31: Internal DEC VMS time fails at 02:48:05.47

60056: Win32 64-bit time fails (started from Jan 1, 1601)

Pivot dates were short sighted.

---

BOINC WIKI