Notably, DOOM crashed before Windows CE.
Doom crash after 2.5 years of real-world runtime confirmed on real hardware
191–200 of 221 posts
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#192Earlier quoted context omitted.
You have 13 years to upgrade to 64-bit ints or switch to a long long for time_t. Lots of embedded stuff or unsupported closed-source stuff is going to need special attention or to be replaced. I know the OpenFirmware in my old SunServer 600MP had the issue. Unfortunately I don’t have to worry about that.
Most 32-bit games won't be updated, we'll have to resort to faking the time to play many of them.
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#1932038 is going to be a fun year.
You have 13 years to upgrade to 64-bit ints or switch to a long long for time_t. Lots of embedded stuff or unsupported closed-source stuff is going to need special attention or to be replaced. I know the OpenFirmware in my old SunServer 600MP had the issue. Unfortunately I don’t have to worry about that.
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#194Earlier quoted context omitted.
Try a Breville PolyScience... https://www.breville.com/en-us/product/csv750 Or if you want something even beefier: https://sammic.com/en/smartvide-xl
It looks like the Breville is the most affordable at $600. Currently I'm paying optimistically $45/90 days or $0.50/day. For the Breville to match that it would need to survive for 3.29 years. Will it?
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#195Earlier quoted context omitted.
The Porsche quote reflects a wider design philosophy that says "Ideally, all components of a system lasts as long as the design life of the entire system and there should be no component that lives significantly longer. If there is such a component, it has been overengineered and thus the system will be more expensive to the end consumer than it needs to be.". It kinda skips over maintenance, but overall most people…
Anyone can build a bridge, but it takes an engineer to barely build a bridge.
I'm chuckling at the thought of barely building something. (All in good fun, thank you.)
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#196Earlier quoted context omitted.
There was an aluminum extrusion company that falsified test records for years. They got away with it because what's a few % when your customer's safety factor is 2. Once they got into weight sensitive aerospace applications, where sometimes the factor is 1.2, rockets starting blowing up on the launch pad. https://www.justice.gov/archives/opa/pr/aluminum-extrusion-m...
Should have resulted in jail time. A monetary fine is no deterrent.
Also a correction to GP: They were payload deployment failures, they didn't blow up on the pad. More here: https://arstechnica.com/science/2019/05/nasa-finally-conclud...
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#197Not a comment on the post, but I sure wish Jira would load even half as quickly as this site.
Perhaps it's hosted on a disposable vape?
Source: https://lenowo.org/viewtopic.php?t=28
badass
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#198Notably, DOOM crashed before Windows CE.
Seriously… I’m most impressed that this PDA kept an application running for 2.5 years. I’d be shocked if any modern hardware could do this, even while disconnected from the Internet.
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#199About a year ago I was looking at Crash Bandicoot timer systems and I found that Crash 3 has a constantly incrementing int32. It only resets if you die. Left for 2.26 years, it will overflow. When it does finally overflow, we get "minus" time and the game breaks in funny ways. I did a video about it: https://youtu.be/f7ZzoyVLu58
Is it common to default to a signed integer for tracking a timer? I realize being unsigned it would still overflow but at least you'd get twice the time, no?
Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware
#200Earlier quoted context omitted.
> Back in the real world, no race team would agree that their cars should disintegrate after one race. Wasn't F1 teams basically doing this by replacing their engines and transmissions until the rules introduced penalties for component swaps in 2014?
If you go back further than that, teams used to destroy entire engines for a single qualifying. The BMW turbocharged M12/M13 that was used in the mid-eighties put out about 1,400 horsepower at 60 PSI of boost pressure, but it may have been even more than that because there was no dyno at the time capable of testing it. They would literally weld the wastegate shut for qualifying, and it would last for about 2-3 laps:…