4 ms·
Ahh, those transitions from the days where you could just turn off you DOS, until the computer could "turn off" by itself (I know, not that hard off, just a sof
by woliveirajr 11y ago
Ahh, those transitions from the days where you could just turn off you DOS, until the computer could "turn off" by itself (I know, not that hard off, just a soft button off)
- onre 11y agoSMARTDRV /C
- robert_tweed 11y agoAnd not forgetting the days of MFM hard drives, when you had to run the "park" command before turning off, or risk crashing the heads.
- nsxwolf 11y agoI remember seeing that hand-written warning taped onto IBM PCs.
- digi_owl 11y agoWe seem to be heading back towards those days. The property that made this possible was that DOS had little "state" to save before going bye bye. And these days you get much the same with ChromeOS. Heck, was there not someone in the -sec community arguing that state was to be considered bad?
- JBiserkov 11y agoThere was a very funny video where the main character's Chrome book gets destroyed every few minutes and a new one is delivered and he just keeps on working.
- digi_owl 11y agohttps://www.youtube.com/watch?v=lm-Vnx58UYo https://www.youtube.com/watch?v=lm-Vnx58UYo Seeing that original browser only UI makes me nostalgic.
- woliveirajr 11y agoI don't if it is bad, but I think that it just means that some computation isn't being done in full, and that's why you have to tell it to finish. Explaining better: any program should have the information saved when you click it to save, or at some specific time. If I don't save, ok, no problem loosing it. But opening a word processor and then turning the computer off shouldn't make the processor crash, or go through some recovery, or complain about something.