700 Series Question Matrix
Question Index by Applicable Category
(Questions below may be listed in many groups for easier searching)
General:









I have a 700 Mono and want to run PPC 2003, is this possible?
(Page 2)
I have a 700 Color Series (740, 750, or 760) running PPC 2002 and want to upgrade to PPC 2003,
is this possible?
(Page 2)
How am I able to find out what operating system is currently installed?
(Page 2)
I am running PPC 2002, what is the latest build for the 700 Series?
(Page 2)
I am running PPC 2003, what is the latest build for the 700 Series?
(Page 2)
I have never upgraded a terminal before, how do I do that?
(Page 2)
I am just starting to develop for the Intermec Terminals, where can I find any development tools
to help me?
(Page 3)
How can I have my application files all automatically reload on a cold boot?
(Page 3)
How can I have my general settings restore on a cold boot?
(Page 4)
General PPC 2003 (Windows Mobile):












What are the general differences between PPC 2002 and PPC 2003?
How do I order PPC 2003 for my device?
When I order PPC 2003 what is the difference between “A” and “B”?
With PPC 2003 what is the difference between “Upgrade Kit” and “Recovery CD”?
My 802.11 code worked on PPC 2002 but not on PPC 2003, why?
I recently upgraded to PPC 2003 and now my 802.11 radio doesn’t work?
With PPC 2003, why is my Flash File Store now filled with files?
What new features do I get from Intermec with PPC 2003?
My toolkit application worked with PPC 2002 and now won’t with 2003?
Is Bluetooth different from PPC 2002 to 2003?
Is scanning different from PPC 2002 to 2003?
What Bluetooth profiles are supported with PPC 2003?
(Page 5)
(Page 5)
(Page 5)
(Page 5)
(Page 8)
(Page 8)
(Page 6)
(Page 6)
(Page 11)
(Page 12)
(Page 13)
(Page 12)
802.11:



My 802.11 code worked on PPC 2002 but not on PPC 2003, why?
How am I able to program the 802.1x security supplicant?
I recently upgraded to PPC 2003 and now my 802.11 radio doesn’t work?
(Page 8)
(Page 8)
(Page 8)
WWAN:







How do I program for the GPRS or CDMA radio in my unit?
What is the WWAN Toolkit?
Why won’t the example toolkit application run on my handheld?
This is my first WWAN application with the toolkit, how do I get started?
My toolkit application worked with PPC 2002 and now won’t with 2003?
What are my connection parameters for the WWAN radios profile?
Why is my application not creating my connection my manager entry?
(Page 10)
(Page 10)
(Page 11)
(Page 10)
(Page 11)
(Page 11)
(Page 11)
Bluetooth:


Is Bluetooth different from PPC 2002 to 2003?
What Bluetooth profiles are supported with PPC 2003?
(Page 12)
(Page 12)
Scanning:


Is scanning different from PPC 2002 to 2003?
What are my different options for scanning with a 700 Series Mobile Computer?
(Page 12)
(Page 12)
1
General

I have a 700 Mono and want to run PPC 2003, is this possible?
The 700 Mono Series supports PPC 2000 and 2002. The Pocket PC 2002 operating system
and the 700 Mono Line, are in the process of being “End of Lifed.” Orders are taking place
through the year and into Q1 2005 for the terminals. The PPC 2002 OS will be installed onto
the 700 Series through mid-2005. It is our recommendation that those interested in the 700
Mono, look at the 700 Color Series and the 730. Those customers still on PPC 2002 and
looking to continue purchasing units and progressing forward, should look into the PPC 2003
Operating System.

I have a 700 Color Series (740, 750, or 760) running PPC 2002 and want to upgrade to
PPC 2003, is this possible?
The 700 Color Series is broken down into groups and supports according to those. Any 740,
750, or 760 terminals with 32mb of ROM are able to run both the PPC 2002 and 2003
operating systems. It is important to note that the 2003 OS does not have any extra space
on a 32mb ROM unit after a complete install. Any 740, 750, or 760 terminals with 64mb
ROM may only run the PPC 2003 operating system. The 730 Color Terminal may also only
run the PPC 2003 operating system.

How am I able to find what operating system is currently installed?
PPC 2002:
Start>Internet Explorer>Intermec
(gives the full OS build number)
PPC 2003:
Start>Internet Explorer>Intermec
(gives PPC version number)
Start>Programs>File Explorer>Flash File Store>PSMInfo.txt
(gives Intermec Value Add Version)
About Screen:
Start>Settings>About
(gives CE Version PPC built off of)
(3.xx.xx is PPC 2002, 4.xx.xx is PPC 2003)

I am running PPC 2002, what is the latest build for the 700 Series?
700 Mono Series (Professional and Premium) – 2.42
700 Color Series (Professional and Premium) – 1.31.32 (and new PRISM drivers)
Note: Does not include 64mb ROM option nor the 730 Terminal

I am running PPC 2003, what is the latest build for the 700 Series?
November 22, 2004:
Pocket PC Operating System Version 3.40
Intermec Value Add Version 3.14
.Net Compact Framework Version 1.0

I have never upgraded a terminal before, how do I do that?
Directions for the upgrading of each terminal is included within the operating system
download. It is important to note that PPC 2003 can only be upgraded with the use of a SD
card. You can transfer files onto the card via a card reader or active sync. A card reader is
the quickest option. Support can help with any upgrade problems.

I am just starting to develop for the Intermec Terminals, where can I find any
development tools to help me?
Your first stop when developing for an Intermec Terminal would be the Intermec Developer’s
Library (IDL). This is a one-stop-shop to find all of our development tools, toolkits, samples,
2
demos, applications, and free source code. The IDL is free, but a quick registration is
required. As a part of registration, you will be notified when new and updated tools are
available. You can find the IDL at http://www.intermec.com/idl.

How can I have my application files all automatically reload on a cold boot?
PPC 2002:
This is accomplished via a combination of a 2577 directory and a Cabfiles directory. With
PPC 2002 you have the option of using the available Flash File Store space to load your
applications from or a card (Secure Digital or Compact Flash).
- First determine where you want to store your Cabfiles and have them reload on a cold
boot.
- Then go to the IDL Component Toolbox to download the ready made 2577 directory.
- Unzip this directory on your desktop and open the autorun.dat file in Notepad.
- If you want to load from the Flash File Store insert this into the strings:
EXEC "Flash File Store\2577\AutoCab.exe"
CALL "Flash File Store\2577\AutoUser.dat"
- If you want to load from the SD card insert this into the strings:
EXEC "SDMMC DISK\2577\AutoCab.exe"
CALL "SDMMC DISK\2577\AutoUser.dat"
- If you want to load from the CF card insert this into the strings:
EXEC "Storage Card\2577\AutoCab.exe"
CALL "Storage Card\2577\AutoUser.dat"
- Place this directory and it’s three files in the root of your desired location.
- In the root of that same location create a directory called Cabfiles.
- While the Cabfiles you want to autoload are on your desktop, right click and set them to
read only. This will ensure that they remain after they have installed themselves for future
use.
- Place any Cabfiles you want autoloaded inside this Cabfiles directory. You are then
finished!
PPC 2003:
With the introduction of some new programs in 2003 and a required warm boot to complete
the install, it is necessary to change the method of having applications auto reload. Instead
of a 2577 and Cabfiles directory you will now use a method called Persistent Copy. Note that
with PPC 2003 you will need to use a SD card for this process. Unless you have a 64mb
ROM device there is no room in the Flash File Store after a complete install.
- On your SD card create a directory called Persistent Copy.
- Inside this created directory, create one called CabFiles.
- While your Cabfiles are on your desktop, right click and set them to read only.
- Take these Cabfiles and rename them following the scheme below. They will load in
the numbered order that you rename them to. Continue iterating the 0000 until all of your
cabs are renamed.
Example: _0000_copy_cabfilename.CAB
_0001_copy_ cabfilename.CAB
_0002_copy_ cabfilename.CAB
- Put Cabfiles into the Cabfiles directory and you’re done.
 How can I have my general settings restore on a cold boot?
Most general settings on the handheld are stored in the registry. Anything stored in the registry
can either be directly written into your application using the specific registry keys, or can be
reloaded as an entire saved registry. For most people it is easier to just reload the entire saved
registry. Depending on whether you are using a 700 Mono or Color terminal the process is a little
3
different. Saving the registry is handled via the Regflush API. For those that do not wish to
program it into their apps, we have written a small program that does this on its own.
Mono:
- Go out to the IDL Component Toolbox and download regflush.cab.
- Put regflush.cab onto your CF card and execute.
- Set all of the settings you are interested in on your handheld.
- Go into the Start Menu and click on Registry Save.
- You will get a confirmation that your registry has been saved.
Color:
- Go out to the IDL Component Toolbox and download regflush.cab.
- Put regflush.cab onto your SD or CF card (Flash File Store also available) and execute.
- Go to Start>Settings>System>Utilities>Registry Save and enable.
- Note: PPC 2002 allows you to use SD, CR, or Flash File Store
PPC 2003 will only allow you to save to the Flash File Store
- Set all of the settings you are interested in on your handheld.
- Go into the Start Menu and click on Registry Save.
- You will get a confirmation that your registry has been saved.
Your registry is saved in your chosen location as a registry.sys file. This is a hidden file that can
only be shown by either tapping and holding in the area and choosing View All Files or via Active
Sync.
4
General PPC 2003 (Windows Mobile)

What are the general differences between PPC 2002 and PPC 2003?
Pocket IE
802.11b
Bluetooth
Printing
Data Collection
WWAN/Conn. Mgr.
OS Size, FFL
Programming
PPC 2002
PPC 2003 (Windows Mobile)
HTML version 3.0
Java Script 1.2
JScript 1.0
Intermec Configuration
Old dll’s and toolkit
NO 80211pm.dll
PRISM drivers
Socket Stack
Shortcuts on Today
Screen
SPP only supported
profile
LinePrinter Ctrl
HTML version 4.0, Java Script 4.0
JScript 5.5, DHTML, CSS
Ipv6, XHTML Basic, WML 2.0
Intermec & MS Configuration
Updated/New dll’s and toolkit
80211pm.dll for profile management
PRISM drivers with IVA 3.11+
Microsoft Stack
Config in Settings>Connections
3 Profiles Supported
LinePrinter Ctrl
No Changes in Methodology
Configurations Not Saved Configurations Saved
Imager configuration only ICCU With Imager Configuration
through code or imager
Updated decoding
demo
WWAN Toolkit 3.0
WWAN Toolkit 4.1
Work & Internet
My Work Network & My ISP
Premium & Professional Premium Only-Different ROM Sizes
OS Size: 23mb & 17mb
OS Size: 30mb & 55mb
FFL Size: 11mb & 5 mb FFL Size: <1 mb & 30 mb
(remaining
(remaining after install)
after install)
.NET CF Not Included
.NET CF Built In v1.0
Embedded Tools 3.0*
Embedded Tools 4.0
eVb Fully Supported
eVb Runtime Needed
For more detailed information on general MS OS functionality differences please look at the
Intermec PPC 2003 Presentation (available on GSS PPC2003.ppt). Microsoft’s page for the
Window’s Mobile Operating System (PPC 2003) can be found here.

When I order PPC 2003 what is the difference between “A” and “B”?
The A version is a PPC 2003 version BEFORE the new 802.11 radio drivers. The B version
will be the latest PPC 2003 version and will contain/require the new 802.11b PRISM drivers.
The A version will be available through mid 2005 and then only B will be available.
It is recommended to get all customers with new PPC 2003 development to use the B
version.

With PPC 2003 what is the difference between “Upgrade Kit” and “Recovery CD”?
The Recovery CD is what always has to be ordered first for those upgrading to PPC 2003. It contains
the license and one must be ordered for each unit being upgraded. The Upgrade Kit is what you will
order when you need to upgrade your base PPC 2003 version. If you only need to upgrade your IVA,
you can download that from the website at any point. Upgrades to the base 2003 build have to be
ordered via the price guide. You do not need to purchase licenses more than once.
5

How do I order PPC 2003 for my device?
Language
700 Color Worldwide English
(WM2003 v. 3.40;IVA 2.28)
700 Color Spanish
(WM2003 v. 3.40;IVA 2.28)
700 Color French
(WM2003 v. 3.40;IVA 2.28)
700 Color Worldwide English
(WM2003 v. 3.40;IVA 3.14)
700 Color Spanish
(WM2003 v. 3.40;IVA 3.14)
700 Color French
(WM2003 v. 3.40;IVA 3.14)
700 Color Japanese
(WM2003 v. 3.40;IVA 3.14)
700 Color Simplified Chinese
(WM2003 v. 3.40;IVA 3.14)
700 Color Korean
(WM2003 v. 3.40;IVA 3.14)
Upgrade Kit Part Number
235-110-101
235-115-101
235-116-101
235-135-101
235-146-110
235-147-101
November 2004
December 2004
December 2004

With PPC 2003, why is my Flash File Store now filled with files?
With the introduction of PPC 2003 we have now had to take our operating system files out of
general ROM and put them into the Flash File Store. Although this takes up space that used
to be open and available, it now gives you the full ability to customize your IVA. If you are
running a 32 mb ROM device then you are left with less than 1 mb of space after the full OS.
This is generally large enough to save the registry only. If you have a 64 mb ROM device
you are looking at 33mb + of extra space to use after the full OS has been loaded. Most of
these files are dependant on being in the directory structure they are installed to, but there
are a few that can be moved or deleted. If you go into the Apps folder you will see CORE.
The entire CORE directory is stand alone and can be either deleted (if not wanted) or moved
to a SD card for use. Inside Persistent Copy>Cabfiles you will find any Cabfiles that are
required by the OS for cold boot recovery. The first one is the Cabfile for the Wavelink
Enabler. If this is not a program you are currently using you can right-click, delete and then
cold boot to remove it. This can always be reinstalled later.

What new features do I get from Intermec with PPC 2003?
Currently Available:
Wavelink Avalanche Enabler:
“Wavelink Avalanche is proven software for centralized management of mobile devices. It
performs rapid, hands-off updates of wireless devices located anywhere in the enterprise.
Remotely and seamlessly, Avalanche revises configurations, synchronizes software and
updates firmware and drivers. Best of all, it cuts your costs—in time, money and
morale—by reducing the burden on your IT resources and eliminating labor-intensive
management of mobile equipment. With Wavelink, you’ll have better tools, and more
time, to achieve your wireless possibilities.” The Avalanche Enabler has now been added
into the Intermec Value Add and will automatically load on every device running this build
and higher. http://www.wavelink.com/wavelink/avalanche/
Security Supplicant:
The Intermec Security Supplicant has now been added to the build and will automatically
install on every device. This includes support for LEAP, PEAP, WPA, CCX, etc.
Data Collection / Intermec Settings:
The latest version’s of Data Collection have been added into this OS. Now instead of the
old Data Collection Icon, you will see Intermec Settings. Inside Intermec Settings you
can now configure Scanner and Symbologies, the 802.11 Radio, UDP Plus, and basic
700 Settings.
• Scanner symbologies are now saved in the registry and can be saved via regflush.
• Improved decode speed and performance.
6
•
The Imager can now be configured via a gui, instead of an application or imager
demo.
802.11:
The drivers have now been updated to the new PRISM driver’s from Intel. Please look
under the 802.11 section of this document for more detailed information.
Available January 2, 2004:
Unbundled IVA Components
The operating system and IVA components are now unbundled. This allows for smaller,
individual .CAB file updates and patches to be enabled for customer fixes.
- The IVA will be able to be updated on a component basis. There will no longer
be a need for an entire IVA update.
Updated BT Components
Currently included in the SR cabfile patches that can be downloaded from the IDL Beta
Zone.
Integrated Support of the Mag Stripe Reader (MSR)
Fully integrated into the ICCU (Intermec Settings)
802.11b Software Enhancements
Will provide a significant reduction in the amount of time required for a 700 to hard roam
between APs. Multiple SSIDs will be supported. It also gives the ability to support devices
with different security capabilities to use the same RF network.
SF51 Support
Intermec’s newest, and the world’s most innovative, Bluetooth enabled scanner.
Device Management and Remote OS Upgrade
You will now be able to remotely manage the following device settings: MSR, Bluetooth,
Power Management Settings, and Display Settings
7
802.11

My 802.11 code worked on PPC 2002 but not on PPC 2003, why?
With every version of the PPC 2002 operating system but that latest (1.31.32) the drivers
being used by the 802.11 radio were older ones from Intel. With the newer versions of PPC
2003 and the latest version of PPC 2002 these drivers have now been upgraded to Intel
PRISM drivers. With this upgrade came a few changes in how the radio is programmed.
General 802.11 Radio Programming Differences:
1. If the application directly manipulates the radio, the driver name has changed.
From: NETWLAN.DLL
To: PRISM.DLL.
2. If an application modifies any registry settings for the radio driver. (i.e. EnableDHCP,
IpAddress), the location of the root driver specific registry keys have moved.
From: HKLM\CommNETWLAN1
To: HKLM\Comm\PRISMNDS1.
3. The Display Name in the Settings->Connections->Advanced(Tab)->Network Card
has changed.
From: “802.11b Wireless LAN (750-2011b)”
To: “802.11b Wireless LAN (730-802CF13)”.
4. The new Prism drivers has a registry key for APDensity that has 3 values
"HKLM\Comm\PRISMNDS1\Parms\APDensity" 1=Sparse, 2=Normal, 3=Dense.
WM 2003 IVA v2.28 vs. newer
1. If you are using NDISUIO.DLL, the device prefix for this driver has changed from
“UIO1:” to “ZIO1:”. This device name is normally captured in the macro
NDISUIO_DEVICE_NAME in nuiouser.h. This macro will no longer be valid and you
will need to redefine the macro or use the new device prefix explicitly.
2. 80211pm.dll available for programming PPC 2003 Security Settings. Please look
inside the SDK for more information.

How am I able to program the 802.1x security supplicant?
The ability to program the security supplicant was introduced with PPC 2003. This is handled
via the 80211pm.dll. More information can be found within the SDK. The profile differences
between PPC 2002 and PPC 2003 are noted below.
Profile Changes for WM 2003 with the Prism Radio Drivers
1. The 802.11 Profiles have changed.
a. There are now only 4 static profiles available
b. The 80211api.dll ConfigureProfile() function only accepts
“Profile_1”, “Profile_2”, “Profile_4”, “Profile_4”. (Previously the function would accept
user defined names for profiles.)
c. Profiles will have to be recreated.
2. Customers will be able to take advantage of the new 80211pm API’s for
managing their profiles programmatically.
Security Supplicant Differences:
1. If you are using the security supplicant for PPC2002 you will need the
700CSecure200RC5.CAB file.
 I recently upgraded to PPC 2003 and now my 802.11 radio doesn’t work?
With the newer versions of PPC 2003 (those after July 2004) the new Intel PRISM drivers are
required in order to have the radio and security supplicant function correctly. Everything needed
8
to complete the upgrade of these drivers is found in the general operating system upgrade zip
file. The latest file for these drivers is: upg2011b_200x_C.CAB
9
WWAN
 How do I program for the GPRS or CDMA radio in my unit?
The WWAN radios can be programmed via the AT commands specific to those radios. Each
different company and radio model will have their own commands. This means that if you are
writing an application to work across multiple radios you will have to see multiple sets of
commands. These commands must come from the radio manufacturer. It is important to note
that the WWAN radios can be the most difficult to program for as you have multiple coverage and
programming scenarios to work around. If you do not have an in-depth background in coms and
WWAN radios, it is recommended that you look into the WWAN Toolkit.
 What is the WWAN Toolkit?
The WWAN Toolkit is an Intermec Toolkit that was written by our offices overseas. It is written
using the base AT commands of each of the radios that we support. The advantage to the
toolkit, is that these AT commands are written into easy to use functions that are not radio
specific. For example: WWANRadioPower() is the function that will turn the power onto any of
our WWAN radios. There is not a separate function for each radio. This drastically cuts down on
the amount of code needing to be written as well as the learning curve required to learn each
radios AT commands. The WWAN Toolkit is also fully backwards compatible, so not only will
our new radios be supported but our old ones going back to the 700 Mono Series will be as well.
This is a for purchase toolkit that is in the price guide and has an applicable discount code. A full
evaluation version of the WWAN Toolkit can be downloaded for free in the Software Showcase of
the Developer’s Library.
 Why won’t the example application run on my handheld?
The WWAN Toolkit needs dlls to run the application API calls that it makes to the radio. In order
to save space in the operating system, these dlls do not come pre loaded onto the device. Aside
from the .exe of the application you want to run you will need to install the toolkit dll. This can
either be done by directly loading the wwantk.dll into the \windows directory on your handheld via
active sync, or by loading the WWANToolkit4_.ARM.CAB (based on toolkit version) onto your
device and executing. If you are loading a .net application you will also need the .net wrapper.
You will need to place Intermec.Communications.WWAN.dll in the same place as your
application. Now go and click on your .exe and you should not have any problems.
 This is my first WWAN application with the toolkit, how do I get started?
The first step should be to go into C:Program Files:Intermec:WWAN Toolkit and take a look at the
enclosed sample applications. You will find that they cover evb, ec++, vb.net, c#, and java. The
general application framework for both radios is similar, but GPRS has a few steps that CDMA
does not. Here is a framework application, as well as the base calls and page numbers for more
information from the manual.
Turn Power On to the Built In Radio
or
(MONO ONLY)
BOOL WWANRadioPower()
BOOL G18PowerOn()
(page 7)
(page 8)
Setup WWAN Toolkit
BOOL SetupToolKit()
(page 9)
Setup Modem Event Reporting
BOOL SetModemEventReporting()
(page 10)
Create either a RAS or Connection Manager Entry on Pocket PC DWORD CreateRasEntry ()
or BOOL CreateDiallingLocation()
Add a RAS or Connection Manager Entry you created above
Check/Enter SIM Pin (GPRS radios ONLY)
Get Signal Strength
Attach to a GPRS Network (GPRS ONLY)
Connect To Network either RAS or Connection Manager
(page 27 or 35 )
BOOL GSMTOOLAPI AddEntryToConnMgr()
or BOOL SetDialingLocation()
(page 28 or 36)
PIN_CODES CheckSimPin()
(page 13)
BOOL EnterSimPin ()
(page 13)
BOOL SignalStrength()
(page 15)
BOOL SetGPRSAttach()
(page 16)
BOOL DoDialUpConnect ()
10
or BOOL DoRASConnect()
(pages 32-33)
YOU ARE NOW TALKING TO THE NETWORK AND CAN WORK WITH YOUR APP
Disconnect From Network either RAS or Connection Manger
Remove a RAS Entry from Connection Manager
Delete a RAS or Conneciton Manager Entry on Pocket PC
Shutdown WWAN Toolkit
Turn Power OFF to the Built in Radio
BOOLDoDialUpHangup()
or BOOL DoRASHangup()
(pages 33-34)
BOOL RemoveEntryFromConnMgr()
(page 29)
BOOL DeleteRasEntry()
or BOOL DeleteDiallingLocation()
(page 28 or 35)
BOOL SetupToolKit()
(page 9)
BOOL WWANRadioPowerOff()
(page 7)
or (MONO ONLY) BOOL G18PowerOff() (Page 8)
 My toolkit application worked with PPC 2002 and now won’t with 2003?
With PPC 2003 Microsoft changed the drop down boxes in connection manager from Internet
Settings to My ISP and Work to My Work Network. The piece in your application that is effected
with this is included in the short sample below.
connParams.UseConnMgr = true;
connParams.ConnMgrDestination = _T("Internet Settings");
connParams.SetAlwaysDialEntry = true;
 What are my connection parameters for the WWAN radios profile?
GPRS:
connParams.Flags = 0;
connParams.CountryCode = 0;
connParams.AreaCode = _T("");
connParams.PhoneNumber = _T("*99***1#");
connParams.ExtraCmds = _T("");
connParams.UserName = _T("");
connParams.Password = _T("");
connParams.Domain = _T("");
// *99***1# is the default GPRS Phone Number
// use SetGprsApn() method instead below for APN
// usually not given by provider, leave blank then
// usually not given by provider, leave blank then
// Typically use DHCP, so we don't need to specify any IP, DNS or WINS addresses.
connParams.IpAddr = _T("");
connParams.DnsAddr = _T("");
connParams.DnsAltAddr = _T("");
connParams.WinsAddr = _T("");
connParams.WinsAltAddr = _T("");
// We'll set our GPRS APN using the toolkit command.
// You could instead use +CGDCONT=1,"IP","your.apn.here" in ExtraCmds,
// but beware of 39 limit on that command string
connParams.GprsApn = _T("");
// just the APN, not the whole +CGDCONT command string!!!
// the above is usually left empty on most US networks. Overseas uses an APN all the time.
CDMA:
Same as above except the below is changed and there is typically always a username and password.
connParams.PhoneNumber = _T("#777");
//
#777 is the default CDMA Phone Number
 Why is my application not creating my connection my manager entry?
If you are basing your application off of one of the toolkit sample applications there could be a
reason for this both on CDMA and GPRS. All of our samples are built for WWAN in general and
to work across both radios. If you are writing a GPRS program and the samples are built for this
com port:
connParams.ModemName = _T("WANA on COM4: (No modem reset)");
This is by default not loaded onto the devices. You will need the MC45 All Modems Cabfile which
can be found in Developer’s Support>700 Color Support>Downloads. This cab must be loaded
11
for applications using that com port to work. On the other side if you are using CDMA this is not a
CDMA modem possibility. In your code remove the part in bold above and recompile.
Bluetooth

Is Bluetooth different from PPC 2002 to 2003?
Pocket PC 2002 uses the Socket Stack and PPC 2003 uses the Microsoft Stack and it’s
APIs.If you are currently using Bluetooth under PPC2002, then you need to know if you are
using the underlying stack or just opening the correct com port. If you let the wizard setup the
com port and then save off a favorite and flush the registry you should have no changes. If
your application does anything with the Drakkar API, then you will need to make changes. It
is recommended to look at the new Wireless Printing SDK and the Beta Zone of the
Developer’s Library. If you use the wizard there is a new wizard that can be used to discover
and set up the com port. You can then save off the registry and everything should work
without a hitch. If you use the lineprinter activeX control to open the port and print, you will
need the updated lineptr.dll which can be found in the latest 700 color toolkit.

What Bluetooth profiles are supported with PPC 2003?
Generic Access Profile, Service Discovery Profile, and Serial Port Profile
Scanning

Is scanning different from PPC 2002 to 2003?
Are you using the scanner in wedge mode or does your application control the scanner? If
you are using wedge mode, then no changes should be made. If you control the scanner and
are using an ActiveX control, you must upgrade to the latest itcaxbarcodereader.dll. If you are
using .Net you will need to upgrade to the latest itcscan.dll and itc50.dll. Both of these
updated dlls can be found inside the latest 700 color toolkit in the Developer’s Library.

What are my different options for scanning with a 700 Series Mobile Computer?
You may use two approaches to collecting scanned data (1) the virtual wedge or (2) the Com
interfaces.
The virtual wedge requires no programming on your part to collect the data. Rather the
scanned data is wedged into whatever input field has the keyboard focus. For example
PWord, PExcel or an edit box in your app.
The Com interfaces, which may be accessed directly or accessed by ITCAXBarcodereader,
provide the application programmer many options for collecting, editing and routing of
scanned data. However to use the Com interfaces, the application must post a Read request
to obtain the scanned data. This supports multiple channels, that may selectively read only
when the application wants data on a particular channel. A Read request may be
incorporated into the CompletRead processing from a previous read. Then after the first
Read request is posted, during application initialization for example, the Read requests are
"automatically" posted when data is scanned . This approach requires no pushbutton action
by the operator. The Read requests may be programmed with a timeout defined or the Read
request may be programmed to wait forever for scanned data. Note that the Read request is
a blocking call. Thus the application may need to consider a separate thread for the Read
requests, to prevent hanging up the application.
12