Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!csd4.milw.wisc.edu!nic.MR.NET!umn-d-ub!rutgers!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Little-known Dos calls
Keywords: AddDosNode, DeleteDosNode
Message-ID: <5714@cbmvax.UUCP>
Date: 18 Jan 89 04:17:55 GMT
References: <284@microsoft.UUCP>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 21

In article <284@microsoft.UUCP> w-colinp@microsoft.uucp (Colin Plumb) writes:
>An acquaintannce of mine from Toronto (who I can't readily get in touch with
>now) told me about two calls, AddDosNode and DeleteDosNode (or it may be
>DOS; this was verbal) that do All The Right Things in hitting the di_DevInfo
>list to add volumes, devices, etc.

	Yes, use them.  There are autodocs for them in the 1.3 developers
update (call/write CATS), and I believe they are in expansion.library (I
could be wrong).

>The problem I'm really trying to manage is to signal open "Please insert
>volume..." requesters, so the user doesn't have to click "retry."  I believe
>most else can be handled by hitting the list directly, using Forbid() and
>Permit().

	They do this already.  Wait a second or two.  The one exception is
the requesters WB puts up when you do a loadwb, and some disks aren't in drives.
Those you have to Retry (will be fixed).

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup