Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- From: jp2msft <jp2msft@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 10 Dec 2008 08:42:10 -0800
Mobile 5? I _think_ you mean Windows Mobile 5. And if you started with
Pocket PCs, you more specifically mean Windows Mobile Classic. But if
you tell us the model number, at least some of us could get the specs.
The old devices are running Windows Mobile 2003, commonly referred to as
Pocket PC 2003 [information for Windows Mobile Classic (WMC) is not as easy
to find as it is for Pocket PC, hence my use of the later term]. They were
manufactured by Symbol Technologies, Inc, but this company has since been
bought out by various other vendors. It is currently owned by Motorola, which
does not offer support for the older systems. For documentation purposes, the
Model Number of these PPC/WMC devices is PPT8846-R3BZ10WW (you didn't say
whether you wanted the model number of the old devices or the new, so I'm
going to give you both).
The new devices were ordered with Windows Mobile 5. They are the Datalogic
Falcon 4410. A link to information on them is here:
http://www.racoindustries.com/pscfalcon4420_4410color.htm
(except ours were ordered with M5 instead of the Windows CE .NET operating
system)
I'm sorry, but I don't understand this paragraph.
Let me rephrase, then:
In Visual Studio, we could run the Pocket PC emulators and have network
connections using the PC that is running the emulator. We can not get the
Windows Mobile emulators to access the network through the PC running the
emulator (even though it is setup correctly in the Device Options menu of
Visual Studio).
Our version of ActiveSync is 4.5 (the latest, to my knowledge).
The Pocket PC devices connect to the PC using the Symbol charging cratle,
which connects to the PC using a serial cable. ActiveSync always connects to
the old Pocket PC devices using this setup.
The Windows Mobile 5 devices connect to the PC using the Datalogic charging
cratle, which connects to the PC using a USB cable (It is connected directly
to the PC with no hubs other than those which are built into the PC's
motherboard). Sometimes ActiveSync will connect with these devices, but not
always. When ActiveSync does connect, often (over 80% of the time) the
connection will be lost for no apparent reason.
ActiveSync can be "temperamental". The USB hardware can make a
difference. If you are using a hub, try bypassing it.
I've tried using different USB ports on my machine, but all give the same
results. Is there another product to connect with devices besides ActiveSync?
When I do manage to establish a successful connection with ActiveSync, I try
to deply my application using Visual Studio as quickly as possible. If the
ActiveSync connection is lost during the deployment, Visual Studio continues
to try to deply, there is no way to cancel Visual Studio's deployment, and
Visual Studio appears to wait indefinitely for this deployment to complete -
In other words, Visual Studio is locked into a never ending loop.
Is there any other information I can give?
Does this explanation clearer?
"r_z_aret@xxxxxxxxxxxx" wrote:
.With the PPC devices, we update the software by connecting with ActiveSync
4.5 and transferring the new CAB files over using Windows Explorer. The PPC
devices used an Ethernet to Serial connection to connect the Ethernet socket
on the PPC's charging base to the RS-232 serial port of the development
computer (MyPC) running WinXP Pro and Visual Studio 2005 Pro (VS2005).
The new M5 devices have a USB connector on the back of their charging base
that plugs into the USB port on MyPC.
In the Emulators: When debugging with VS2005 using PPC, everything works.
When debugging with VS2005 using M5, the network connection does not use
MyPC's network connection, like I have checked in the Emulator Properties >
Network settings.
I'm sorry, but I don't understand this paragraph.
Using the Device: I can try to debug using the M5 device, but before the
application is fully deployed, ActiveSync drops the connection. VS2005 can
not be stopped during this deployment, and it must be killed using Task
Manager.
When an M5 device is connected to MyPC, WinXP installs the new hardware,
then starts ActiveSync. I can try to transfer my application by dropping the
new CAB files over using Windows Explorer, but this often fails when
ActiveSync drops its connection.
ActiveSync can be "temperamental". The USB hardware can make a
difference. If you are using a hub, try bypassing it. Also, cable and
adapter quality matters. I built one of my computers in the early days
of USB, and it just barely supports modern USB devices.
Has anyone had similar problems that they know how to get around?
I have no idea how to get these new devices to work.
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 400
Boston, MA 02116
www.penfact.com
- Follow-Ups:
- Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- From: Doug Forster
- Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- From: r_z_aret
- Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- References:
- Mobile 5 and Pocket PC 2003 (Mobile 2003)
- From: jp2msft
- Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- From: r_z_aret
- Mobile 5 and Pocket PC 2003 (Mobile 2003)
- Prev by Date: Re: Is it necessary to sign Pocket PC applications ?
- Next by Date: Re: Device Sleep and Wake-Up
- Previous by thread: Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- Next by thread: Re: Mobile 5 and Pocket PC 2003 (Mobile 2003)
- Index(es):
Relevant Pages
|
