Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ogicse!orstcs!usenet!prism.CS.ORST.EDU!jasmerb
From: jasmerb@prism.CS.ORST.EDU (Bryce Jasmer)
Newsgroups: comp.sys.next
Subject: BuildDisk and 2.0
Message-ID: <1991Jan03.031323.12087@usenet@scion.CS.ORST.EDU>
Date: 3 Jan 91 03:13:23 GMT
Sender: @usenet@scion.CS.ORST.EDU
Reply-To: jasmerb@prism.CS.ORST.EDU (Bryce Jasmer)
Organization: Oregon State Univ. -- Computer Science
Lines: 23
Nntp-Posting-Host: prism.cs.orst.edu

Well, that time came once again. Time to rebuild my system with a brand
new killer operating system. This is about the fourth I've done on my 
own machine (0.8, 0.9, 1.0, and 2.0.)

And every time I get ready to build a new system I become very panicked
because I am always losing track of my special disktab file that contains
info on my 3rd party hard disk. I had heard something about NeXT putting
some great SCSI support into 2.0 so I didn't bother looking for my old
disktab entry and just decided to start up BuildDisk and see what would
happen. And to my semi-surprise, it recognized my disk and started building
away. I was quite pleased (nay, quite impressed) to say the least.

In case you are interested, here is the disk info:

internal CDC Imprimis Wren-V 94181-702
formats down to about 570 Meg usable space (after inodes and all)

I can't guarentee that this will work for all SCSI disks, but was thrilled
that it worked with mine. I hope others are having the same experiences.

Bryce Jasmer
St. Helens Software
bart!jasmerb@sequent.com