Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!hayes.ims.alaska.edu!accuvax.nwu.edu!casbah.acns.nwu.edu!galanter
From: galanter@casbah.acns.nwu.edu (Philip Galanter)
Newsgroups: comp.sys.next
Subject: Re: in Time, again
Message-ID: <332@casbah.acns.nwu.edu>
Date: 11 Oct 90 22:59:48 GMT
References: <8990@helios.TAMU.EDU>
Sender: news@casbah.acns.nwu.edu
Reply-To: galanter@casbah.acns.nwu.edu (Philip Galanter)
Organization: Academic Computing and Network Services, Evanston, Il.
Lines: 23

>>They tell me that the first large batch of 68040s had a bug which did not
>>affect any of the NeXT software because mach does not use the affected 
>>opcode.  This bug does sink most of the other companies who would use the 40.
>>So NeXT took delivery of the entire batch and can thus release an 040 machine
>>well ahead of everyone else.

I have heard this form various NeXT folks as well, but it sure sounds goofy.
So what instruction could possibly be so expendable, by NeXT _and_ any other
developer/development system/compiler?  Maybe some kind of low level thing
that _only_ the OS should be dealing with, like virtual memory paging or
something?  Anybody out there from NeXT have the technical info that would
help the above make sense?

Thanks, Phil



============================================================================== 
Academic Computing & Network Services ~ AppleLink: A42 ~ ~ 627 Dartmouth Place
~ ~Advanced Technology Group Manager ~ galanter@nwu.edu ~ ~ Evanston, IL 60208
 ~ ~ ~ ~ ~Northwestern University ~ ~CompuServe: 76474,154 ~ fax: 708-491-4548
~ ~ ~ ~ ~ ~ ~ Philip Galanter~ ~ ~ NeXT>gambuh.acns.nwu.edu ~ ph: 708-491-4050
==============================================================================