Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

fail to connect to IPAQ H5450

2 views
Skip to first unread message

Dan

unread,
Jul 3, 2003, 7:16:46 AM7/3/03
to
Visual Studio .NET 2003 seems unable to connect to my IPAQ H5450 device;
anyway, ActiveSync works fine and I can explore the contents of the device
from the same machine; further, it can connect to other devices (e.g. IPAQ
H3870). I have seeen older posts on the same problem, and someone suggested
to use a reg file from C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\WinCE> Utilities\WinCE Proxy Ports Reg. I have no
such directory in my machine or in the .NET cd (CompactFrameworkSDK includes
only 2 folders named ConnectionManager and v1.0.5000, and no reg file in
them). Could anybody suggest a solution for this problem?

Thanx!


Peter Foot [MVP]

unread,
Jul 3, 2003, 7:25:19 AM7/3/03
to
I think the tools referred to are part of the Add-On pack for CE.NET
http://www.microsoft.com/downloads/details.aspx?FamilyID=7ec99ca6-2095-4086-b0cc-7c6c39b28762&DisplayLang=en

I'm not sure if the method works I don't have a 54xx.

Peter

--
Peter Foot
Windows Embedded MVP

In The Hand
http://www.inthehand.com
Handheld Interactive Reference Guides

"Dan" <fu...@iol.it> wrote in message
news:upKJeSVQ...@TK2MSFTNGP12.phx.gbl...

Alberto Silva

unread,
Jul 3, 2003, 7:41:06 AM7/3/03
to
Hi Dan,
I still haven't found a solutions for this problem.
Several sugestions have been presented but none of them worked for me, as
well as for many other users.
In my particular case, my iPaq 5450 works fine with my home PC, with VS.net
2003, but not with my office notebook, although it works fine with both for
synchronisation and the old eVB.

Please keep us informed.

Alberto Silva

"Dan" <fu...@iol.it> escreveu na mensagem
news:upKJeSVQ...@TK2MSFTNGP12.phx.gbl...

Rich Hanbidge [MSFT]

unread,
Jul 11, 2003, 7:25:20 PM7/11/03
to
Try this out:

For general device connectivity issues, I recommend that you download and
install the "Windows CE Utilities for Visual Studio .NET 2003 Add-on pack,
which can be found at
http://smartdevices.microsoftdev.com/Downloads/default.aspx.

Once the add-on is installed, there will be a WinCE Utilities folder off
the \Program Files\Microsoft Visual Studio .NET 2003\CompactFramework
directory. Read the Readme.htm file for more information on what the
requirements are for device connectivity with ActiveSync.

For device connectivity issue, also make sure that you check the following:

1) For machines that have been upgraded from an earlier VS .NET 2003 beta
release, you may need to delete the Connection Manager data store files,
found in the %userprofile%\Local Settings\Application
Data\Microsoft\VisualStudio\devices\7.1 directory.

This is especially true if you've uninstalled an earlier beta release of VS
NET 2003, and then installed a later version in a diferent drive/directory
path, or if you've done a re-install of VS .NET at some point, which also
may result in VS .NET 2003 being installed in a different drive/directory
path then the previous installation.

2) Do a hard reset of the Pocket PC device, to ensure that no older device
side Connection Manager client programs are still installed on the device.

Rich
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Alberto Silva" <albertosilva@_mundomovel_.com>
| References: <upKJeSVQ...@TK2MSFTNGP12.phx.gbl>
| Subject: Re: fail to connect to IPAQ H5450
| Date: Thu, 3 Jul 2003 12:41:06 +0100
| Lines: 20
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <#WHJCgVQ...@TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 194.65.97.178
| Path: cpmsftngxa09.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: cpmsftngxa09.phx.gbl
microsoft.public.dotnet.framework.compactframework:9802
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework

0 new messages