7 ms·
I knew guys who ran VMS systems out of their homes, back in the 90's. It was fairly accessible.
by icedchai 7y ago
I knew guys who ran VMS systems out of their homes, back in the 90's. It was fairly accessible.
- bediger4000 7y agoHow many of them had the manuals? Very few. The famous "Orange Wall of Manuals" was often secreted away, for the wizards to consult, but not for the masses to enlighten themselves with.
- icedchai 7y agoOne guy, at least, had manuals. VMS also had an excellent help facility.
- bediger4000 7y agoOh, sure. What was the format of an executable file? Nostalgia is a trap. Wallowing in the idealized "good old days" blinds you to the true scope of history and cuts you off from progress.
- icedchai 7y agoHah. I've forgotten. Retrocomputing is just a hobby of mind. It's fun to play around with those old systems.
- bediger4000 7y agoAs near as I could ever find, the format of a VMS executable file did not appear in the DEC manuals. I meant that as a commentary on the "VMS had great docs" sentiment. At one point, I was convinced that understanding the format of an executable file (a.out, COFF, XCOFF, Mach-O, ELF, .com, .exe, PE, etc) was important to understanding the operating system itself. I spent a fair amount of effort and some money buying books trying to find the VMS executable file format. Couldn't find a hint.
- vaxman 7y agoIt did, sigh. It was in the LINK'ER documentation. RSX/VMS was all about object modules being shared between concurrently running applications in separate user spaces (because RAM was crazy expensive and DISK was crazy slow and expensive). The format for runtime libraries, executables and memory-mapped sections in general descended from the PDP11 a bit and I believe it changed radically (for the first time in decades) with the introduction of the 64-bit Alpha architecture under "Open"VMS.
- bediger4000 7y agoThank you! I'm serious, I bought several books and inquired of VMS experts (on usenet, that long ago) looking for anything about VMS executable format. This is the first hint I've gotten.
- bediger4000 7y agoAlas, the LINKER documentation (https://www.itec.suny.edu/scsys/vms/ovmsdoc073/v73/4548/4548pro_contents.html https://www.itec.suny.edu/scsys/vms/ovmsdoc073/v73/4548/4548...) I can find only includes a description of the "object language" for VAX (https://www.itec.suny.edu/scsys/vms/ovmsdoc073/v73/4548/4548pro_contents_001.html#toc_appendix_a https://www.itec.suny.edu/scsys/vms/ovmsdoc073/v73/4548/4548...) and Alpha (https://www.itec.suny.edu/scsys/vms/ovmsdoc073/v73/4548/4548pro_contents_002.html#toc_appendix_b https://www.itec.suny.edu/scsys/vms/ovmsdoc073/v73/4548/4548...). It does say that Itanium VMS used ELF format executables. So I think it's still an open question as to whether VAX/VMS or Alpha/VMS executable file format ever had documentation. How did ELF format files play in VMS' idea of process-as-elaborate-address-sapce, where running a command involved reading or mapping in an executable, and then jumping to the entry point? Or did I64 VMS abandon the unusual VMS process model?
- vaxman 7y agoI have a friend who converted a coat closet in his house into a datacenter large enough for a MicroVAX II with air-conditioning. He had run terminal lines to every room in the house to plug-in VTs. That said, he had a legit reason for doing it. Basically writing code 24x7 a day for his customers in those pre-laptop days.
- icedchai 7y agoCool! I'm looking to pick up a VAX or AlphaStation on EBay.