ISRAPDA

Posts 1
Cannot install Windows Mobile-based device
Was this post helpful ?

I have some problems connecting my Smartphone (Qtek 8310) to my computer via USB. When I connect the smartphone to the computer with a USB-Cable the following happends:
I get a ballonmessage that says -New Hardware found: Generic RNDIS. Then it changes "Generic RNDIS" to "Windows Mobile-based Device" and a Wizard for Installing hardware appears.
When I select Install automaticly the wizard fails to install the device. If I now look in the device-manager I have a new network card with an exclamation mark on the icon. I tried to start over and install it manually. But I don´t know where to look for drivers. I tried the drivers in the active sync-folder but they didn´t work.

The computer is running on Win XP pro with SP2. I have no personal firewall. I´m using Active Sync 4.2.

What am I doing wrong? Am I missing anything? Do I need to download any drivers?

I should also add that it works fine on my other computer. Plug and play!

Pleas help me!

--------------------------------------------------------------------------------
Ludwig Eriksson

28 Nov 2006, 2:04 AM UTC
Richard Lyle

Posts 2 Re: Cannot install Windows Mobile-based device
Was this post helpful ?

I'm having the same issue after upgrading from Windows 2000 SP4 to Windows XP SP2...

I keep reinstalling ActiveSync 4.2, but when I plug in my Pocket PC into my USB port, I get an "Cannot Install this hardware" error message. The message box also says "The name is already in use as either a service name or a service display name".

I've uninstalled & installed ActiveSync 4.2 about 20 times now... I'm going to go run regedit and see if I can figured out what got left-over in the registry that's messing with getting ActiveSync working again.

IMHO ... ActiveSync has been nothing but a pain in the butt since the first day. I really wish I would have gotten the Palm version instead of the windows mobile version now.

Please help, and show me how awsome Microsoft support is...

-Richard

28 Nov 2006, 3:35 AM UTC
Richard Lyle


Posts 2
Re: Cannot install Windows Mobile-based device
Was this post helpful ?


Ok, found the anwer myself... and sharing it here with others that might run into problems with ActiveSync when upgrading from Windows 2000 to Windows XP.

The setupapi.log provided the clue I needed... it actually contained useful information, unlike the actual windows dialog. It contained the following text:

#-035 Processing service Add/Delete section [Usb_Rndis.ndi.Services].
#E279 Add Service: Failed to create service "usb_rndisx". Error 1078: The name is already in use as either a service name or a service display name.
#E033 Error 1078: The name is already in use as either a service name or a service display name.
#E275 Error while installing services. Error 1078: The name is already in use as either a service name or a service display name.
#E122 Device install failed. Error 1078: The name is already in use as either a service name or a service display name.
#E154 Class installer failed. Error 1078: The name is already in use as either a service name or a service display name.
#I060 Set selected driver.


Using the information above, I searched the registry using "RegEdit" for "usb_rndis"... I found several keys called "usb_rndisy", I removed all those keys. I then reinstalled ActiveSync 4.2 again, plugged in my Pocket PC and it WORKED!

Aparently, when the updated drivers tried to install my PocketPC device, the usb_rndisx service was conflicting with the old usb_rndisy service.

-Richard

after a sync and several soft installations, the same problem of an incorrect Windows Mobile-based device re-appears

zeevik_k писал(а):igor7
После всех вчерашних попыток, я выбрал наиболее лёгкий способ.
1. System Restore на 2 дня назад, до переустановки ActiveSync, Windows Mobile-based device - OK.
2. Запуск ActiveSync из Start->Program Files->ActiveSync
3. ActiveSync автоматически переустановился.
4. Подключил КПК (наблюдая за поведением Device Manager-а.
5. Всё сработало нормально, только время от времени появлялся incorrect Windows Mobile-based device, но потом приходил в норму.