Re: How do I load a third party driver in Windows CE 6.0

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi Bruce,
I read the documentation here.

http://msdn2.microsoft.com/en-us/library/aa918154.aspx

I though if I matched the parameters of the device that I am trying to plug
into the usb in the
HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients and gave the name of my dll
I would get a dll to load. I guess this isn't right? So let me turn the
question around. What do I have to do in the registry to get my dll to load?
--
Don


"Bruce Eitman [eMVP]" wrote:

No.

What documenation are you refering to?

That key is the root of where you need to put your keys, but I can't cross
reference what you have done enough to try to straighten you out.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:49E9D7FD-5C32-47D2-911F-CD5AB12DCF64@xxxxxxxxxxxxxxxx
Hi Bruce,

What I am getting from the documentation is if I add the following
registry
entry

[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients]
"VendorID"=dword:1905
"ProductID"=dword:1956
"DeviceClass"=dword:0
"DeviceSubClass"=dword:0
"DeviceProtocol"=dword:0
"Dll"="myusbdevicedriver.dll"

then myusbdevicedriver.dll will get loaded when I attach my USB device.
Is
this true?
--
Don


"Bruce Eitman [eMVP]" wrote:

You need a USB Host Class driver since you will be plugging it into the
USB
Host, not USB Function.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:039868F2-2505-402B-AA1B-1FFC05C04189@xxxxxxxxxxxxxxxx
Hi,

I have been reading some of the documentation for USB drivers. It is
unclear to me which type of drivers I need to read and write the end
points
described below for my USB to 485 converter. I think I need a USB
Function
Serial Client Driver can anyone confirm?


Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x1905
idProduct: 0x1956
bcdDevice: 0x0400
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x03
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: Full
Device Address: 0x01
Open Pipes: 2

Endpoint Descriptor:
bEndpointAddress: 0x81
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x02
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

--
Don


"amag" wrote:


Serial communications USB-drivers typically goes into:

[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\<X>_<Y>\Default\Default\USBSER_CLASS]

where <X> is the USB vendor id in decimal(!) and <Y> is the device id
in
decimal.

But you should probably check what values you need with FTDI. At least
you'll need the Dll-value:

"Dll"="mydrv.dll"

Btw have you tested communication with the driver, last I checked FTDI
wasn't to eager to provide CE6 implementations of their drivers.

Hope it helps,

/AM

"Don" wrote:

Hi,

I have a USB to 485 converter with a FTDI chip on it. FTDI supplies
an
inf
file and a dll that supports windows CE. Currently I have to copy
the
inf
and dll file to the windows directory and when I plug the USBto485
converter
in a window pops up and I have to type the name of the dll in that
window and
it works. I would like this to be more automatic. I am assuming
that
I can
modify a bib file in my project and get the files in the windows
directory,
but how do I make it so the window does not come up asking me for
the
name of
the dll? Are there registry entries I can add so the dll is already
present?
--
Don






.



Relevant Pages