Millisecs() = 0

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

Shifty Geezer

Millisecs() resets to zero in think it's 30 years time. It's a similar problem to the Y2K bug of clocks, but moreso. The timer counts up to umpteen billion and then rolls-over, at which point timer based functions go pear-shaped and all hell breaks loose and just like the year 2000, all computers stop and the world is thrown into anarchy and a new Dark Age as we regress to animals without our computers working.

Just looked it up on the Wikipedia
http://en.wikipedia.org/wiki/Year_2038_problem