Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!mit-eddie!media-lab!lacsap@plethora.media.mit.edu
From: lacsap@plethora.media.mit.edu (Pascal Chesnais)
Newsgroups: comp.sys.next
Subject: Re: Boot failed. Sdmach corrupted.
Message-ID: <5318@media-lab.MEDIA.MIT.EDU>
Date: 21 Feb 91 19:19:57 GMT
References: <1991Feb21.151922.5888@investor.pgh.pa.us>
Sender: news@media-lab.MEDIA.MIT.EDU
Reply-To: lacsap@plethora.media.mit.edu
Lines: 26

In article <1991Feb21.151922.5888@investor.pgh.pa.us> rbp@investor.pgh.pa.us  
(Bob Peirce #305) writes:
> The other day I fired up the cube (1.0) and it started through the
> checking process.  It got to the point where the little HD icon started
> spinning but after a few seconds it stopped. 
> Why should it happen
> here?  Should I expect this to be a frequent occurrence?  Is it a 1.0
> thing a BSD thing or a fluke of some sort?
> 
> Bob Peirce, Pittsburgh, PA	

From our FAQ:

5. Why does my 030 NeXT system using Release 1.0 hang a few seconds
   after attempting to boot from the optical disk?

   Release 1.0 contains a bug that can corrupt the kernel /odmach
   if a user attempts to launch /odmach from the browser.  The
   solution is to copy a clean /odmach from another NeXT system.
   Be sure to change the permissions of the newly installed /odmach
   to remove execute permissions to prevent future occurrences of
   the same problem.  Release 2.0 does not have this problem.

Pascal Chesnais, Research Specialist, Electronic Publishing Group
Media Laboratory, E15-351, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311
email: lacsap@plethora.media.mit.edu (NeXT)


Brought to you by Super Global Mega Corp .com