| Latest revision |
Your text |
| Line 24: |
Line 24: |
| | "Laptop fire" reminds me of that silly but popular phenomenon in space operas: in case the own ship is hit by some enemies "rays", | | "Laptop fire" reminds me of that silly but popular phenomenon in space operas: in case the own ship is hit by some enemies "rays", |
| | inevitably fire will spark from keybords and monitors in the command room. Georg [[Special:Contributions/173.245.53.171|173.245.53.171]] 09:59, 11 February 2014 (UTC) | | inevitably fire will spark from keybords and monitors in the command room. Georg [[Special:Contributions/173.245.53.171|173.245.53.171]] 09:59, 11 February 2014 (UTC) |
| − | : http://tvtropes.org/pmwiki/pmwiki.php/Main/ExplosiveInstrumentation [[User:Wwoods|Wwoods]] ([[User talk:Wwoods|talk]]) 20:17, 11 February 2014 (UTC)
| |
| − |
| |
| − | The usual lot of nonsense in the comments. Why don't we talk about how to improve the explanation? Arguing that browsers remember open tabs, or advertising Linux, or going into excruciating detail how you would react in this situation, is ludicrously off the point. The following points are made by this comic:
| |
| − | * Windows is always banging on about something, usually incredibly unimportant.
| |
| − | * Even if it is important (as here) we may just skim the explanation (because of the first point) and not even realize what it is saying
| |
| − | * Even if we do understand it, we don't want to be interrupted during our work (or our not-work) as we hate being inconvenienced in any way
| |
| − | [[Special:Contributions/108.162.219.58|108.162.219.58]] 21:45, 11 February 2014 (UTC)
| |
| − |
| |
| − | The nonsense is in the comic! The user knows about that the fire is almost impossible from software (mis-)function {{unsigned ip|173.245.53.154}}
| |
| − |
| |
| − |
| |
| − | Possible reference to Microsoft's monthly security patch on the second Tuesday of each month, having been posted the day before the second Tuesday of February 2014. [[User:Quetzalcoatl|Quetzalcoatl]] ([[User talk:Quetzalcoatl|talk]]) 22:23, 11 February 2014 (UTC)
| |
| − |
| |
| − | ;Dubious statement in explanation
| |
| − | "The joke goes further because a software update mostly can't prevent any hardware failures like burning laptop batteries. This specific update is just nonsense."
| |
| − |
| |
| − | It's quite possible for software to put hardware into a state which damages it. In an ideal world hardware would have protection against this but sometimes the protection is either missing or incorrectly set. This sort of thing CAN be worked around in software, if you know what the bad states are you can avoid ever putting the hardware into them.
| |
| − |
| |
| − | Burning laptop batteries are an extreme example but not completely implausible.
| |
| − |
| |
| − | -- plugwash
| |
| − |
| |
| − | :This actually happened a few years ago. A poorly-written driver (among other issues) caused some Nvidia laptop GPUs to get so hot that they'd cause the cases of some laptops to warp. [[Special:Contributions/108.162.219.44|108.162.219.44]] 07:09, 12 February 2014 (UTC)
| |
| − |
| |
| − | :I think the point here is that no matter how severe the problem being fixed, the presence of a "bunch of stuff open" makes a reboot unthinkable. {{unsigned ip|199.27.130.204}}
| |
| − |
| |
| − | Two things: software can absolutely cause/prevent a fire if the hardware is capable of it. Software is what runs the controllers that handle charging for modern rechargeable batteries (well, it may be firmware, but the point is that it's not hardwired). If the charging software doesn't do it's job right, a Li-Ion battery can overcharge and literally catch fire. Likewise, it's software that tells the CPU or GPU to throttle down if it gets too hot and the cooling systems can't keep up. And, at an extreme, in principle the software could perhaps force the hardware to do something out of it's capabilities, like try to direct too much current over some internal connection, thus overheating nearby elements.
| |
| − |
| |
| − | The other thing is that the latest version (or two?) of OS X will auto-resume pretty much everything when you reboot, even if it's a crash rather than intentional. I've had a dozen apps, including a webbrowser with a couple dozen tabs open, running, when my laptop crashed or I accidentally ran it out of juice. When I restarted it everything was back right where I left it, including unsaved documents and comments-in-process on webpages. I suspect that exactly this behavior is part of why Apple implemented that. I certainly know that I'm more inclined to install updates the first time I see them on my laptop for exactly that reason (vs. my desktop, which is running 10.6 and thus doesn't have auto-resume). [[Special:Contributions/108.162.216.31|108.162.216.31]] 15:14, 14 February 2014 (UTC)
| |
| − |
| |
| − | :I should've said: this auto-resume behavior on OS X even succeeds through system updates (and every other update that has required reboot), IME. The only time I didn't get everything back right where I left it was with a major update (10.8.x-->10.9). [[Special:Contributions/108.162.216.31|108.162.216.31]] 15:17, 14 February 2014 (UTC)
| |
| − |
| |
| − | i think that many people are forgetting about OS X's Resume feature. [[User:InAndOutLand|InAndOutLand]] ([[User talk:InAndOutLand|talk]]) 03:04, 13 July 2014 (UTC)
| |
| − |
| |
| − | With Windows 8, there is no option to restart when you want to restart; you either restart immediately, or Windows will do it for you 24 hours later. I've actually lost reports I was typing at work because of this, since I typically just put my workstation on Standby when I leave for the day. [[User:Boct1584|Boct1584]] ([[User talk:Boct1584|talk]]) 17:09, 21 April 2015 (UTC)
| |
