Antinomy November 8, 2013, 4:55:07 AM GMT Thank you, Scotty! GENiEBEN, no, it's only 8.5 hours http://hwbot.org/submission/2448531_ Do you know how to deal with the "cheat detected" bug when system time ticks over midnight? Wanna know for even slower and older things like 486 BTW, Super pi 32M on Winchip CPUs take about 12 hours.
GENiEBEN November 8, 2013, 7:15:21 AM GMT Thank you, Scotty! GENiEBEN, no, it's only 8.5 hours http://hwbot.org/submission/2448531_ Do you know how to deal with the "cheat detected" bug when system time ticks over midnight? Wanna know for even slower and older things like 486 BTW, Super pi 32M on Winchip CPUs take about 12 hours. No, but I bet Karl knows something. What I would try is to change system time every 23 hours back to the time the application started+1hr.
TerraRaptor November 8, 2013, 7:59:40 AM GMT I remember Karl has written that he was changing time every day))
Comments
You've got more patience than I.
I take it we're going to see 1024 in about 3 months? :
Thank you, Scotty!
GENiEBEN, no, it's only 8.5 hours http://hwbot.org/submission/2448531_
Do you know how to deal with the "cheat detected" bug when system time ticks over midnight? Wanna know for even slower and older things like 486
BTW, Super pi 32M on Winchip CPUs take about 12 hours.
No, but I bet Karl knows something. What I would try is to change system time every 23 hours back to the time the application started+1hr.
I remember Karl has written that he was changing time every day))
Log in or register to comment.