But the most significant thing I remember was DirectX. The first game I ever saw in Windows (I dual booted to DOS for gaming, strictly) was something called The Hive and I just remember thinking "Games in Windows? That'll never catch on. Nice try M$".
I remember "The Hive". That game's installer updated my video driver without asking and caused serious breakage. I've had a grudge against that game ever since. 20 years later the disc case has sat preserved and untouched on the shelf, like operating system Kryptonite.
I need to set up a Win95 machine, and if I do, I guess maybe I'll install Hive again, just for old times sake. I don't think it was much of a game, but I guess I can play it once more after 20 years. But if it breaks my drivers again I'm breaking the disc.
Maybe installing a video driver newer than what the game provided will prevent the problem?
It might. Anything I put together today would be different hardware than our family PC back then, and the drivers will probably be newer. I don't know if Hive compares the driver dates or not. I hate how it presumes to update without asking, but there's certainly a good chance that it might leave the drivers alone if they're newer.
Back then I needed to use an older video driver, because the newer one was unstable on my system. Really, we just had an unstable motherboard, but for whatever reason the older driver was working okay while the newer one induced lots of crashes.
It seems like I would have just reinstalled the old driver at that point. I don't remember if I was able to do that, or if it caused some other lingering problem.
This was on one of those cheap PC-Chips 486 boards with the anonymous chipset with a sticky label on it.
The situation with Hive was kind of ironic because I had already decided that DOS games were crashing all the time, while Windows games were stable. That was why somebody gave me a Windows game for Christmas, but then it went and destabilized Windows.