• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Lol...everyone was scared for year 2000...set ur computer to 2098 an see wut happens...

N

niwi7

Golden Member
I did that by accident 1 day w/o realizing it

i boot up today

i get like 5 random programs givin me messages saying the usual you must sned error report to microsoft and this program must end error

and then other randoms like windows media player started doing the same thing! i had no idea what was wrong so i downlaoded windows media player 9 instead of 8 aand it gave me an error saying set your clock to a lower date...hahahahha wow was i stupid


but by the time 2098 comes....our computers will d13 😀
 
Hahahaha!!! That's awesome. The instant I hit accept, Trillian died on me, then one by one, a bunch of my background apps died too. "Instruction at blah blah.... could not be read."
 
Originally posted by: dmurray14
Originally posted by: EyeMWing
I've run in the year 3200 with no problems. Not sure what the heck your stuff is doing.
Click to expand...

right, because windows will only go up to 2099 😉
Click to expand...

Who said it was Windows? We all know that Windows will cease to exist in the enthusiast world with the introduction of Longhorn, which is 2006.

I set my BIOS date to 3200, which caused no problems whatsoever. Patching software for date ranges is a simple matter. It's getting the hardware to do it properly that's the problem.
 
Actually, the failure you are seeing comes up long before 2098.

The key date is Jan. 18 2038. I forget what time exactly some time in the afternoon.

Oh, and if anyone is still using old Apple IIs, the latest year ProDOS & GS-OS can handle is 2004.

 
Originally posted by: glugglug
Actually, the failure you are seeing comes up long before 2098.

The key date is Jan. 18 2038. I forget what time exactly some time in the afternoon.
Click to expand...

As it stands right now under Linux (Debian in 2002), the date command is unable to work after January 18th 2038 at 9:14PM and 7 seconds Central Standard Time.

Text

*edit* it's not just linux, that's just the first source I found. It has to do witht he 4 byte date storing system.
 
sry for my nubishness

googled longhorn


its made by microsoft


so...yea i guess it will replace windows...
 
my first thought was "eh, ill have a new machine by then anyway"
and then i read the rest of this thread and i thought "oh yeah, ill be dead"
 
im sure some dude will come out with a patch for whatever OS is around in 2038 and all will be hollericious
 
Originally posted by: MartyMcFly3
im sure people will be using this computer 95 years from now too
Click to expand...



Read a little more of the thread.... It's only 33 years and a month or so away... 🙂
 
Originally posted by: Indolent
Originally posted by: glugglug
Actually, the failure you are seeing comes up long before 2098.

The key date is Jan. 18 2038. I forget what time exactly some time in the afternoon.
Click to expand...

As it stands right now under Linux (Debian in 2002), the date command is unable to work after January 18th 2038 at 9:14PM and 7 seconds Central Standard Time.

Text

*edit* it's not just linux, that's just the first source I found. It has to do witht he 4 byte date storing system.
Click to expand...

It's all about the epoch
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top