What was buggy about DOS 4? I ran it for years until I switched to DR DOS 5.

There were two entirely separate DOS 4s

The multi-tasking DOS 4 that had its next release be branded as OS/2

and the other one, a conventional DOS stopgap product

I used dosshell on IBM PC DOS 4.0. I don't remember that feature. Was it added in 5?

I knew viewmax had static windows, but I always wondered why. Now I know.

I have run x11 in 16-color and 256-color mode, but it was not fun. The palette would get swapped when changing windows, which was quite disorienting. Hardware that could do 16-bit color was common by the late 90s.

Fun thing - SGI specifically used 256 color mode a lot, to reduce memory usage even if you used 24bit outputs. So long as you used defaults of their Motif fork, everything you didn't specifically request to use more colors would use 256 color visuals which then were composited in hardware.

Much better to stick to 1 bit per pixel. :-)

Like in Sun SPARCStation ELC. No confusing colors or shades.

1bpp (at low resolution) is still relevant today on epaper screens, though some of them now allow for shades of grey or even color.

Most aren't all that low res either... 300dpi is standard.

I recall it playing the same ad repeatedly during commercial breaks. I think i once watched the same ad 5 times in a row.

Later I subscribed to paramount+ via amazon, and said goodbye to the glitches.

I remember noticing that a teacher in high school had used white-out to hide the marks for the correct multiple choice answer on final exam practice questions before copying them. Then she literally cut-and-pasted questions from the practice questions for the final. I did mediocre on the essay, but got the highest score in the class on the multiple choice questions, because I could see little black dots where the white out was used.

Camping is a viable strategy in many Quake levels, and it is problematic to the point that many servers will kill you if you stay in one place for too long.

Camping is like.. regulatory capture? Stretching the analogy thin here.

Regulatory capture or sitting on an immovable network effect.

Antitrust is like anti camping mods for the server.

First mover advantage.

Can we not do the computer game analogy? it breaks down quickly

Some of the sharks will also do just fine sitting still: https://www.britannica.com/story/do-sharks-really-die-if-the...

If I were to write an OS for a system of that era, I think I would target a game console. Compatibility is a rabbit hole (as I discovered when writing a JIT for Ruby). If you don't have to worry about whether other software runs, there is a lot of room for creativity.

Risk was minimized with the use of segmented memory. A bad pointer would generally only clobber something in the same (data) segment of memory. But there were no segfaults; a program crash means a reboot, which is why so many people optimized config.sys abs autoexec.bat for fast boot.

Come to think of it, maybe things aren't so different today -- if something goes wrong in your container/vm, many teams just wipe it and start from a clean snapshot

I remember that book! I wanted to get a copy but made do with the DOS Programmer's Reference, 3rd ed., which was also very good since beej's interrupt list wasn't available yet or I didn't know about it.

Was it Ralf Brown? beej has C and networking tutorials: https://beej.us/guide/

Yes, Ralf Brown. I guess I'm getting old.

I found a copy of the PC Game Programmer's Encyclopedia (PCGPE) back then but couldn't really wrap my head around most of the articles (especially the 3D stuff and Mode X).