INTERMEC Communications Resource Kit V3.52

README.HTM

© 2005 - 2013 INTERMEC TECHNOLOGIES CORPORATION, ALL RIGHTS RESERVED

 

Contents

VERSION HISTORY

REQUIREMENTS

SUPPORTED DEVICES

KNOWN_ISSUES

 

VERSION HISTORY

Version #

Description

V3.52

  • Fixed an issue with Network Tools LoadNetworkDevice() function that was causing it to incorrectly return ITC_NETWORK_TOOLS_NOT_SUPPORTED when attempting to load the Ethernet adapter on the CV30.

V3.51

  • Added support for CV41 running Windows Embedded Standard 2009 (WES) operating system.

V3.50

  • Added Network Tools deliverable for new CV41 device.
  • Added new .NET Full Framework 2.0 deliverables for use on the CV61 device.  These assemblies provide access to the WLAN Information and WLAN Profile Management functionality on the device.
  • Expanded sample application offering to include new C# examples for the existing Network Tools, WLAN Information, and WLAN Profile Management .NET interfaces.

V3.40

  • Updated Network Tools functionality for WM6.5 devices.

V3.30

  • Added support for the CN4 Mobile Computer.
  • Fixed Network Tools functions EnableAutoFTP, DisableAutoFTP and GetAutoFTPBootState to work on the CK3 and CN3 Mobile Computers.
  • Fixed Network Tools functions LoadNetworkDevice and UnloadNetworkDevice to return an error when the nDevice argument is an invalid value and the bBypassDeviceCheck argument is true.

V3.20

  • Added new paths for ITC_CE50, and WM6.
  • Removed ITCSWinsock functions and all UDP Plus support for WM6 and higher devices.
  • Deprecated Windows Configuration Utility for WM6 devices.
  • Fixed Network Tools functions GetCurrentNetworkDevice, LoadNetworkDevice and UnloadNetworkDevice, which leaked a handle on 700 Series computers.
  • Fixed Network Tools in Visual Studio 2003. Add Reference failed with message "A reference to '<dll>' could not be added. This is not a .NET assembly."
  • Fixed Network Tools in a Visual Studio 2005 CF 1.0 application. The build failed with error "Metadata file '.dll' could not be opened -- 'Version 2.0 is not a compatible version’."

V3.10

  • Added Intermec Update to the installation kit.

V3.00

  • Separate IDL into individual Resource Kit installs.

V1.02

  • Network Tools method GetCurrentNetworkDevice, C++ and .NET, had been failing for some adapter types.

V1.01

  • Updates for WM 5.0.

V1.00

  • Initial release for the IDL.

 

RECOMMENDED DEVELOPMENT ENVIRONMENT

·         Windows XP (SP3) or Windows 7

·         For native C++ development, use Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008.  Development also requires the appropriate platform SDK.  For most devices this will be either the Microsoft Windows Mobile 5.0 Pocket PC SDK or the Microsoft Windows Mobile 6 Professional SDK, which can either be included with Visual Studio or downloaded from the Microsoft Download site.  For older devices, the appropriate SDK can be identified in the “DEVICE/PLATFORM RELATIONSHIP TABLE in the overall IDL readme.

·         For .NET development with C# or VB.NET, use Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008.

 

SUPPORTED DEVICES 

Device

Operating System

CK3

Windows Mobile 6.1

CK70

Windows Mobile 6.5

CK71

Windows Mobile 6.5

CN3

Windows Mobile 5.0, Windows Mobile 6.1

CN4

Windows Mobile 6.1

CN50

Windows Mobile 6.1, Windows Mobile 6.5

CN51

Windows Mobile 6.5

CN70

Windows Mobile 6.5

CS40

Windows Mobile 6.5

CV30

Windows Mobile 5.0

CV41

Windows CE 6.0, Windows Embedded Standard 2009 (WES)

CV61

Windows XP, Windows 7

 

KNOWN ISSUES

·         On some devices, the GetRadioIpAddress() function is incorrectly appending several extra characters after the NULL string terminator.  This can cause an overrun error if the buffer passed to the function is too small to handle the extra characters.  To prevent this issue, the buffer should be at least 64 characters in length. 

·         The supported field names for 802.11 profile management can vary by device and operating system.  For example, newer platforms may support different security options than older platforms.  The easiest way to determine whether a particular option is supported is to first check whether it is available in Intermec Settings on the device.  (Profile settings are generally found under the “Intermec Settings->Communications->802.11 Radio” tree.)

·         The C++ SetField() function requires administrative privileges when used on devices running Windows 7.  If an application cannot run with those privileges for security reasons, then either the .NET SetField() method or the Device Management Resource Kit should be used instead to adjust 802.11 profile settings. 

·         The GetTXPower() function is not currently supported on the CV61. 

·         The 80211api.dll library on the CV61 is compiled without UNICODE enabled.  As a result, any WLAN Information functions with a TCHAR parameter will expect that parameter to be a regular char data type (rather than a WCHAR data type).  For reference, this impacts the GetMac(), GetRadioIpAddress(), GetCurrentDriverName(), and GetBSSID() functions.

·         The GetRadioIpAddress() function is always returning ERR_QUERY_FAILED on the initial release of CV61.  To resolve this issue, upgrade the ITC Network Management package to version 1.00.00.0050 or later.   

·         The GetCurrentDrivername() function is always returning an empty string on the initial release of CV61.  To resolve this issue, upgrade the ITC Network Management package to version 1.00.00.0050 or later.

·         The isDHCPEnabled() function is always returning 0 (FALSE) on the CV61.  As an alternative, consider using the GetRadioIpAddress() function, which correctly indicates whether DHCP is enabled/disable when using an ITC Network Management package of version 1.00.00.0050 or later. 

·         The GetTXPower() function is not currently supported on the CV41 WES. 

·         The 80211api.dll library on the CV41 WES is compiled without UNICODE enabled.  As a result, any WLAN Information functions with a TCHAR parameter will expect that parameter to be a regular char data type (rather than a WCHAR data type).  For reference, this impacts the GetMac(), GetRadioIpAddress(), GetCurrentDriverName(), and GetBSSID() functions.

·         The GetRadioIpAddress() function is always returning ERR_QUERY_FAILED on the initial release of CV41 WES.  To resolve this issue, upgrade the ITC Network Management package to version 1.00.00.0050 or later.   

·         The GetCurrentDrivername() function is always returning an empty string on the initial release of CV41 WES.  To resolve this issue, upgrade the ITC Network Management package to version 1.00.00.0050 or later.

·         The isDHCPEnabled() function is always returning 0 (FALSE) on the CV41 WES.  As an alternative, consider using the GetRadioIpAddress() function, which correctly indicates whether DHCP is enabled/disable when using an ITC Network Management package of version 1.00.00.0050 or later.