Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: DIBadMount
Message-ID: <27435@ucbvax.BERKELEY.EDU>
Date: 10 Jan 89 03:37:38 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 29

I was reading some source code that comes with the THINK C compiler (Also
known as LightSpeed C version 3) and I came across the following in a main
event loop:

	switch (event->what) {
		case diskEvt:
			if(noErr != HiWord(event->message)){
				InitCursor();
				DIBadMount(0x00640064, event->message);
			}
			break;

followed by more stuff, of course.  A quick check of Inside Mac Vol. 2,
the Disk Initialization package, says, yes:

Application programs should watch for disk inserted events in their main
event loops.  If the high word of the message of the event is an error,
then pass it to DIBadMount() so it can put up a dialog asking the user
what he wants to do about the bad floppy.

My question:

Is this still recommended?

Apple, what do you say?

--- David Phillip Oster            --"When we replace the mouse with a pen,
Arpa: oster@dewey.soe.berkeley.edu --3 button mouse fans will need saxophone
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu --lessons." - Gasee