4 ms·
You are being reminded that Microsoft code was always batshit insane, and only ever just barely worked. In the W95/98 era, they succeeded in redefining "crash"
by ncmncm 7y ago
You are being reminded that Microsoft code was always batshit insane, and only ever just barely worked.
In the W95/98 era, they succeeded in redefining "crash" to mean, not that the program or OS stopped, requiring a restart, but rather that restarting wouldn't work, and you would have to re-install the OS.
I still recall my shock at learning of this re-definition. I had said that Linux (of the day) would hardly ever crash, and the person said he often went weeks without need to re-install his OS. Crashing, in the old sense, was a several- or many-times-a-day event, and hardly deserved mention. People berated themselves for not having saved their work recently enough. Sometimes they complained of bluescreens while saving, and would alternate saving to two different files, so one might survive.
- b_tterc_p 7y agoCurious if this resonates with others. That is hard to believe but I wasn’t around to have an opinion.
- altcognito 7y agoI was around and this doesn’t ring a bell.
- naikrovek 7y agoWindows OS quality has varied quite a bit, and I think it is unfair to call the majority of Windows "batshit insane." It isn't a knowledgeable opinion and it isn't necessarily fair, either. There ARE plenty of mistakes in the history of Windows, don't get me wrong. Microsoft has gone well out of their way to keep backwards compatibility from release to release, even if it means other features won't be added. Every few years they break this trend and they give everyone multiple years of notice. There are often very good reasons for some of the things that appear to be insane, as any regular reader of Raymond Chen's "The Old New Thing" blog will testify. Arguably, if anyone I know of would have a valid opinion of Windows' level of insanity, it would be Raymond Chen, as he's had his hands in the Windows source code for 2-3 decades at this point. He continues to work as a developer at Microsoft, so I'm quite confident that the level of "batshit insanity" in Windows is quite low and getting lower by the day.
- ncmncm 7y agoPeople who lived it could be forgiven for wanting to forget. I never had any direct contact with Microsoft code, but was surrounded by people who did. It should be noted that Windows NT/Vista/XP/7/8/10 are a different lineage, and carry very little code from the 3.1/3.11/95/98/Me codebase, aside from some UI subsystems. There was not much contact between the two groups, and (I was told) a fair bit of bad blood. If you find somebody claiming that crashes were not, at minimum, a daily event on W95, you may commiserate over their amnesia. Many people ran Windows programs under OS/2, where only the programs would crash, not the OS, and so less often, and they did not need to reinstall the OS.
- acqq 7y ago> I never had any direct contact with Microsoft code So your claims are rather reflecting your memory of your interaction with the people who did have the direct contact, and not the actual state. In reality, Windows 3.0 and 3.1 is hugely different from 3.11, and from 95/98/Me. Starting with 3.11, there was actually the of code avoiding the lower lever calls to BIOS and DOS if possible (if the hardware allowed) but using the new 32-bit code instead. The stability of the OS was definitely not as you describe, one could surely use the system for days without having the system crashes. The system's design was the effect of the engineering goal of having a system that can work with very small amounts of memory, compared to the competing safer systems. With more memory available on the computer to implement the "hardware" memory protection one was able to use the "safer" systems like NT. The wide use of that lineage vs. NT was a strong reflection of the market needs: people did have the computers with too little RAM for the "safer" systems but still wanted to run the programs that had the functionality they needed. Additionally, the "safer" system not only demanded more RAM, but were often for some tasks less convenient. A lot of users who "had to reinstall the system often" were actively doing "unhealthy" steps themselves: "trying" the software they didn't need, which did the interventions on the system which damaged the system. The programs running on the OS (even on NT) typically did tend to crash regularly, however. Especially including the biggest like Microsoft Word. Fascinatingly, that was by design: it was the "knowledge" of the managers that delivering fast the new versions of programs with more features was more important than the code correctness. Just like in the web world more recently...
- rswail 7y agoGetting an 80286 or 80386 out of 8086/8088 mode to address more memory required access to the A20 address line. Which IBM added to the keyboard controller on the motherboard. Which lead to the A20 hacks necessary to access memory above 1MB (let alone the hacks already in place to access over 640K). Note that this hack has required CPU support up to Intel Haswell which is only 5-6 years ago. https://en.wikipedia.org/wiki/A20_line https://en.wikipedia.org/wiki/A20_line
- consp 7y agoActually, the hack is to fix the incorrect behavior of the processor in real mode (not lowering line 20 to 0). The fact that it was put into the keyboard controller was probably as it is a simple soc[1] with (in the case of a keyboard controller) about 256 bytes of ram and about 1-4K of rom. Which resources was probably still available to the motherboard designers without complicated logic or additional components. It is not the weirdest fix to imagine. note: modern variant of the keyboard controller can sometimes be flashed which is fun to play around with. [1] https://en.wikipedia.org/wiki/Intel_MCS-48 https://en.wikipedia.org/wiki/Intel_MCS-48
- Frondo 7y agoI was also around and never heard of anyone describing "crash" to mean "need to reinstall OS". Always in the same Linux sense, which absolutely was a breath of fresh air by comparison.
- EvanAnderson 7y agoI'd be interested in a reference for this "crash" definition you're describing. It was common parlance in the late 80's in the DOS-era PC circles I ran in to use the word "crash" to mean a physical fault with a hard disk drive (probably in reference to a head crash) and I've seen it picked-up by the novice community over time. I've never seen any Microsoft-provided reference that forwarded such a definition. None of this is to say that MS-DOS and Win3.x isn't a bizarre maze of assembly-language hacks. It was unreliable as hell, though the entire PC software ecosystem and playing fast-and-loose with tricks like directly accessing hardware was as much to blame as anything.
- partitionator 7y agoI've had things happen to old versions of Windows that have completely blown the system installed to the C: drive. This was definitely a thing. You can recall an artifact of folk proof in this detail, by recalling a lot of more technical users and professional IT/desktop support staff in computer labs using C: as a system drive, and D: as the work area containing user files, even if it was a single user machine. Losing the C: partition was a bad burn, bad enough that you didn't let it happen twice. Years later, even in the Vista days, I had a partition destroying error from a truly innocuous action (like renaming some file; and that NOT being just a coincidence, but a repeatable error with Google results), and had a flabbergasted flashback to a prior C: drive implosion, that reminded me why you always divide the bootable system install off to its own untouched C: partition, and always only put the things you care about on the D: drive, and create lots of backups. This was real. Never touch C: and don't trust it. Never put anything that matters in the C: partition.
- pdkl95 7y agoOne of the ways Windows would corrupt itself was an optimization it used to reduce the size of the VM swap file. On many OS, when a program is loaded into memory the executable code pages of memory are the same as any other memory page: the VM might write the page to the swap file, and later reload that memory from the swap file to restore the memory page. On windows, code pages were not sent to the swap file, because that data already had a copy of that data in the program's original .exe file! Instead of writing the memory page to the swap file, simply freeing the memory was much faster and saved a lot of space on the disk reserved for the swap file. The code pages were supposed to be read-only, but some kind of bug(s) would cause the memory pages to be seen as normal memory, where writes would mark the page as "dirty" and eventually the VM would write those changes to the swap file. Unfortunately, for code pages, the "swap file" was the original .exe, so the changes to the memory page would corrupt the .exe, probably requiring it to be reinstalled. > always divide the bootable system install off to its own untouched C: partition They might have been using 'ghost' to restore the C: partition over the LAN at boot time. This was very common in professionally-managed settings.
- deleted 7y ago[deleted]
- fortran77 7y agoThat's simply not true. Many, many people got their start with Microsoft Basic, Microsoft Visual Basic, etc. People still make a living knowing the very reliable Microsoft Excel.
- interfixus 7y agoRan a fair bit of Windows 95 back in the day, and a bit of 98 before ditching and going all-out Linux. Did weird shit to those systems, had my liberal share of blue screens and reboots and facepalms and shouting at my CRT. Also frequent reinstalls because things inevitably grew crufty and polluted beyond repair. But these were planned and deliberate. I never once had a system die on me.
- Spooky23 7y agoYou probably, by luck or design, bought decent gear. The biggest killer of windows systems was drivers and bad hardware. The average punter bought some garbage device at retail and plugged in his software modem, software printer, and god knows what kind of software. Those boxes died. Enterprise software was usually even worse, as companies were uniquely unskilled to produce it.
- ncmncm 7y ago"Crufty and polluted beyond repair"? But still booted? Pro-active maintenance must have intervened before the fatal rot.
- geocrasher 7y agoI disagree with your redefinition of "crash". I remember the 90's quite well, and have spent lots of time supporting everything from DOS 3.3 on up to W10. That's not to say that there weren't those people for whom "crash" meant "OS reload". Usually when somebody said their computer "crashed" and they had to reinstall their OS I discerned a few possibilities: 1) the user broke their system because they were installing anything they could and are blaming MS for their troubles 2) the user has no idea how to fix anything so they default to a reinstall because they think it's easier than finding the fix. In a pre-Google/StackOverflow world, this may have been true. 3) The user was on a quest for absolute stability, and was superstitious about uninstalling/reinstalling drivers etc. As for the "only ever just barely worked" statement, I strongly disagree. Yes, a lot of maintenance and good habits were required, but it wasn't outside of the realm of possibility to have a stable Windows ME. I know, because I'm one of about 5 people who ever liked Windows ME. I thought it was a decent OS, as long as you figured out that the Device Manager had 10 copies of every driver, unhid them, and removed them all and rebooted.
- ncmncm 7y agoI guess you don't remember when it came out that a Windows 95/98/Me machine, running nothing at all, would crash spontaneously after, what? 39? days, when a time counter rolled over. No one had noticed, in years prior, because: No one had ever got one to run that long. Boeing 787s need to be fully power-cycled every few months, for identically the same reason, although its time counter ticks less frequently. They would fall out of the sky, otherwise. It is just lucky somebody noticed before it happened, because there has otherwise been no need to reboot it.
- silversconfused 7y agoOur win95 print server ran for years unattended with a simple nightly reboot set up in the task scheduler.
- nicoburns 7y agoSo that's what was wrong with ME. I still reflexively ctrl-s after every sentence due to a bad experience growing up on an ME system.
- LocalH 7y agoI wouldn't say always. Their 8-bit BASIC was decent.