Re: Vista and IMate Jamin WMDC 6 RTM Problem

We will probably need to see what is listed in your
\windows\inf\setupapi.dev.log file to see what went wrong. If you want to
send the file, it should compress well in a zip. If you want to try to take
a look at it, start at the bottom and search up for instances of !! in the
log.

Gary Waliczek [MSFT]

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Pete Z" <> wrote in message
news:...
>I uninstalled the WMDC and downloaded the WMDC 6 RTM version tonight and
>still cannot get my PPC to be recognised by my Vista Ultimate PC
>
> When I plug in my IMate PPC phone, I get message "installing device driver
> software" then after a few seconds I get the error message "device driver
> software was not installed successfully"
>
> Clicking on the dialog to get more details, I get shown a window telling
> me:
> "Please consult with your device manufacturer for assitance getting this
> device installed" Windows Mobile device: failed
>
> Windows Update Mgr seems not to want to download the correct drivers for
> it.
>
> Help please ! (btw I am running Office 2007 too)

Well, it looks like this is the important part:
!!! dvi: Device not started: Device has problem: 0x0a:
CM_PROB_FAILED_START.

The portable device interface failed to load for your device which means you
cannot browse files, import photos, etc. And the WMDC UI will not see the
device as connected. Does the Activesync application on the device say that
it is connected?

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Pete Z" <> wrote in message
news:...
> Hi Gary,
>
> Here is the segment of the file (straight after a power up)
>
>>>> [Device Install (Hardware initiated) -
>>>> ActiveSyncWPDEnumerator\UMB\2&306b293b&0&ACTIVESYN CWPDDEVICE-72E78F0C-6C67-6A29-3684-4A7913004CEE-]
>>>> Section start 2007/02/08 17:49:06.847
> ump: Creating Install Process: DrvInst.exe 17:49:06.849
> ndv: Retrieving device info...
> ndv: Setting device parameters...
> ndv: Building driver list...
> dvi: {Build Driver List} 17:49:07.349
> dvi: Searching for hardware ID(s):
> dvi: tcpip\windows_mobile_device
> dvi: Searching for compatible ID(s):
> dvi: tcpip\windows_mobile_device
> dvi: Enumerating INFs from path list 'C:\Windows\INF'
> inf: Opened PNF:
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> dvi: Created Driver Node:
> dvi: HardwareID - TCPIP\WINDOWS_MOBILE_DEVICE
> dvi: InfName -
> C:\Windows\System32\DriverStore\FileRepository\wpd rapi.inf_3942e2cb\wpdrapi.inf
> dvi: DevDesc - Windows Mobile device
> dvi: DrvDesc - Windows Mobile device
> dvi: Provider - Microsoft
> dvi: Mfg - (Standard Windows Mobile devices)
> dvi: ModelsSec - Microsoft.NTx86
> dvi: InstallSec - WINDOWSMOBILE_WPD_DEVICE
> dvi: ActualSec - WINDOWSMOBILE_WPD_DEVICE.NT
> dvi: Rank - 0x0dff0000
> dvi: Signer - microsoft windows
> dvi: Signer Score - INBOX
> dvi: DrvDate - 06/21/2006
> dvi: Version - 6.0.6000.16386
> inf: Searched 1 potential matches in published INF directory
> inf: Searched 57 INFs in directory: 'C:\Windows\INF'
> dvi: {Build Driver List - exit(0x00000000)} 17:49:08.719
> ndv: Selecting best match...
> dvi: {DIF_SELECTBESTCOMPATDRV} 17:49:08.721
> dvi: Using exported function 'WpdClassInstaller' in module
> 'C:\Windows\system32\wpd_ci.dll'.
> dvi: Class installer == wpd_ci.dll,WpdClassInstaller
> dvi: Using exported function 'CoDeviceInstall' in module
> 'C:\Windows\system32\WUDFCoInstaller.dll'.
> dvi: CoInstaller 1 == WUDFCoInstaller.dll
> dvi: CoInstaller 1: Enter 17:49:08.920
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:08.921
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:08.922
> dvi: {Select Best Driver}
> dvi: Selected driver installs from section
> [WINDOWSMOBILE_WPD_DEVICE] in
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'.
> dvi: Class GUID of device remains:
> {eec5ad98-8080-425f-922a-dabf3de3f69a}.
> dvi: Set selected driver complete.
> dvi: Selected:
> dvi: Description - [Windows Mobile device]
> dvi: InfFile -
> [c:\windows\system32\driverstore\filerepository\wpd rapi.inf_3942e2cb\wpdrapi.inf]
> dvi: Section - [WINDOWSMOBILE_WPD_DEVICE]
> dvi: Signer - [microsoft windows]
> dvi: Rank - [0x0dff0000]
> dvi: {Select Best Driver - exit(0x00000000)}
> dvi: Default installer: Exit
> dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 17:49:08.934
> ndv: Driver selected, now performing install...
> ndv: {Core Device Install}
> inf: Opened PNF: 'C:\Windows\INF\wpdrapi.inf' ([strings.0409]
> <src=drvstore>)
> inf: Opened PNF: 'C:\Windows\INF\wpdrapi.inf' ([strings.0409]
> <src=drvstore>)
> dvi: {DIF_ALLOW_INSTALL} 17:49:09.970
> dvi: CoInstaller 1: Enter 17:49:09.971
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:09.972
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:10.025
> dvi: Default installer: Exit
> dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 17:49:10.036
> ndv: Installing files...
> dvi: {DIF_INSTALLDEVICEFILES} 17:49:10.058
> dvi: CoInstaller 1: Enter 17:49:10.058
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:10.060
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:10.061
> dvi: {Install FILES}
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT]}
> inf:
> CopyFiles=WPDRAPIDRIVER_COMMON.Files.Core (wpdrapi.inf line 44)
> flq: CopyFiles from an inbox inf.
> cpy: Open PnpLockdownPolicy: Err=2. This is
> OK. Use LockDownPolicyDefault
> flq: QueueSingleCopy...
> flq: Inf :
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> flq: SourceInf:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> flq: SourceSection: [sourcedisksfiles]
> flq: Source root path based on SourceInf
> flq: SourceRootPath:
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_3942e2cb'
> flq: {FILE_QUEUE_COPY}
> flq: CopyStyle - 0x09000000
> flq: SourceRootPath -
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_3942e2cb'
> flq: SourceFilename - 'WpdRapi.dll'
> flq: TargetDirectory-
> 'C:\Windows\system32\DRIVERS\UMDF'
> flq: TargetFilename - 'WpdRapi.dll'
> flq: SourceDesc - 'windows cd'
> flq: {FILE_QUEUE_COPY exit(0x00000000)}
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
> dvi: Processing co-installer registration section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers].
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers]}
> inf: No (Copy/Ren/Del)Files directives found
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers] exit (0x00000000)}
> dvi: Co-installers registered.
> dvi: {Install INTERFACES}
> dvi: Installing section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Interfaces]
> dvi: {Install INTERFACES exit 00000000}
> dvi: {Install FILES exit (0x00000000)}
> dvi: Default installer: Exit
> dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 17:49:10.196
> ndv: Pruning file queue...
> dvi: {_SCAN_FILE_QUEUE}
> flq: ScanQ flags=620
> flq: SPQ_SCAN_PRUNE_COPY_QUEUE
> flq: SPQ_SCAN_FILE_COMPARISON
> flq: SPQ_SCAN_ACTIVATE_DRP
> flq: ScanQ number of copy nodes=1
> flq: File 'C:\Windows\system32\DRIVERS\UMDF\WpdRapi.dll'
> pruned from copy.
> sig: Using catalog
> 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\nt5.cat'.
> cpy: DrpSetRegFileProt
> 'C:\Windows\system32\DRIVERS\UMDF\WpdRapi.dll' Status=0 Class=Inbox
> Windows protected
> flq: ScanQ action=200 DoPruning=32
> flq: ScanQ end Validity flags=620 CopyNodes=0
> dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
> ndv: Committing file queue...
> flq: {_COMMIT_FILE_QUEUE}
> flq: CommitQ DelNodes=0 RenNodes=0 BackNodes=0 CopyNodes=0
> flq: {_COMMIT_FILE_QUEUE exit(0x00000000)}
> ndv: Registering CoInstallers...
> dvi: {DIF_REGISTER_COINSTALLERS} 17:49:11.165
> dvi: CoInstaller 1: Enter 17:49:11.168
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:11.169
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:11.171
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers]}
> inf: AddReg=CoInstallers_AddReg (wpdrapi.inf line
> 54)
> inf: HKR,,CoInstallers32,0x00010000,WUDFCoInstaller.dll (wpdrapi.inf
> line 88)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers] exit (0x00000000)}
> dvi: {DIF_DESTROYPRIVATEDATA} 17:49:11.178
> dvi: CoInstaller 1: Enter 17:49:11.179
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:11.180
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:11.181
> dvi: Default installer: Exit
> dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)}
> 17:49:11.182
> dvi: Co-installers registered.
> dvi: Default installer: Exit
> dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 17:49:11.184
> ndv: Installing interfaces...
> dvi: {DIF_INSTALLINTERFACES} 17:49:11.186
> dvi: Using exported function 'CoDeviceInstall' in module
> 'C:\Windows\system32\WUDFCoInstaller.dll'.
> dvi: CoInstaller 1 == WUDFCoInstaller.dll
> dvi: CoInstaller 1: Enter 17:49:11.188
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:11.190
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:11.191
> dvi: {Install INTERFACES}
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> dvi: Installing section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Interfaces]
> dvi: {Install INTERFACES exit 00000000}
> dvi: Default installer: Exit
> dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 17:49:11.198
> ndv: Installing device...
> dvi: {DIF_INSTALLDEVICE} 17:49:11.200
> dvi: CoInstaller 1: Enter 17:49:11.201
> inf: Opened PNF: 'C:\Windows\INF\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:12.234
> dvi: {Install DEVICE}
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> dvi: Processing Registry/Property directives...
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT]}
> inf: 12,UMDF,wpdrapi.dll,1 (wpdrapi.inf line
> 71)
> inf: Processing REGISTERDLLS section
> [WPDRAPIDRIVER_COMMON.RegisterComServers]. Module:
> '%12%\UMDF\wpdrapi.dll', flags: 0x0001, timeout: 60s, Arguments: '(null)'.
> inf: Calling 'DllRegisterServer' in OLE
> Control 'C:\Windows\system32\DRIVERS\UMDF\wpdrapi.dll' succeeded.
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Hw]}
> inf: AddReg=WPDRAPIDRIVER_COMMON.AutoPlayRegistration (wpdrapi.inf
> line 48)
> inf: HKR,,EnableDefaultAutoPlaySupport,0x10001,1 (wpdrapi.inf line
> 74)
> inf: HKR,,EnableLegacySupport,0x10001,1
> (wpdrapi.inf line 75)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Hw] exit (0x00000000)}
> dvi: {Writing Device Properties}
> dvi: Provider name=Microsoft
> dvi: DriverDate 06/21/2006
> dvi: DriverVersion=6.0.6000.16386
> dvi: Class name=WPD
> dvi: Manufacturer=(Standard Windows Mobile
> devices)
> dvi: Matching
> DeviceID=tcpip\windows_mobile_device
> dvi: Strong
> Name=wpdrapi.inf:Microsoft.NTx86:WINDOWSMOBILE_WPD _DEVICE:6.0.6000.16386:tcpip\windows_mobile_device
> dvi: {Writing Device Properties - Complete}
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Services]}
> inf: AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall (wpdrapi.inf
> line 51)
> inf: ServiceType=1 (wpdrapi.inf line 82)
> inf: StartType=3 (wpdrapi.inf line 83)
> inf: ErrorControl=1 (wpdrapi.inf line 84)
> inf: ServiceBinary=C:\Windows\system32\DRIVERS\WUDFRd.s ys
> (wpdrapi.inf line 85)
> dvi: Add Service: Modified existing service
> 'WUDFRd'.
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Services] exit(0x00000000)}
> dvi: {Install DEVICE exit (0x00000000)}
> dvi: Writing common driver property settings.
> dvi: DriverDescription=Windows Mobile device
> dvi: DeviceDisplayName=Windows Mobile device
> dvi: Install Device: Restarting device. 17:49:12.583
> dvi: Install Device: Restarting device completed.
> 17:49:14.054
> !!! dvi: Device not started: Device has problem: 0x0a:
> CM_PROB_FAILED_START.
> dvi: Class installer: Exit
> dvi: CoInstaller 1: Enter (Post Processing) 17:49:14.097
> dvi: CoInstaller 1: Exit (Post Processing)
> dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 17:49:14.239
> dvi: {Build Driver List} 17:49:14.240
> ! dvi: Driver list already built
> dvi: {Build Driver List - exit(0x00000000)} 17:49:14.242
> dvi: {DIF_SELECTBESTCOMPATDRV} 17:49:14.242
> dvi: CoInstaller 1: Enter 17:49:14.243
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:14.244
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:14.246
> dvi: {Select Best Driver}
> dvi: Selected driver installs from section
> [WINDOWSMOBILE_WPD_DEVICE] in
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_3942e2cb\wpdrapi.inf'.
> dvi: Class GUID of device remains:
> {eec5ad98-8080-425f-922a-dabf3de3f69a}.
> dvi: Set selected driver complete.
> dvi: Selected:
> dvi: Description - [Windows Mobile device]
> dvi: InfFile -
> [c:\windows\system32\driverstore\filerepository\wpd rapi.inf_3942e2cb\wpdrapi.inf]
> dvi: Section - [WINDOWSMOBILE_WPD_DEVICE]
> dvi: Signer - [microsoft windows]
> dvi: Rank - [0x0dff0000]
> dvi: {Select Best Driver - exit(0x00000000)}
> dvi: Default installer: Exit
> dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 17:49:14.281
> dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 17:49:14.282
> dvi: CoInstaller 1: Enter 17:49:14.283
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:14.284
> dvi: Class installer: Exit
> dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0x00000000)}
> 17:49:14.311
> ndv: Device install status=0x00000000
> ndv: Performing device install final cleanup...
> ! ndv: Queueing up error report since device has a PnP problem...
> ndv: {Core Device Install - exit(0x00000000)}
> dvi: {DIF_DESTROYPRIVATEDATA} 17:49:18.271
> dvi: CoInstaller 1: Enter 17:49:18.271
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 17:49:18.272
> dvi: Class installer: Exit
> dvi: Default installer: Enter 17:49:18.273
> dvi: Default installer: Exit
> dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 17:49:18.275
> ump: Server install process exited with code 0x00000000 17:49:18.282
> <<< Section end 2007/02/08 17:49:18.284
> <<< [Exit status: SUCCESS]
>
>
>
>
>
> "Gary Waliczek [MSFT]" <> wrote in message
> news:%...
>> We will probably need to see what is listed in your
>> \windows\inf\setupapi.dev.log file to see what went wrong. If you want
>> to send the file, it should compress well in a zip. If you want to try
>> to take a look at it, start at the bottom and search up for instances of
>> !! in the log.
>>
>> Gary Waliczek [MSFT]
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "Pete Z" <> wrote in message
>> news:...
>>>I uninstalled the WMDC and downloaded the WMDC 6 RTM version tonight and
>>>still cannot get my PPC to be recognised by my Vista Ultimate PC
>>>
>>> When I plug in my IMate PPC phone, I get message "installing device
>>> driver software" then after a few seconds I get the error message
>>> "device driver software was not installed successfully"
>>>
>>> Clicking on the dialog to get more details, I get shown a window telling
>>> me:
>>> "Please consult with your device manufacturer for assitance getting this
>>> device installed" Windows Mobile device: failed
>>>
>>> Windows Update Mgr seems not to want to download the correct drivers for
>>> it.
>>>
>>> Help please ! (btw I am running Office 2007 too)
>>
>

My guess is that if you look in the device manager (start->Computer, right
click, manage) you'll find a portable devices node with a device under it
that has ! on it. This is the driver that needs to load no matter how you
connect (USB, Bluetooth, IR, etc) and if the device shows connected on USB,
the higher level driver is probably what isn't working.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Pete Z" <> wrote in message
news:...
> Hi Gary,
>
> "Does the Activesync application on the device say that it is connected?"
>
> Yes, it first says authenticating, then authenticated, then tapping on the
> status icon (on the phone) shows me that I'm "connected"
>
> Then Vista displays the dialog "installing device driver software" then
> after a few seconds I get the error message
> "device driver software was not installed successfully"
>
> I realise your doing this support pro bono so any help would be
> appreciated.
>
> cheers,
>
> - Simon
>
>
> "Gary Waliczek [MSFT]" <> wrote in message
> news:...
>> Well, it looks like this is the important part:
>> !!! dvi: Device not started: Device has problem: 0x0a:
>> CM_PROB_FAILED_START.
>>
>> The portable device interface failed to load for your device which means
>> you cannot browse files, import photos, etc. And the WMDC UI will not
>> see the device as connected. Does the Activesync application on the
>> device say that it is connected?
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>

I am having exactly the same problem with trying to connect my IPAQ HX2495.
HP says it is a Microsoft problem. Are there different drivers we should be
using? Do we just have to wait for MS to push out some new drivers?

"Gary Waliczek [MSFT]" wrote:

> My guess is that if you look in the device manager (start->Computer, right
> click, manage) you'll find a portable devices node with a device under it
> that has ! on it. This is the driver that needs to load no matter how you
> connect (USB, Bluetooth, IR, etc) and if the device shows connected on USB,
> the higher level driver is probably what isn't working.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Pete Z" <> wrote in message
> news:...
> > Hi Gary,
> >
> > "Does the Activesync application on the device say that it is connected?"
> >
> > Yes, it first says authenticating, then authenticated, then tapping on the
> > status icon (on the phone) shows me that I'm "connected"
> >
> > Then Vista displays the dialog "installing device driver software" then
> > after a few seconds I get the error message
> > "device driver software was not installed successfully"
> >
> > I realise your doing this support pro bono so any help would be
> > appreciated.
> >
> > cheers,
> >
> > - Simon
> >
> >
> > "Gary Waliczek [MSFT]" <> wrote in message
> > news:...
> >> Well, it looks like this is the important part:
> >> !!! dvi: Device not started: Device has problem: 0x0a:
> >> CM_PROB_FAILED_START.
> >>
> >> The portable device interface failed to load for your device which means
> >> you cannot browse files, import photos, etc. And the WMDC UI will not
> >> see the device as connected. Does the Activesync application on the
> >> device say that it is connected?
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >
>
>
>

PocketPC Faq has an excellent resource that might help you here, check out:

http://www.pocketpcfaq.com/faqs/wmdc/event-log.htm
for possible problems and
http://www.pocketpcfaq.com/faqs/wmdc/t-shoot-wmdc.htm
for potential fixes

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Lonepinedm" <> wrote in message
news:51F84143-228E-40FA-AE1A-...
>I am having exactly the same problem with trying to connect my IPAQ HX2495.
> HP says it is a Microsoft problem. Are there different drivers we should
> be
> using? Do we just have to wait for MS to push out some new drivers?
>
> "Gary Waliczek [MSFT]" wrote:
>
>> My guess is that if you look in the device manager (start->Computer,
>> right
>> click, manage) you'll find a portable devices node with a device under it
>> that has ! on it. This is the driver that needs to load no matter how
>> you
>> connect (USB, Bluetooth, IR, etc) and if the device shows connected on
>> USB,
>> the higher level driver is probably what isn't working.
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "Pete Z" <> wrote in message
>> news:...
>> > Hi Gary,
>> >
>> > "Does the Activesync application on the device say that it is
>> > connected?"
>> >
>> > Yes, it first says authenticating, then authenticated, then tapping on
>> > the
>> > status icon (on the phone) shows me that I'm "connected"
>> >
>> > Then Vista displays the dialog "installing device driver software" then
>> > after a few seconds I get the error message
>> > "device driver software was not installed successfully"
>> >
>> > I realise your doing this support pro bono so any help would be
>> > appreciated.
>> >
>> > cheers,
>> >
>> > - Simon
>> >
>> >
>> > "Gary Waliczek [MSFT]" <> wrote in message
>> > news:...
>> >> Well, it looks like this is the important part:
>> >> !!! dvi: Device not started: Device has problem: 0x0a:
>> >> CM_PROB_FAILED_START.
>> >>
>> >> The portable device interface failed to load for your device which
>> >> means
>> >> you cannot browse files, import photos, etc. And the WMDC UI will not
>> >> see the device as connected. Does the Activesync application on the
>> >> device say that it is connected?
>> >>
>> >> --
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >
>>
>>
>>