Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site wanginst.UUCP
Path: utzoo!decvax!wanginst!vishniac
From: vishniac@wanginst.UUCP (Ephraim Vishniac)
Newsgroups: net.micro.mac
Subject: Re: MacSCSI problems
Message-ID: <1379@wanginst.UUCP>
Date: Mon, 25-Nov-85 08:22:32 EST
Article-I.D.: wanginst.1379
Posted: Mon Nov 25 08:22:32 1985
Date-Received: Mon, 25-Nov-85 21:27:13 EST
References: <170@brand.UUCP>
Distribution: na
Organization: Wang Institute, Tyngsboro, Ma.  01879
Lines: 22

> About two weeks ago I finished collecting together the pieces to build the
> MacSCSI hard disk described in Dr. Dobbs Journal.  The first time I got it
> all plugged togther, it came up just like the documentation said it would
> and seemed to work fine.  Since then, however, the reliability of the disk
> has rotted away to the point that it is now almost useless.  Some of the
> problems that I've seen are:
> ...
> 4. Finder reports that it can't build the desktop for the hard disk since
>    it's write-locked (which it isn't).
I think I know what this problem is.  The disk driver supplied with MacSCSI
interface is based on the ramdisk driver supplied with Aztec C.  That driver
doesn't respond to status calls correctly - it leaves the status info
unmodified.  The result is that if the most recently mounted volume was
locked, then the ramdisk (or hard disk, in this case) will appear locked 
also.  This is only one of an amazingly large number of "holes" in the driver.
It only works under ideal conditions.

-- 
Ephraim Vishniac
  [apollo, bbncca, cadmus, decvax, harvard, linus, masscomp]!wanginst!vishniac
  vishniac%Wang-Inst@Csnet-Relay