Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!hoser.berkeley.edu!bryce From: bryce@hoser.berkeley.edu (Bryce Nesbitt) Newsgroups: comp.sys.amiga Subject: Re: The secrets of the file system (was FillDisk) Message-ID: <22038@ucbvax.BERKELEY.EDU> Date: Thu, 3-Dec-87 06:44:59 EST Article-I.D.: ucbvax.22038 Posted: Thu Dec 3 06:44:59 1987 Date-Received: Mon, 7-Dec-87 00:14:54 EST References: <6098@jade.BERKELEY.EDU> <2080@ulowell.cs.ulowell.edu> <2085@ulowell.cs.ulowell.edu> Sender: usenet@ucbvax.BERKELEY.EDU Organization: University of California at Berkeley Lines: 28 In article <2085@ulowell.cs.ulowell> page@swan.ulowell.edu (Bob Page) writes: |>You can force a disk validation by running DiskChange DH0: | |Arrgh! DON'T DO THIS unless the people who supply your |harddisk.device (or whatever your driver is called) says it's OK! | |I realized DiskChange makes some NON-STANDARD calls to the driver. |When I say non-standard, I mean IORequests that are not part of the |basic and required functions for a device, like open, close, read, |write, etc. Each device can have its own non-standard functions |for special commands unique to that device. Huh?? Unless my brain is fried, DiskChange ought to be doing a ACTION_INHIBIT true then false (or the other way 'round). That is a standard packet. Now dos may follow up ACTION_INHIBIT with something as rude as TD_CHANGESTATE, TD_CHANGENUM and/or TD_PROTSTATUS, but none of those should give a harddisk.device fits. (I'm told ACTION_INHIBIT was indented to return success for removable media drives, and failure otherwise. I don't know the status of this.) |\ /| . Ack! (NAK, SOH, EOT) {o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (") U WARNING: hoser's spool directory eats a *lot* of mail. :-(