GetDeviceProc

Finds a handler to send a message to (V36)

Finds the handler/file system to send packets regarding 'name' to. This may involve getting temporary locks. It returns a structure that includes a Lock and MsgPort to send DosPackets to in order to attempt your operation. It also includes information on how to handle multiple-directory assigns (by passing the devproc result back to GetDeviceProc() until it eventually returns NULL).

The initial call to GetDeviceProc() should pass NULL for 'devproc'. If, after using the returned DevProc, you get an ERROR_OBJECT_NOT_FOUND, and (devproc->dvp_Flags & DVPF_ASSIGN) is true, you should call GetDeviceProc() again, passing it the 'devproc' structure. It will either return a modified 'devproc' structure, or NULL (with ERROR_NO_MORE_ENTRIES in IoErr()). Continue until it returns NULL.

This function also increments the counter that locks a handler/fs into memory. After calling FreeDeviceProc(), do not use the port or Lock again!

name

name of the object you wish to access. This can be a relative path ("foo/bar"), relative to the current volume (":foo/bar"), or relative to a device/volume/assign ("foo:bar").

devproc

A value returned by GetDeviceProc() before, or NULL

devproc

a pointer to a DevProc structure or NULL

Counter not currently active in 2.0. In 2.0 and 2.01, you HAD to check DVPF_ASSIGN before calling it again. This was fixed for the 2.02 release of V36.

FreeDeviceProc(), DeviceProc(), AssignLock(), AssignLate(), AssignPath()