Hi,
I understand, you are trying to access the device from an usermode
Application. In that case, You must call CreateFile to open a handle
to the device. Do not worry about pipes, internally the driver will
take care of it (Routes the write to the OUT pipe and Read to the IN
pipe).
Rgds
Vanathy
My problem is the CreateFile call, what do I put in parameter 1 - the
filename ?
Cheers,
Colin.
THIS IS AN EXCERPT FROM MSDN & it EXPLAINS USING THE GUID TO OBTAIN A
HANDLE FOR THE DEVICE,
---------------------------------------------------------------------
Device drivers provide a uniform and extensible way for applications
and the system to interact with them programmatically, known as a
device interface. Drivers expose, register, and enable device
interfaces. A driver can expose zero, one, or more than one interface
for a particular device. A device interface is represented by a GUID.
Each device interface is a member of a device interface class. A
device interface class is a group of device interfaces with the same
functionality. For example, all the joysticks on a system could be
members of the joystick device interface class. A device interface
class is identified by a class GUID.
When an application must communicate with a device, it searches for a
device that exports the required interface. To perform the search, use
the following steps.
Call the SetupDiGetClassDevs or SetupDiGetClassDevsEx function to
obtain a list of all devices in a specified device class. This list is
known as a device information set.
Call the SetupDiEnumDeviceInterfaces function to enumerate all devices
of the specified class that export the interface.
To communicate with the device, call the
SetupDiGetDeviceInterfaceDetail function. This function returns device
information in an SP_DEVICE_INTERFACE_DETAIL_DATA structure. The
DevicePath member provides the symbolic link name, which can be used
in the CreateFile function to access the device.
Regards
Vanathy
Colin <co...@microscum.com> wrote in message news:<n7ied059fj88lsosu...@4ax.com>...