Posted by andreww591 12 hours ago
For example, the "Domain_OS SR10.4 - 01 VUE desktop" is a bit confusing, and may cause people to miss actual DomainOS.
Apollo DomainOS (or Domain/IX, or simply Domain) had many unique and interesting things about it, but disappeared soon after being acquired by HP. It looked more like it might look if you took a programmer who had mostly only seen text terminals, and gave them a megapixel display with pixel framebuffer, a mouse, and the freedom to design the keyboard hardware, and told them to make what they would want to use.
VUE (around when the Unix workstation vendors collaborated on standarding on a common desktop environment) was for HP-UX , which was a very different operating system, and entirely different user experience. More of an early attempt at let's give non-power-users an accessible computer with virtual desktops and everything.
Similarly, Solaris had innovative OpenWindows (including but not limited to a networkable display system based on PostScript) before they got the common desktop environment.
SunOS 4.x (retronym "Solaris 1.x") and earlier could run the earlier SunView environment, which was more like monochrome early Mac than the later Open Look look and feel of OpenWindows.
[1]https://www.facebook.com/groups/retrocomputers/posts/7062462...
I’ve also found source for an AEGIS menu system (mouse, hotkeys) written in Forth.
Not all gear got junked. When I was a teen intern, I got some obsolete Apollos (and 2 logic analyzers and a terminal) from my employer, and other people were also bringing home gear the company "sold" them.
Somewhere, there might well be an industry or university sysadmin or programmer who brought home a box of old QIC tapes, and one of them says "AEGIS" on the label, and it's in a garage/attic.
Also, rumor has it that at one point Boeing physically archived at least one Apollo network, because they apparently take documentation integrity extremely seriously. If that's true, they might have an engineering librarian or someone who could take an interest in making sure any versions of Aegis/Domain they need (and have preserved media for) can run on emulators or something?
Currently the terminal doesn't really process input itself, it just gives the program running the "raw" fd.
If instead the terminal gave the processes a pipe (for instance) and consumed all the pty input itself (and its end of the pipe being a buffer of that content), why wouldn't it be the same?
https://en.wikipedia.org/wiki/Pick_operating_system
My first actual job was working for a local health authority here in the UK, and they had a Pick computer running some database application thing, I think to do with accounting. I had to run the backups. Sorry to be a whinger, I don't mean to belittle the monumental amount of work.
I loved working in Pick BASIC on those systems. So much you could do with "dict items"
I'm also wondering whether/how they include OSes from devices that VICE already emulates, since that could save some work if they want to include OSes of Commodore devices.
1) I run my own systems in emulation and its always educational to see how other people handle configuration and sysadmin type problems. Much like programmers reading other programmer's code for educational purposes.
2) I have a genuine philosophical question which it appears I cannot answer by any means simpler than running it and trying it. Similar to the halting problem LOL. I wonder how the project handles operating systems like MVS/360 where there exists a perfectly good 1960s installation (which I have installed by hand from tape for the experience) however no one uses that IRL because the various MVS Turnkey projects provide seemingly infinite debugged and dependency organized patch sets. There's quite a difference between trying to white knuckle a homemade bare basic MVS/360 from the 1960s vs "MVS Turnkey 4" which basically just works out of the box.
Another example of #2 above is there's DEC PDP-8 OS-8 which technically boots... but the most common distro had a non-working but trivially fixable FORTRAN compiler (IIRC the runtime package filename was wrong or something similar). There's a lot of fun customization.
Another example of #2 above is I wonder how the author handles RSX-11M, distribute the ancient unpatched unmodified OS from DEC or ship something like the Billquist distro, or does the author ship the PiDP-11 RSX-11M (or is PiDP-11 shipping the Billquist RSX-11 distro now?)
I guess for people not into retrocomputing it would be like claiming some rando RedHat .iso from the 90s is "The" Linux operating system. Well, its "a" linux from one instant in time... Likewise there seems to be no "The" MVS/360 operating system there's a zillion possible local installs of all capability levels and eras, all very different and fun.
I think I got it on an early Packard Bell Pentium system in 1994. I remember I used it even though it sucked because it seemed a little better than Windows 3.1 mostly due to the fact it didn't try to look like a functional windowing operating system. Once I got my hands on Win95 beta, I never ran it again. Of course, early Win95 also sucked as a real OS but it was enough better than Win 3.1 that I could slowly begin to transition off my beloved Amiga 2500.
Run System 7 in an emulator and the menus look right, but the input feels wrong. What we're really preserving in these collections is the screen output, not the interaction. Which is fine for an archive — just worth being honest it's a museum of appearances, not of use.
It's one of those strange memories from my youth that I've been unable to confirm as an adult.