1. 7
  1. 4

    Never heard of this OS, but the manual is written in an informal, humorous style. I recommend reading bits of it for entertainment, as well as historical education.

    The User’s Guide to Micronix was written in an atmosphere of friendly chaos by John VanderWood and myself. Part of the chaos revolved around a change of attitude that made it possible to rewrite the old manual in a much more amiable style. That made us happy. But, naturally, this project was scheduled to be finished before it even began. The goal, a complete and easy understand User’s Guide, was like a mirage shimmering in the distance.

    Result: the majority of the User’s Guide is pretty good, with the possible exception of Tutorials, which we haven’t had time even to look at yet.

    1. [Comment removed by author]

      1. 4

        I must say I’ve never been so entertained when reading a Unix manual or really any sort of manual, which was partly why I posted it. It also as informative as it is entertaining, a rarity. A little research shows the author, Rik Farrow is alive and well and ended up having somewhat a career in writing documentation.

        The best Unix documentation that I’ve ever seen, however, is the manual for Mark Williams Company Coherent, but without the quaint and humorous non sequuntu.

        1. 3

          Sometimes I think I’m the only person who both remembers Coherent and remembers it fondly…

          …also TIL that the plural of “non sequitur” is “non sequuntu”…

          1. 1

            I think my only frustration with coherent was in trying to port a SysV application to it.

            When you consider what it ran on, what was I expecting? :)

        1. 1

          Also, some interesting info with some source code at: http://www.classiccmp.org/cpmarchives/cpm/Software/rlee/M/MORROW/MICRONIX/

          1. 1
          2. 2

            Well-written guide in humorous style. One part that jumped out at me is the section trying to explain OS’s and I/O to lay people using driving metaphor with Interstates and cars. It was pretty good. I don’t see many try that. I usually explain it in terms of a group of people working together in a company on a product. They each speak different languages. They need translators to work well together with hardware speaking diverse languages, translators called “drivers” helping them talk to the OS, and the OS provides full, standard services to people in English language that most understand and can work with.