You Linux folks are like North Korean refugees coming to America. "But I thought you were a desolated wasteland ruled over by lizard people, where common folk was forced into slave labor to live for another day?"

+1, I was actually playing and recording a game when my display driver crashed... Windows informed me that it crashed and it had automatically restarted it. The game kept running fine and the recording was okay. Cool stuff.

If you thought that was bad, I know of a production server whose DEFAULT hive is 1,199,046,656 bytes. Fortunately the Samsung printer driver which caused the problem bloated NTUSER.DAT first, so I started getting messages about being unable to load the administrator's profile before messages about being unable to start up, and the errant software has now been excised from the system. (I wish I knew how to remotely shrink the DEFAULT hive of a server; dealing with the NTUSER.DAT problem remotely was bad enough.)

You Linux folks are like North Korean refugees coming to America. "But I thought you were a desolated wasteland ruled over by lizard people, where common folk was forced into slave labor to live for another day?"

You Windows folks are bragging stability when you can go a month without rebooting.

Us Linux users find it unstable when we need to reboot more than once every other year :stuck_out_tongue:

You Linux folks are like North Korean refugees coming to America. "But I thought you were a desolated wasteland ruled over by lizard people, where common folk was forced into slave labor to live for another day?"

Got a Windows 10 laptop and a Windows 8.1 media center PC. Can't remember the last time I rebooted either.

On my work PC, I had made a change to the registry that prevented it from auto-rebooting after getting updates, and I would "delay" the reboot for weeks or longer. Finally, the admins across the street caught on and changed GP so that I am no longer allowed to modify the registry on my machine.

Did you ever identify what processes/services might have been causing this?

tenshino:

I still remember upgrading my Pentium 90mhz with 64 megs of RAM. My buddy was like "what on earth are you going to do with 64 megs of RAM?"

"Launch Netscape faster, of course." :wink:

I had a Packard Bell in 1994, 8MB RAM, 420MB HDD, Pentium 60 (the toaster oven model with the floating point problem, yes). Playing Star Control 3 would stress it after about 20 minutes. Upgraded RAM to 24MB - no more problems. Also, booting to the pre-installed Win 3.11 OS: 15 seconds. "Upgraded" later to Windows 95 - would take over 5 minutes, and that on an OS-only install.

On a different note, this reminds me of my old Netware 4.11 server with "Days Up: 1018" (yes, nearly 3 years) which we had to kill because a power down was required to upgrade the NIC from 10Mbps to 100Mbps. This was 1997.