Windows Mobile Device Center

---

Has anyone been able to connect to the Kin using the Windows Mobile Device Center? (most likely not--I haven't seen anyone posting about it...)

I came across a website with a bunch of tools that look pretty useful for WinCE devices:
http://itsme.home.xs4all.nl/projects/xda/tools.html

It seems that these tools will only work though if the phone can be seen by the windows mobile device center (with its associated rapi.dll driver).

If there is a way to make the windows mobile device center "see" the kin, then maybe we give some of these tools a test drive.... I'm guessing it's a matter of having the correct driver (which seems to be somewhat of a problem )

I've thought about trying it, however my Win 7 x64 computer seems unable to install or uninstall the Windows Mobile Device center. Once I figure it out, or get a computer that can run it, I'll test it. And Activesync (for the older OSs)

On my laptop (have Zune installed on here) I have Win XP, so had to install ActiveSync 4.5. Unfortunately, after plugging in the phone, ActiveSync could not detect my phone. Not sure if having Zune on my laptop makes any difference or not.

Will install Windows Mobile Device Center 6.1 on my Win 7 desktop (no Zune) sometime tonight and see if the phone is detected there.

This is my first post, but I have been reading every single post since I got the phone around three months ago. I didn't feel the need to post because you all know way more than I do, but I think I may have made a discovery that might help your WMDC idea. If you are to turn on both the PPRO and usb_pass thru modes at the same time on the Kin device it creates an entirely new usb mode labeled "usbfn composite driver." which from my quick research I just did is the mode needed for the WMDC. I'll let you pros test it some more, but I'll keep messing around and see if I can get something. Hope it helps in anyway. If not sorry for wasting everyone's time.

Originally Posted by kintwofan

This is my first post, but I have been reading every single post since I got the phone around three months ago. I didn't feel the need to post because you all know way more than I do, but I think I may have made a discovery that might help your WMDC idea. If you are to turn on both the PPRO and usb_pass thru modes at the same time on the Kin device it creates an entirely new usb mode labeled "usbfn composite driver." which from my quick research I just did is the mode needed for the WMDC. I'll let you pros test it some more, but I'll keep messing around and see if I can get something. Hope it helps in anyway. If not sorry for wasting everyone's time.

At least you've been reading. We're aware of the mode, and my limited trials do not let my computer recognise it, but I'm interesting in your research as to which mode is needed by WMDC. Where did you find that out?

http://forum.xda-developers.com/showthread.php?t=405945 here says that usbfn is for wmdc

also micrsoft talks about this mode here http://msdn.microsoft.com/en-us/library/gg159468.aspx

finally do a google search it seems that we have to make a driver to make it work, but there are a lot of templates out there.

Like i said maybe it will help and maybe not. Sorry.

I tested it.

Created a custom made driver in XP ("Kin Lame driver" from "LameCorp by Kussack")for device:

VID 0x045e, PID 0x643, MI_00

Activesync doesnt trigger on the phone in composite mode

Usb sniff shows that when the program talks to the phone, the phone doesnt answer (even not an error code or something).

Dunno about WMDC and/or the "other", the MI_01 device.

Originally Posted by johnkussack

I tested it.

Created a custom made driver in XP ("Kin Lame driver" from "LameCorp by Kussack")for device:

VID 0x045e, PID 0x643, MI_00

Activesync doesnt trigger on the phone in composite mode

Usb sniff shows that when the program talks to the phone, the phone doesnt answer (even not an error code or something).

Dunno about WMDC and/or the "other", the MI_01 device.

How did you create the custom driver? Was it completely built from scratch, or an existing MS driver?

I spent a couple hours last night trying to fake a WMDC driver into driving my Kin, but was unable to. The closest I got was in using the "Pink" driver found in another thread here, but I couldn't do anything with it.

I still want to try getting a different driver to work (I have a Palm Treo Pro/WM 6.1 phone that I want to test, to see what driver it uses and how it works on the computer). If you've already done similar work, it might not be worth my duplicating your efforts, but if I can go about it differently, I'm still going to try.

you just need to add a pattern in wceusbsh.inf, following the existing ones.

It's like not exactly, putting it from memory:

%\USB&VID=0x045E&PID=0x643&MI_00%.DeviceDesc = \USB&VID=0x045E&PID=0x643&MI_00

And later in the file:

\USB&VID=0x045E&PID=0x643&MI_00.DeviceDesc = "Lame kin driver mfker!"

It's just pasting and customizing two lines (like i posted) and it will be labeled as "Windows CE devices" (even not working or being hacked in a wrong file).

I did this with all driver modes, just for fun. Nothing worked, but may worth a try with newer drivers or OS or pc's.