Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!uwmacc!dubois
From: dubois@uwmacc.UUCP (Paul DuBois)
Newsgroups: comp.sys.mac
Subject: TransSkel Disk Insert Bug?
Message-ID: <644@uwmacc.UUCP>
Date: Sat, 6-Dec-86 17:15:37 EST
Article-I.D.: uwmacc.644
Posted: Sat Dec  6 17:15:37 1986
Date-Received: Sun, 7-Dec-86 03:52:44 EST
Organization: Flat Egg Software, Ltd.
Lines: 44


This appeared in mod.mac recently.  Anyone care to comment?
---
From: hplabs!felix!fritz!rlong@ucbvax.Berkeley.EDU
Subject: Disk Inserted events in TransSkel

   I just downloaded the new TransSkel recently posted to mod.mac.binaries.
I looked at the code to process disk-inserted events as I was interested
in putting something similar in my project. The code looks like:

         case diskEvt:
             DILoad();
             DIBadMount(...);
             DIUnload();
             break;

   I thought (after reading the phonebook IM) that it was too late to call
DILoad when the disk event occurs, because the system disk may have been
ejected at that time. If you have a one-drive mac, no hard disk, I expect
this to happen:

1/ You eject the system disk.
2/ You insert a blank disk.
3/ Disk event.
4/ Appli calls DILoad.
5/ System ejects blank disk and request system disk.
6/ System loads DI package.
7/ Appli calls DIBadMount.
8/ User gets the disk-unreadable dialog and clicks Initialize.
9/ System disk, still in drive, is initialized!!

     Am I wrong?

        Daniel Ranson.
        Centre National d'Etudes des Telecommunications
        ...!seismo!mcvax!inria!crcge1!crcge2!ranson

---
Paul DuBois     UUCP: {allegra,ihnp4,seismo}!uwvax!uwmacc!dubois    |
                ARPA: dubois@easter                               --+--
                      dubois@rhesus                                 |
                                                                    |
"What is lacking cannot be counted." - Solomon the cladist
                                       (Ecclesiastes 1:15)