MCP: Difference between revisions

Line 26:

After dropping their CMOS line and completing the transition to commodity Intel, Unisys made MCP available free for personal use to run from Windows 7 or 10 64 bit as "MCP Express". ~~ough~~ I didn learn of this until 2019Q3 and didn bring it up till end of Q1 '20 (version 5). It has to be replaced by a new download every July 31st.

After dropping their CMOS line and completing the transition to commodity Intel, Unisys made MCP available free for personal use to run from Windows 7 or 10 64 bit as "MCP Express". I didn learn of this until 2019Q3 and didn bring it up till end of Q1 '20 (version 5). It has to be replaced by a new download every July 31st.

Thus, after 35 years, I now have nads on a current MCP (18) system and that opens a role for the Unisys MCP in the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Usages like ODT, DMS II or MARC unambiguously refer to the Unisys product line as we never intended take more than inspiration from it.<ref> "CANDE", "WFL", and "MCP" are the actual overloads, "SPO" isn't really used in the modern Unisys culture, it's been lost from the mainframe days, so the smalltalk thing I'm doing doesn't map to anything specific, although functionally MARC and the ODT would be the analogs. The original SPO was just an ODT with supervisor permissions. Whose thing, mine or Unisys that is referred to by the overloaded terms will be clear in context (within Unisys MCP or not) and use the same "Unisys" modifier where needed.</ref>Much of the base mainframe stuff is available in the Windows based product and updated for the current epoch, though obviously it's a limited version of the actual priced product that runs on their hardware.

Navigation menu

Page actions

Page actions

Personal tools

About

Search

forewords

novel

Tools

@@ Line 26: / Line 26: @@
 <blockquote style="background-color: gray;color: white;">
 <blockquote><br>
-After dropping their CMOS line and completing the transition to commodity Intel, Unisys made MCP  available free for personal use to run from Windows 7 or 10 64 bit as "MCP Express". ough I didn learn of this until 2019Q3 and didn bring it up till end of Q1 '20 (version 5). It has to be replaced by a new download every July 31st.
+After dropping their CMOS line and completing the transition to commodity Intel, Unisys made MCP  available free for personal use to run from Windows 7 or 10 64 bit as "MCP Express". I didn learn of this until 2019Q3 and didn bring it up till end of Q1 '20 (version 5). It has to be replaced by a new download every July 31st.
 Thus, after 35 years, I now have nads on a current MCP (18) system and that opens a role for the Unisys MCP in the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Usages like ODT, DMS II or MARC unambiguously refer to the Unisys product line as we never intended take more than inspiration from it.<span style="background-color: black; color: lime;"><ref><font size=1 color=black> "CANDE", "WFL", and "MCP" are the actual overloads, "SPO" isn't really used in the modern Unisys culture, it's been lost from the mainframe days, so the smalltalk thing I'm doing doesn't map to anything specific, although functionally MARC and the ODT would be the analogs. The original SPO was just an ODT with supervisor permissions. Whose thing, mine or Unisys that is referred to by the overloaded terms will be clear in context (within Unisys MCP or not) and use the same "Unisys" modifier where needed.</font></ref></span>Much of the base mainframe stuff is available in the Windows based product and updated for the current epoch, though obviously it's a limited version of the actual priced product that runs on their hardware.