Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!psuvax1!vu-vlsi!cbmvax!steveb
From: steveb@cbmvax.UUCP (Steve Beats)
Newsgroups: comp.sys.amiga
Subject: Re: SAMPLE DOS DEVICE DRIVER, source and binary
Message-ID: <2566@cbmvax.UUCP>
Date: Wed, 21-Oct-87 15:38:56 EDT
Article-I.D.: cbmvax.2566
Posted: Wed Oct 21 15:38:56 1987
Date-Received: Sat, 24-Oct-87 09:28:06 EDT
References: <8710210733.AA18361@cory.Berkeley.EDU>
Reply-To: steveb@cbmvax.UUCP (Steve Beats)
Organization: Commodore Technology, West Chester, PA
Lines: 22
Summary: Differences between ACTION_INFO and ACTION_DISK_INFO

In article <8710210733.AA18361@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>	As usual, any and all Feedback will be appreciated.  I plan to do
>another one in the future which exploits the packet types not implemented
>in this one (some just don't apply to a simple ram disk).  I plan to update
>this one as soon as I can figure out (or somebody can describe to me) how
>to make the system recognize the thing in INFO and Info()... sigh.

The problem you are having with these various _INFO packets is the different
arrangements of the args.  The following should clarify things :-

ACTION_INFO		dp_Arg1 = BPTR to DiskInfo structure

ACTION_DISK_INFO	dp_Arg1 = BPTR to a lock on this volume
			dp_Arg2 = BPTR to DiskInfo structure

The ACTION_DISK_INFO packet appears to be used exclusively by WorkBench but it'spossible that other applications will use it too.  When DOS gets this packet it
just checks the lock for validity before dropping through to the ACTION_INFO
handler.

Hope this speeds up the second release :-)

Steve