🚀 go-pugleaf

 For a current project, I'm writing a console-ish handler.  However, with
the sparse documentation on them, I've come up to a problem.  (For
documentation, I'm using the little stated in the back of the AmigaDos
manual, and the article(s) on file systems from a few old issues of
transactor by the Software Distillery guys.)

 Here's the problem:

 I have a device associated through a mountlist with my handler - let's
call it "HAN:".  I need to be able to issue a NEWCLI HAN:parameters command.

 I receive ACTION_FINDINPUT and ACTION_FINDOUTPUT packets fine.
(Although I don't remember which comes through first.)  The first packet
contains a Lock of 0 (as I expected), and a BSTR containing the filename -
in this case, "HAN:parameters".  This works fine.

 Here's the problem:

 When the second of the two comes through, it comes with a filename of "*",
(which I process as "current output"), and a Lock (to which, as far as I
can tell, the "*" is supposed to be relative).  Where's this Lock coming
from?  My handler certainly isn't creating this lock in response to any
packets.  Secondly, since both the ACTION_FINDINPUT and ACTION_FINDOUTPUT
are supposed to access the same thing, how can I associate the lock to
the previous ACTION_FINDwhatever?  (Is there any way I can find the handle
that I filled in during the original ACTION packet from the lock passed
to me by the second?)

 Help!

 - Greg

     +----------------------------------------------------------------+
     | A sign of mismanagement, over-    |  Greg Miller               |
     | complication and overall idiocy:  |  ..ames!sharkey!ionic!gm   |
     |                                   |  gm@ionic.uucp             |
     |                                   |                            |
     |      "Designed By Committee"      |                            |
     +----------------------------------------------------------------+