By Chris De Herrera
Copyright 1998-2007
All Rights Reserved
A member of the
Talksites Family
of WebsitesWindows and
Windows CE are trademarks of
Microsoft
Corporation and are used
under license from owner.
CEWindows.NET is not
associated with Microsoft
Corporation.
All Trademarks are owned
by their respective companies. |
|
Top Connection Issues
with iPAQ Pocket PC,
Plus Recommended Procedures
By Lilla Slater, Copyright 2000, All Rights Reserved
Revised 10/14/2000
[an error occurred while processing this directive]
Introduction
Below is an *important* post I found in Compaq's iPAQ/Handhelds
Support Forum. While this document is on the iPAQ, I recommend this
article to all Pocket PC users' experiencing ActiveSync USB connection
problems.
This document provides a starting point for iPAQ users experiencing
problems.
Important: Put a big X through the instructions on the Compaq iPAQ CD's
cardboard sleeve that accompanied your iPAQ, as the instructions are
wrong and cause problems. If you already followed these instructions, then
follow the instructions in Procedure 3b
to get a clean start.
New iPAQ's ship with a yellow page containing new
installation instructions. If your iPAQ shipped without this page, as
will be the case with early product iPAQ's, you might want to print (or
save as a file) this document for your future reference. This image
is courtesy of Steve Perry, Microsoft MVP - Windows CE, who scanned and
posted this to the microsoft.public.pocketpc.binaries
newsgroup on 4 Oct 2000.
When installing/reinstalling ActiveSync, follow
the instructions in Procedure 3a.
Lilla
Forum: http://forum.compaq.com/mb3/user/main.html
Topic: Handhelds Message #76397
Subject: RE: Connecting with iPAQ - USB
From: Compaq - troy j 10/05/00 12:35:44
Connection issues with the iPAQ Pocket PC
We've seen four major issues that affect connection and synchronizing the
units. From the most common to the least common they are:
Issue #1: USB Connectivity is only for Windows 98 or Windows 2000.
If you have Windows 95 or Windows NT 4.0 then you will need the serial
cradle to connect and synchronize reliably. Additionally, we have heard
from some customers that they have used a product called
"USBRetail". It is from http://www.bluewatersystems.com/products_USB_Retail.html
and some customers have had success with it connecting handheld drives
under Windows NT with a USB connection. Please remember, that
troubleshooting for this product should be directed to Blue Water's
Technical Support.
Issue #2: Microsoft has released a new build of ActiveSync 3.1 that
has several fixes to improve synchronization. The latest version as of the
time of this writing is v3.1 build 9587. The latest release is available
for download from PocketPC.com http://www.microsoft.com/pocketpc/downloads/
Issue #3: The iPAQ H3600 series USB cradle uses a UHCI (Universal
Host Control Interface) USB. Some units use the less common OHCI (Open
Host Control Interface.) We cannot guarantee that the iPAQ will work
flawlessly when connected to a machine using OHCI. Normally it will
recognize that you connected a device to it but it just shows up as an
"Unknown Device." This is the same issue seen with many USB
devices. Although a UHCI USB controller is preferred, remember the iPAQ
WILL synchronize with some OHCI equipped hosts. To resolve this, try the
following:
If the controller shows a VIA chipset, then go to http://www.viatech.com/drivers/
and get the latest version of the USB Filter software (currently, v1.08).
Procedure 3a. Assuming you have not yet attached
the unit to the USB port and have not installed ActiveSync, then follow
these simple steps:
- Turn on and
configure the iPAQ with the appropriate user info, then place it
in the cradle while still on, displaying the "Today" screen.
Do not insert the USB cable into the host computer.
- Install Outlook
2000 by inserting the ActiveSync CD, canceling the ActiveSync
install process, and browsing to the X:\Extras\Outlook folder and
launching setup (where X: is the user's CD-ROM drive designation). You
will be prompted to reboot to complete installation. Please do so and
then configure and run Outlook 2000.
- Now
launch the ActiveSync installation and proceed until you see the
screen that says "Get Connected," at which point you should
now plug the USB cable into the unit and the iPAQ will be properly
detected and a partnership created.
Procedure 3b. If you have
varied from this scenario in any way, please do the following:
- Remove all USB devices from the main computer
(an exception can be made if you're using a USB mouse)
- Configure the iPAQ as describe in Step
1 of Procedure 3a, above.
- Uninstall Microsoft ActiveSync 3.1 from the
Add/Remove Software Control Panel.
- Boot to Safe Mode and remove all "Unknown
Devices" found in the "Other Devices" category of
Device Manager as well as all devices found in the "USB" or
"USB Devices" categories. NOTE: In Windows 2000 it is
not necessary to go to safe mode. Simply select the "Show All
Devices" option in Device Manager.
- Reboot to allow redetection of the built-in
USB devices.
- Install and configure Outlook 2000 as
described in Step 2 of
Procedure 3a above.
- Install ActiveSync as described in Step
3 of Procedure 3a above.
If you're still having problems, make sure you
have the latest version ActiveSync, that your USB ports are not disabled
in BIOS and that the cradle works on another unit (to be sure you don't
have a bad cradle). If so, try doing a soft reset on the iPAQ and then
reboot the main computer, leaving the iPAQ in the cradle and the USB cable
attached.
When troubleshooting connectivity issues, don't forget the soft reset.
This has resolved a large number of connectivity issues that have been
escalated here.
Issue #4: Microsoft has an issue where USB devices may not work in
Windows 98 SE if you have an AMD CPU that is 350Mhz or higher and a VIA
Technologies USB Controller. It is a timing issue and they have a complete
write-up and a solution here at their site, see http://support.microsoft.com/support/kb/articles/Q240/0/75.ASP
[an error occurred while processing this directive]
Return to Chris
De Herrera's Windows CE Website
|