im a noob at qbasic but for the y2k+ problems couldint u just keep your clock behind that point untill its fixed..?
Yes, but then your datestamps would be wrong.. this brings problems to large corporations..The homeuser rarely have problems with this kind of things, unless you never ever update.. But most users either update, or have the knowledge to know it'll go wrong, or atleast what went wrong when it does if they still run older machines..
Statistics: Posted by Z!re — Sun Oct 16, 2005 10:19 am
]]>
]]>
0_o
Statistics: Posted by {Nathan} — Thu Oct 13, 2005 3:51 pm
]]>
Basically, he wrote a bunch of random crap down, and now people "interpret" it to mean all kinds of crazy stuff..
Some of the predictions are fun/interessting.. but they dont account for anything..
Statistics: Posted by Z!re — Thu Oct 13, 2005 12:18 am
]]>
Actually, Nostradamus never said anything really.. It's all about interpretation.. Also, his dates are a bit.. weird.. sometimes.. most "famous" is the 35th of december.. go figure..Well, he also said...2034 is when the world is going to end.
Nostradamus said so.
3755 - world destroyed by asteroids according to Nostradamus.
3797 - world consumed by an expanding Sun according to Nostradamus.
Which is it???
And either all, or none of his predictions so far has turned out correct.. like I said, interpretation..
Statistics: Posted by {Nathan} — Wed Oct 12, 2005 7:56 pm
]]>
Well, he also said...2034 is when the world is going to end.
Nostradamus said so.
3755 - world destroyed by asteroids according to Nostradamus.
3797 - world consumed by an expanding Sun according to Nostradamus.
Which is it???
And either all, or none of his predictions so far has turned out correct.. like I said, interpretation..
Statistics: Posted by Z!re — Wed Oct 12, 2005 6:39 pm
]]>
2034 is when the world is going to end.
Nostradamus said so.
Well, he also said...Nostradamus said so.
3755 - world destroyed by asteroids according to Nostradamus.
3797 - world consumed by an expanding Sun according to Nostradamus.
Which is it???
Statistics: Posted by Patz QuickBASIC Creations — Wed Oct 12, 2005 5:18 pm
]]>
Statistics: Posted by Nemesis — Tue Oct 11, 2005 4:12 pm
]]>
]]>
*****
Statistics: Posted by moneo — Tue Oct 11, 2005 2:11 pm
]]>
Ya, just saying..
Statistics: Posted by Z!re — Tue Oct 11, 2005 1:36 pm
]]>
Thanks.
Anybody else know of more Y2K holes out there?
*****
Statistics: Posted by moneo — Sat Oct 08, 2005 7:47 pm
]]>
On January 1st, 2028, any computers that use the "28 year setback" trick to avoid Y2K will fail to display time properly.
On January 19th, 2038, at 03:14:07 GMT, the seconds counter used for date/time information in UNIX and C and C++ will reach 2,147,483,647, which is the largest number which can be stored as a 32-bit signed integer. This will cause some problems in certain programs which expect the date to never be prior to January 1st, 1970.
On January 1st, 2100, we'll see "Y2.1K"...current PC BIOS clocks will run out of dates. I guess this means they'll no longer get laid either.
On March 1st, 2101, any system which is compliant at this point in time is fully date compliant up until December 31st, 9999.
Source.
Statistics: Posted by Nodtveidt — Fri Oct 07, 2005 11:55 pm
]]>
Anyway, if you like, I have had a page posted on my dust covered web site now since 1999 ? it?s still there ? and it contains my rant from that year on the very topic of what was then been called the (ugh) ?Millennium Bug? (cringes ? I hate that term). Read it if you like, here: http://members.aol.com/uwlabs/y2k.htm
I find it interesting to see a current discussion concerning something that happened over five years ago - regarding it as long-lost history - when it seems just like yesterday to me. Of course I'm also so old I remember wearing a black plastic Texas Instrument LED watch to High School, AND manually making IBM 80-column punch cards in 11th grade Algebra2 class! Then the turn of the century was more than a score hence.
Statistics: Posted by UWLabs — Fri Oct 07, 2005 6:54 am
]]>
Statistics: Posted by Rattrapmax6 — Thu Oct 06, 2005 8:45 pm
]]>