Forums Bug Reports mIRC timestamp bug (6.16)

This may affect more than just 6.16, but what the hell. Anyway:

System: Windows XP Professional, SP1 , mIRC 6.16
Reproducable: Always

(1) Turn timestamps on while you're on any IRC network, then set your PC's clock to 9-January-2038 3:14:05 AM.

(2) Wait for 5 seconds.

(3) Type something / wait for someone else to type something or for an event to occur.

(4) Note timestamps are no longer appearing.

This is most likely something to do with the Unix Epoch Bug, reference here: http://www.deepsky.com/~merovech/2038.html

I can't reproduce this.

mIRC 6.16
Windows XP Home Service Pack 1

I can't reproduce here either.

mIRC 6.16
Windows XP Professional Service Pack 2
AMD Athlon XP 2200+

Ya know, if I were to set my television right on the edge
of my swimming pool, just a hair away from falling in,
then go get myself a drink, sit down and relax and wait
for a strong enough breeze to blow in, the television
just might fall into the swimming pool. Can anyone
reproduce this?

Damn buggy TV's, I must go report this bug.

I couldn't reproduce that exactly, but I found that timestamps disappear at Jan 18 2038 21:14:08 (my time zone is -6:00 -- adjust the time for your time zone), which is when $ctime actually hits 2^31. (//echo -a $asctime($calc(2^31-1)) and add a second.) Anyway, since it's not 2038, I wouldn't worry about this for a few decades. If mIRC hopes to reach its 43rd birthday, though, this would need to be fixed.

If this is indeed a bug with mIRC, then Khaled (or whoever takes over for him, has about 3 decades in which to get it fixed...personally, I'll be thankful to still be alive and healthy in 3 decades (I'll be in my 70's at that point)

Reproduced with my Phillips K9, my Sony 32Inch, but my Plasma Flat Screen seemed to be uneffected, maybe because i had it lying flat ?

Oh yes, my mistake. What I actually did to find this bug was just set my year clock to 2038 - what with what the current day/month is, the problem started. I know it affects Trillian on the date I set, so I assumed mIRC was the same.Sorry, guys =P

But yeah, this bug is real and destroys the timestamping. Only got 33 years, best get on a fix

I read somewhere this week, at a certain point like 20-something unix time will mess up on alot of machines, i could be wrong, but when i read this it's the first thing i thought of.