Proprietary VMThis is the topic for machines you shouldn't use, least you'll become the hostage of the vendors who lock you and whoever else you will communicate with you into their technology.
However attractive a proprietary technology may appear, it shouldn't be used as a means of communication.
Happily, no one owns the english language.
Of course, it is good to know what proprietary VMs exist or have existed, to be aware of their advantages and shortcomings, which is why they are listed here.
- .NET VM - A concrete VM inspired by a Microsoft proprietary VM (.Net) with an open published standard (ECMA 335, see below); it provides a means for loosely combining languages through a "Common Language Infrastructure" (CLI) in which applications written in multiple high-level languages may be executed in different system environments without porting
- Intel 8086 - The most infamous proprietary VM in computer history, that throttled for so many years advances in computer technology, has been the i8086 instruction set, upon which the "PC-compatible" computers were built
- TAOS VM - Despite the hype, it seems that the TAOS VP (virtual processor), as used in the Tao OS is just a proprietary variation on the ANDF idea
Also linked from: Virtual Machines