Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ames!eos!data.nas.nasa.gov!mustang!nntp-server.caltech.edu!pooh!madler From: madler@pooh.caltech.edu (Mark Adler) Newsgroups: comp.sys.next Subject: Re: 68040 upgrade Message-ID: <1991Feb3.013242.17217@nntp-server.caltech.edu> Date: 3 Feb 91 01:32:42 GMT References: Sender: news@nntp-server.caltech.edu Organization: California Institute of Technology, Pasadena Lines: 27 Nntp-Posting-Host: pooh Just got my 040 upgrade and 2.0 OD. A few notes ... The 68040 did not say "sample" anywhere on it. Then again, there was a large heat sink glued to the thing that covered most of the package. What writing there was, however, seemed to be carefully printed on the boundary, perhaps anticipating the heat sink. The 2.0 OD would not boot on the 040. It would simply hang without even courtesy of an exception message, like the one that accompanies the hard disk boot failure after an 040 upgrade. Nevertheless, I guessed it was the same problem, and used the command: "disk -b /dev/rod0a" to write a new boot sector, and then the OD booted fine. I installed 2.0 on my 330M (really 349M) Maxtor from scratch (i.e. I did not use Upgrade2.0). This virgin install took 179M of space, leaving 123M "available" out of 337M total. (In my notation, 1M=1048576 bytes--NeXT seems to think 1M=10^6 in some cases.) The remaining 35M is the reserved 10% for the superuser when the file system fills up. The 179M includes a 16M swapfile. I must also add that 2.0 is a considerable improvement over 1.0 in both convenience and speed (I've used 2.0 on an 030 also). If anyone out there is resisting the move to 2.0, you don't know what you're missing. Mark Adler madler@pooh.caltech.edu