virtual memory 4464
that was POK and the majority of the customer base. however, a lot of virtual machines, virtual memory, paging, interactive computing, networking, multiprocessor and other...
see melinda's paper on the development of virtual memory and virtual machines in the 60s
part of it was mit had chosen ge for ctss follow-on multics.
a quote from Melinda's paper about some of the commitment to 360-67 and TSS-360: What was most significant was that the commitment to virtual memory was backed with...
the science center
had added custom virtual memory to 360-40 and built cp-40 supporting virtual machines and paging-swapping.
the 360-67 was official product with virtual memory support, built for tss-360. however, the science center ported cp-40 from the 360-40 to 360-67 renaming it cp-67.
univ. of michigan also developed MTS (michigen terminal system) that supported virtual memory on 360-67 (also paging-swapping).
however, there was at least one effort that modified os-360 to utilize the 360-67 virtual memory hardware w-o providing paging-swapping support. os-360 was nominally a "real address" operating system where applications were allocated contiguous areas of real memory. long running applications frequently resulted in storage fragmentation, there would be enough real memory to run an application but not located contiguously. the use of virtual memory hardware allowed discontiguous real storage to be appear to be contiguous.
for some drift ... misc posts about doing page replacement algorithms in the 60s (i.e. deciding which pages should be moved between real memory and disk).
--
Alt Folklore Computers from Newsgroups