Talk:MCP: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
As [https://unite.org/wp/external-networking-with-mcp-express/ <span style="color: yellow;">the comments here</span>] discuss there is a conflict between versions of Windows after build 1903 (2019) and the legacy drivers emebedded in MCP Express. Ran into this because Windows forces updates, before which the MCP installation was working fine. After the upgrade to 1903, MARC could only be run from the ODT and CANDE appears broken. Unclear what product that post is calling "Developer's Studio" but decided to just uninstall current MCP Express and see if as the author says, the next version will address the issue. Assume it's MCP developers studio which you can't even find a clear way to buy, I hate that kind of shit so I will likely drop Unisys entirely from my plans if the next release of Express doesn't resolve the problem. [[User:Root|Root]] ([[User talk:Root|talk]]) | As [https://unite.org/wp/external-networking-with-mcp-express/ <span style="color: yellow;">the comments here</span>] discuss there is a conflict between versions of Windows after build 1903 (2019) and the legacy drivers emebedded in MCP Express. Ran into this because Windows forces updates, before which the MCP installation was working fine. After the upgrade to 1903, MARC could only be run from the ODT and CANDE appears broken. Unclear what product that post is calling "Developer's Studio" but decided to just uninstall current MCP Express and see if as the author says, the next version will address the issue. Assume it's MCP developers studio which you can't even find a clear way to buy, I hate that kind of shit so I will likely drop Unisys entirely from my plans if the next release of Express doesn't resolve the problem. [[User:Root|Root]] ([[User talk:Root|talk]]) | ||
</div> | </div> | ||
== Elliott AI ™ == | |||
<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 64 bit as "MCP Express". I don't recall learning of this before 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 hands on a current MCP (18) system <span style="background-color: black; color: lime;"><ref><font size=1 color=black> At DBCC, the SPO for the 6700 was in my office, it and the production 6800 had between them less than 2 MWord of RAM and there was not much more than 1GB of disk, if that. The MCP XE I run has 2X the processors, 32X the RAM and about 20X the disk. Mill is harder to judge, but i5 3.3GHZ is about 50X times the 150ns B6800 clock, and it does about 83K MIPS vs presumed less than 10 MIPS for the B6xx. The i5 box was bought refurbished for about $100. The B6700 was gotten off a state of FL salvage depot but it probably used more than a $100 of electricity a month. The prod machine served 500 transaction types to several hundred terminals and the 6700 served a dev staff of about 10. During registration I sat at the production SPO tweaking system factors, before the dev machine came up I think.</font></ref></span> 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 taking 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. | |||
The most natural form of integration of Unisys MCP is to allow it as an alternate to linux node in a DCP. A design principle to inform and guide such an effort is that Unisys MCP shall only have integration with the DCP cognitive architecture and not the physical one, each Unisys MCP in a DCP will be an island (Unisys internetworking notwithstanding) unlike the linux nodes which form a single system image. Thus, the integration can be in software built with the standard Unisys dev kit targeting the DCP cognitive architecture.<span style="background-color: black; color: lime;"><ref><font size=1 color=black> Seems like a good enough place to say I have no interest in the Unisys Univac stuff. There appear to be only a couple hundred MCP sites still running and a good number of them are software houses serving the remainder, a mix of banks, govt units, etc.</font></ref></span> | |||
Thus, "Elliot AI", where Elliot suggests the Algol, Organick, or perhaps the ET display 🖖. Obviously, the proviso in the README for domain space about intentions versus production realizations applies to this a fortiori. However it is a serious intention and due to the small size of any possible market, I will make anything that does reach the stage of distribution available at no cost (other than standard first class capitation and the passed thru cost of any used hosting resources).<span style="background-color: black; color: lime;"><ref><font size=1 color=black>When I first encountered MCP and its arch and product lines they were already decades old and I would remark that if Burroughs had followed the advancement of computer science over that time they would have various features they lacked as common business oriented systems, such as OO, AI, etc. Elliot AI is a possible realization of that, albeit now with 3X times the elapsed time since the inaugural MCP. Current MCP bears mark 59.* which I take it roughly marks years from the first mark release.</font></ref></span> | |||
<br><br> | |||
</blockquote> | |||
</blockquote> | |||
</hr> | |||
<references/> | |||
Revision as of 11:47, 12 May 2020
Janus / TCP v3 SNAFU
As the comments here discuss there is a conflict between versions of Windows after build 1903 (2019) and the legacy drivers emebedded in MCP Express. Ran into this because Windows forces updates, before which the MCP installation was working fine. After the upgrade to 1903, MARC could only be run from the ODT and CANDE appears broken. Unclear what product that post is calling "Developer's Studio" but decided to just uninstall current MCP Express and see if as the author says, the next version will address the issue. Assume it's MCP developers studio which you can't even find a clear way to buy, I hate that kind of shit so I will likely drop Unisys entirely from my plans if the next release of Express doesn't resolve the problem. Root (talk)
Elliott AI ™
After dropping their CMOS line and completing the transition to commodity Intel, Unisys made MCP available free for personal use to run from Windows 64 bit as "MCP Express". I don't recall learning of this before 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 hands on a current MCP (18) system [1] 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 taking more than inspiration from it.[2]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.
The most natural form of integration of Unisys MCP is to allow it as an alternate to linux node in a DCP. A design principle to inform and guide such an effort is that Unisys MCP shall only have integration with the DCP cognitive architecture and not the physical one, each Unisys MCP in a DCP will be an island (Unisys internetworking notwithstanding) unlike the linux nodes which form a single system image. Thus, the integration can be in software built with the standard Unisys dev kit targeting the DCP cognitive architecture.[3]
Thus, "Elliot AI", where Elliot suggests the Algol, Organick, or perhaps the ET display 🖖. Obviously, the proviso in the README for domain space about intentions versus production realizations applies to this a fortiori. However it is a serious intention and due to the small size of any possible market, I will make anything that does reach the stage of distribution available at no cost (other than standard first class capitation and the passed thru cost of any used hosting resources).[4]
- ↑ At DBCC, the SPO for the 6700 was in my office, it and the production 6800 had between them less than 2 MWord of RAM and there was not much more than 1GB of disk, if that. The MCP XE I run has 2X the processors, 32X the RAM and about 20X the disk. Mill is harder to judge, but i5 3.3GHZ is about 50X times the 150ns B6800 clock, and it does about 83K MIPS vs presumed less than 10 MIPS for the B6xx. The i5 box was bought refurbished for about $100. The B6700 was gotten off a state of FL salvage depot but it probably used more than a $100 of electricity a month. The prod machine served 500 transaction types to several hundred terminals and the 6700 served a dev staff of about 10. During registration I sat at the production SPO tweaking system factors, before the dev machine came up I think.
- ↑ "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.
- ↑ Seems like a good enough place to say I have no interest in the Unisys Univac stuff. There appear to be only a couple hundred MCP sites still running and a good number of them are software houses serving the remainder, a mix of banks, govt units, etc.
- ↑ When I first encountered MCP and its arch and product lines they were already decades old and I would remark that if Burroughs had followed the advancement of computer science over that time they would have various features they lacked as common business oriented systems, such as OO, AI, etc. Elliot AI is a possible realization of that, albeit now with 3X times the elapsed time since the inaugural MCP. Current MCP bears mark 59.* which I take it roughly marks years from the first mark release.
