Oh, I'm sorry.
I'm really naive in this subject and I wasn't explicit in my
question.
What I meant is that I don't know what you have to do after you
acomplish writing your driver source.
Do I have to do build it on Platform Builder and copy the files to the
somewhere in the WM and modify a .reg file?
Thanks for your help
Regards,
Guilherme Kami
Is it safe to say that you do not work for Dell or one of their vendors?
But instead are developing a driver to distribute to others to use a device
you are buiding that inserts into the Axim?
Let's assume that I am right. You need a way to get your driver and
registry setting into the device and insert your registry settings in the
registry. Unfortunatly, this is outside of my expertise but I can point you
in the right direction. CAB files are the typically way to do this, and
usually they are wrapped with an MSI that installs the CAB file on a PC so
that ActiveSync can send the CAB and run the cab file installer on the
device.

Signature
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman
EuroTech Inc.
www.EuroTech.com
> Oh, I'm sorry.
>
[quoted text clipped - 9 lines]
> Regards,
> Guilherme Kami
GuiKami - 31 Jul 2008 21:20 GMT
Hi everybody again.
Thanks for all your help.
Now, I have another doubt.
As I read, the bus driver is responsible to do the first communication
with the SD and determine the appropriate client driver to load. To do
this, the bus driver has to access the CIS area and get the
CISTPL_MANFID.
Another thing I've read is that you have to use CMD52 for reading a
register. So I thought that it would be the first command the host
would use.
But in my tests, I only received the following commands from the host:
CMD5, CMD0, CMD1, CMD55.
Is that correct? Do I have to receive all this commands before the
command to get the Plug and Play information? Or does the host uses
another command to get that?
Thanks again.
Regards,
Guilherme Kami