Talk:Data General Eclipse MV/8000

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by Computer hardware task force.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Software[edit]

Page needs more work, in particular, pre-DG/UX OSes and programming languages, applications, etc. 143.232.210.150 (talk) 19:29, 5 April 2012 (UTC)[reply]

Production[edit]

Production figures would be useful. Number would give a count of significance. 143.232.210.150 (talk) 19:30, 5 April 2012 (UTC)[reply]

Some issues with the article[edit]

"The Eclipse MV/8000 was the first in a family of 32-bit minicomputers produced by Data General during the 1980s." I doubt this is true. The MV/7800 is 32 bit. Was is before the MV/8000?

Clarification note: The MV/8000 was the first machine in the 32 bit MV series (as evidenced in Soul of a New Machine where the original development of wire-wrapped prototypes of the ALU, ATU (etc) cards is described). The MV/7800 was developed later as a single-chip implementation of the MV CPU architecture, and was slower than the MV/8000. The MV/7800XP was a subsequent evolution of the MV/7800, and was faster than the MV/8000.

"The Eclipse MV was a 32-bit CISC architecture with a 4GB address space." Not true. The MV/7800 XP is preconfigured with 2 or 4 MiB. Expandable to 14 MiB.

Clarification note: It is correct that the 32bit MV architecture supported a 4GB address space. This was a virtual address space, in which unused pages of memory were swapped from physical memory out to disk, and swapped back in again when needed. Physical memory size could therefore be much smaller than 4GB. It was the job of the ATU (Address Translation Unit) to perform fast mapping between the physical and virtual address spaces.

"The outermost ring, ring-7, was the least privileged. The inner-most ring, ring-0 was the most privileged." Not true. I will read the manual tomorrow and update this comment - paraphrased. — Preceding unsigned comment added by 81.106.158.48 (talk) 18:57, 4 March 2014 (UTC)[reply]

Clarification note: It is correct that Ring 0 was the most privileged, and Ring 7 the least. Each virtual memory page existed in the context of a specific ring. Later operating system implementations including OS/2 followed the ring based memory protection scheme (although with a lower number of rings). — Preceding unsigned comment added by 180.149.199.30 (talk) 07:40, 23 November 2014 (UTC)[reply]

"Later operating system implementations including OS/2 followed the ring based memory protection scheme" As did earlier operating systems including Multics. Guy Harris (talk) 07:14, 24 September 2021 (UTC)[reply]