Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!ucbvax!bloom-beacon!apple!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: DIBadMount
Message-ID: <437@internal.Apple.COM>
Date: 18 Jan 89 17:45:35 GMT
References: <27435@ucbvax.BERKELEY.EDU> <40cd6a85.a590@mag.engin.umich.edu>
Organization: Advanced Technology Group, Apple Computer
Lines: 21

In article <40cd6a85.a590@mag.engin.umich.edu> billkatt@caen.engin.umich.edu (Steve Bollinger) writes:
>It never was recommended.  If you read a little farther (bottom of page 395,
>and top of 396 it says
>
>When your Application received the DiskEvt, the system has aldready tried to
>mount the volume.  If it was successful, great, if not, it will sit in the
>drive until the SFGet(or Put)File comes up.  This is fine because most file

I have to disagree with this.  What good is it to have the diskette sit in
the drive, where the only way to get it out is to type Cmd-Shift-1?  It
also doesn't make sense to make the user wait for Std File before s/he can
format the disk.  I think applications should call DIBadMount, so that the
user has a chance to eject the disk or format it.  (BTW, MacApp calls
DIBadMount in this case.)


-- 
		 Larry Rosenstein,  Object Specialist
 Apple Computer, Inc.  20525 Mariani Ave, MS 46-B  Cupertino, CA 95014
	    AppleLink:Rosenstein1    domain:lsr@Apple.COM
		UUCP:{sun,voder,nsc,decwrl}!apple!lsr