Discussion:
Mobile 5.0 requirements?
(too old to reply)
Dennis
19 years ago
Permalink
I'm running ActiveSync 3.8 here and using a variety of PPC2002 and PPC2003
PDAs. I just purchased a used HP rx1955 PDA running Windows Mobile 5.0.
When I introduce it to my system (XP) by plugging in the USB cable, I get a
message about Generic RNDIS and I'm stopped.

The PDA did not come with a CD so I don't have its installation stuff. I'm
going to go onto the HP site and see if I can download it.

But, my question is: will my rx1955 with Mobile 5.0 work with the ActiveSync
3.8 that I'm using now with my other PDAs? Are there other gotchas I
should be aware of as I add this new PDA to my mix?

Thanks,

Dennis Gallagher
Dennis
19 years ago
Permalink
And, if I upgrade to a later version of ActiveSync, say 4.1, will all the
features I use with ActiveSync 3.8 and my PPC2002 and PPC2003 PDAs still
work? I have a vague memory that later versions of ActiveSync discontinued
certain types of functionality but i can't remember the details.
Specifically, I transfer Access databases to and from my PDAs through
ActiveSysnc 3.8 and that will be important to preserve.

Dennis Gallagher
Post by Dennis
I'm running ActiveSync 3.8 here and using a variety of PPC2002 and PPC2003
PDAs. I just purchased a used HP rx1955 PDA running Windows Mobile 5.0.
When I introduce it to my system (XP) by plugging in the USB cable, I get a
message about Generic RNDIS and I'm stopped.
The PDA did not come with a CD so I don't have its installation stuff.
I'm
Post by Dennis
going to go onto the HP site and see if I can download it.
But, my question is: will my rx1955 with Mobile 5.0 work with the ActiveSync
3.8 that I'm using now with my other PDAs? Are there other gotchas I
should be aware of as I add this new PDA to my mix?
Thanks,
Dennis Gallagher
Clint
19 years ago
Permalink
You do need AS 4.1 for WM5.0 machines. And I can't comment on what features
are removed beyond the wireless sync to a desktop. But you very well may be
right about the Access; seems to me I read something about that. And you
can't have both on one machine, AFAIK. Bummer...

Clint
...
Raj Pillai
19 years ago
Permalink
Hi Dennis,

If you need to sync a WM 5.0 device, you will need ActiveSync 4.1. You
other devices should work well under AS 4.1, except you won't be able to use
WiFi sync. This feature is not provided in AS 4.1 due to security reasons.

The database functionality will be available for your older devices even if
you install AS4.1 but not on WM 5.0. For more insight on this refer to
http://groups.google.com/group/microsoft.public.pocketpc.activesync/msg/7cc16ba572eb4cb1
--
Regards,
Raj Pillai
Microsoft MVP - Mobile Devices
http://www.pocketpcfaq.com/raj
...
Raj Pillai
19 years ago
Permalink
Forgot to include - You can download AS 4.1 from
http://www.microsoft.com/windowsmobile/downloads/activesync41.mspx
--
Regards,
Raj Pillai
Microsoft MVP - Mobile Devices
http://www.pocketpcfaq.com/raj
...
Chris De Herrera
19 years ago
Permalink
Hi,
For a complete set of limitations of ActiveSync 4.1 see
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x-limitations.htm
--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

ActiveSync 4.x Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm
...
Dennis
19 years ago
Permalink
Thanks, Clint, Raj and Chris. A great bunch of responses - they gave me
everything I was looking for to be clear about my options.

Cheers all,

Dennis
...
get
Post by Dennis
a
Post by Dennis
message about Generic RNDIS and I'm stopped.
The PDA did not come with a CD so I don't have its installation stuff.
I'm
Post by Dennis
going to go onto the HP site and see if I can download it.
But, my question is: will my rx1955 with Mobile 5.0 work with the
ActiveSync
Post by Dennis
3.8 that I'm using now with my other PDAs? Are there other gotchas I
should be aware of as I add this new PDA to my mix?
Thanks,
Dennis Gallagher
m***@gmail.com
19 years ago
Permalink
I have the same problem about Generic RNDIS message with Ipaq hx2415
just obtained from ebay. I have loaded Activesync 4.1 but that is no
different than 3.7

I did get the cd and installed activesync from it (3.7); but there was
no indication of drivers being loaded.


I think the PDA is not being correctly recognized and drivers not
loaded.

HP website makes no mention of drivers for the host computer.

Please get back to what can be causing the RNDIS message instead of
capabilities of 4.1!
Post by Dennis
I'm running ActiveSync 3.8 here and using a variety of PPC2002 and PPC2003
PDAs. I just purchased a used HP rx1955 PDA running Windows Mobile 5.0.
When I introduce it to my system (XP) by plugging in the USB cable, I get a
message about Generic RNDIS and I'm stopped.
Carl Wolz [MSFT]
19 years ago
Permalink
The drivers are installed as part of the installation of the ActiveSync 4.1
processes.



The installation of ActiveSync 4.1 should have handled all of this for you.
If the installation asked for a reboot, it needs to be done before
connecting in the device.



You can manually point to the driver. In the update the driver in the Device
manager and select "have disk". Point it to the WceRndis.inf file in the
ActiveSync Driver directory.
--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.
...
m***@gmail.com
19 years ago
Permalink
I get this error message after installing the driver pointed to and
then another it requests.

This device cannot start. (Code 10)
Post by Carl Wolz [MSFT]
You can manually point to the driver. In the update the driver in the Device
manager and select "have disk". Point it to the WceRndis.inf file in the
ActiveSync Driver directory.
Carl Wolz [MSFT]
19 years ago
Permalink
In your PC's windows directory, there is a setupapi.log file. Can you post
the ending of the file?
--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.
Post by m***@gmail.com
I get this error message after installing the driver pointed to and
then another it requests.
This device cannot start. (Code 10)
Post by Carl Wolz [MSFT]
You can manually point to the driver. In the update the driver in the Device
manager and select "have disk". Point it to the WceRndis.inf file in the
ActiveSync Driver directory.
m***@gmail.com
19 years ago
Permalink
#-018 Searching for compatible ID(s):
usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#-019 Searching for hardware ID(s):
usb\vid_8086&pid_f003&rev_0000,usb\vid_8086&pid_f003
#-018 Searching for compatible ID(s):
usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#I022 Found "USB\Class_EF&SubClass_01&Prot_01" in c:\program
files\microsoft activesync\drivers\WceRndis.inf; Device: "Windows
Mobile-based Device"; Driver: "Windows Mobile-based Device"; Provider:
"Microsoft Corporation"; Mfg: "Microsoft Corporation"; Section name:
"RNDIS.NT.5.1".
#I023 Actual install section: [RNDIS.NT.5.1]. Rank: 0x00002000.
Effective driver date: 10/28/2005.
#-124 Doing copy-only install of
"USB\VID_8086&PID_F003\3037910F-41B2-F10A-A800-0050BF1977E0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [RNDIS.NT.5.1.Interfaces] from "c:\program
files\microsoft activesync\drivers\wcerndis.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"USB\VID_8086&PID_F003\3037910F-41B2-F10A-A800-0050BF1977E0".
#I163 Device not started: Device has problem: 0x0a:
CM_PROB_FAILED_START.
#I121 Device install of
"USB\VID_8086&PID_F003\3037910F-41B2-F10A-A800-0050BF1977E0" finished
successfully.
[2006/03/06 09:25:40 3716.1413]
#-198 Command line processed: "C:\WINNT\System32\mmc.exe"
C:\WINNT\system32\devmgmt.msc /s
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
usb\vid_8086&pid_f003&rev_0000,usb\vid_8086&pid_f003
#-018 Searching for compatible ID(s):
usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#I022 Found "USB\Class_EF&SubClass_01&Prot_01" in
C:\WINNT\inf\oem27.inf; Device: "Windows Mobile-based Device"; Driver:
"Windows Mobile-based Device"; Provider: "Microsoft Corporation"; Mfg:
"Microsoft Corporation"; Section name: "RNDIS.NT.5.1".
#I023 Actual install section: [RNDIS.NT.5.1]. Rank: 0x00002000.
Effective driver date: 10/28/2005.
#-019 Searching for hardware ID(s):
usb\vid_8086&pid_f003&rev_0000,usb\vid_8086&pid_f003
#-018 Searching for compatible ID(s):
usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#-019 Searching for hardware ID(s):
usb\vid_8086&pid_f003&rev_0000,usb\vid_8086&pid_f003
#-018 Searching for compatible ID(s):
usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#-019 Searching for hardware ID(s):
usb\vid_8086&pid_f003&rev_0000,usb\vid_8086&pid_f003
#-018 Searching for compatible ID(s):
usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#I022 Found "USB\Class_EF&SubClass_01&Prot_01" in c:\program
files\microsoft activesync\drivers\WceRndis.inf; Device: "Windows
Mobile-based Device"; Driver: "Windows Mobile-based Device"; Provider:
"Microsoft Corporation"; Mfg: "Microsoft Corporation"; Section name:
"RNDIS.NT.5.1".
#I023 Actual install section: [RNDIS.NT.5.1]. Rank: 0x00002000.
Effective driver date: 10/28/2005.
#-124 Doing copy-only install of
"USB\VID_8086&PID_F003\3037910F-41B2-F10A-A800-0050BF1977E0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [RNDIS.NT.5.1.Interfaces] from "c:\program
files\microsoft activesync\drivers\wcerndis.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"USB\VID_8086&PID_F003\3037910F-41B2-F10A-A800-0050BF1977E0".
#I163 Device not started: Device has problem: 0x0a:
CM_PROB_FAILED_START.
#I121 Device install of
"USB\VID_8086&PID_F003\3037910F-41B2-F10A-A800-0050BF1977E0" finished
successfully.
Carl Wolz [MSFT]
19 years ago
Permalink
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
It's failing to start.

What is the version for rndismpx.sys and usb8023x.sys?? (in the
windows\system32\drivers)

I'm seeing on my PC
rndismpx.sys 5.1.2600.2781 (xpsp.051020-1729)
usb8023x.sys 5.1.2600.2781 (xpsp.051020-1729)

Is there any VPN software or byte optimizer install??
--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.
...
m***@gmail.com
19 years ago
Permalink
unit was defective and replaced.

Continue reading on narkive:
Loading...