Download iLaunch User`s Guide

User's Guide
iLaunch
Intermec Technologies Corporation
Worldwide Headquarters
6001 36th Ave.W.
Everett, WA 98203
U.S.A.
Cedar Rapids Technical Communications
550 Second Street SE
Cedar Rapids, IA 52401
U.S.A.
www.intermec.com
The information contained herein is provided solely for the purpose of allowing customers to operate and service Intermec-manufactured equipment and is not to be released, reproduced, or used for any other purpose
without written permission of Intermec Technologies Corporation.
Information and specifications contained in this document are subject to change without prior notice and do
not represent a commitment on the part of Intermec Technologies Corporation.
© 2003-2006 by Intermec Technologies Corporation. All rights reserved.
The word Intermec, the Intermec logo, Norand, ArciTech, Beverage Routebook, CrossBar, dcBrowser, Duratherm, EasyADC, EasyCoder, EasySet, Fingerprint, i-gistics, INCA (under license), Intellitag, Intellitag Gen2,
JANUS, LabelShop, MobileLAN, Picolink, Ready-to-Work, RoutePower, Sabre, ScanPlus, ShopScan, Smart
Mobile Computing, TE 2000, Trakker Antares, and Vista Powered are either trademarks or registered trademarks of Intermec Technologies Corporation.
There are U.S. and foreign patents as well as U.S. and foreign patent applications pending.
Microsoft, Windows, and the Windows logo are registered trademarks of Microsoft Corporation in the United
States and/or other countries.
Bluetooth is a trademark of Bluetooth SIG, Inc., U.S.A.
ii
iLaunch User’s Guide
Document Change Record
This page records changes to this document. The document was originally
released as Revision A.
iLaunch User’s Guide
Revision
Letter
Date
Description of Change
B
02/2004
Added information that pertains to the CK30 Handheld
Computer.
C
01/2006
Updated for software version 1.15, updated CK30
instructions based on changes to its System Main Menu.
Added information for CK60, CN2, CN30 terminals.
D
04/2006
Updated for software version 1.16, updated to correct
two bugs.
E
05/2006
Updated for software version 1.17, updated to correct one
bug.
F
10/2006
Updated for software version 1.18, Removed references to
Pocket PC 2002 and 700 Monochrome terminals. Added
information for CN3 and CV30 terminals.
G
11/2006
Updated for software version 1.19 with two corrections.
iii
iv
iLaunch User’s Guide
Contents
Contents
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Global Services and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Who Should Read This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
iLaunch Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
iLaunch Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Requirements for Running iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
About the INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reserved INI File Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[Caption] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[exe] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[Bitmaps] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[password] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[ApplicationKeys] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[Disabled if no signal]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[EnforceSingleAppInstance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[parameters] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[Auto start] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
3
3
3
4
4
5
6
6
6
6
Installing iLaunch onto the Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing the CAB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Copying the CAB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Installing iLaunch onto the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Running iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Uninstalling iLaunch from the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Uninstalling iLaunch from the Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
TE 2000 Version of iLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Securing the System on a Cold Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Evaluation Version of iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
iLaunch Limitations and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
iLaunch User’s Guide
v
Contents
Contacting Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Application Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.19) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.18) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.17) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.09) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.05B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.05A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.01D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.01C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.01B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version (1.01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
16
16
16
16
17
17
17
18
18
18
18
19
19
19
iLaunch User’s Guide
Before You Begin
Before You Begin
This section provides you with safety information, technical support information, and sources for additional product information.
Safety Information
This section explains how to identify and understand notes that are in this
document.
Note: Notes either provide extra information about a topic or contain special instructions for handling a particular condition or set of circumstances.
Global Services and Support
Warranty Information
To understand the warranty for your Intermec product, visit the Intermec
web site at www.intermec.com and click Service & Support. The Intermec
Global Sales & Service page appears. From the Service & Support menu,
move your pointer over Support, and then click Warranty.
Disclaimer of warranties: The sample code included in this document is
presented for reference only. The code does not necessarily represent complete, tested programs. The code is provided “as is with all faults.” All warranties are expressly disclaimed, including the implied warranties of
merchantability and fitness for a particular purpose.
Web Support
Visit the Intermec web site at www.intermec.com to download our current
manuals (in PDF). To order printed versions of the Intermec manuals, contact your local Intermec representative or distributor.
Visit the Intermec technical knowledge base (Knowledge Central) at
intermec.custhelp.com to review technical information or to request
technical support for your Intermec product.
Telephone Support
These services are available from Intermec Technologies Corporation.
iLaunch User’s Guide
In the U.S.A. and
Canada, call 1-800755-5505 and choose
this option
Service
Description
Order Intermec
products
• Place an order.
• Ask about an existing order.
1 and then choose 2
Order Intermec media
Order printer labels and
ribbons.
1 and then choose 1
vii
Before You Begin
Service
Description
In the U.S.A. and
Canada, call 1-800755-5505 and choose
this option
Order spare parts
Order spare parts
1 or 2 and then choose 4
Technical Support
Talk to technical support about
your Intermec product.
2 and then choose 2
Service
• Get a return authorization
number for authorized service center repair.
• Request an on-site repair
technician.
2 and then choose 1
Service contracts
• Ask about an existing contract.
• Renew a contract.
• Inquire about repair billing
or other service invoicing
questions.
1 or 2 and then choose 3
Outside the U.S.A. and Canada, contact your local Intermec representative.
To search for your local representative, from the Intermec web site, click
Contact.
Who Should Read This Manual
This manual is written for the person who is responsible for installing, configuring, and maintaining the iLaunch application.
This document provides you with information about the features of the
iLaunch application, and how to install, configure, operate, maintain, and
troubleshoot it.
Before you work with the iLaunch application, you should be familiar with
your network and general networking terms, such as IP address.
Related Documents
This contains a list of related Intermec documents and their part numbers.
viii
Document Title
Part Number
700 Color Series Mobile Computer Quick Start Guide
962-054-053
700 Color Series Mobile Computer User’s Manual
961-054-031
CK30 Handheld Computer User’s Manual
073528
CK31 Handheld Computer User’s Manual
075207
CK60 Handheld Computer Quick Start Guide
962-054-115
CK60 Handheld Computer with Windows CE User’s Manual
961-054-037
iLaunch User’s Guide
Before You Begin
Document Title
Part Number
CK60 Handheld Computer with Windows Mobile User’s Manual
935-000-001
CN2A Mobile Computer User’s Manual
075464
CN2B Mobile Computer Quick Start Guide
930-103-001
CN2B Mobile Computer User’s Manual
935-001-002
CN3 Mobile Computer Quick Start Guide
930-151-001
CN3 Mobile Computer User’s Manual
935-003-001
CN30 Mobile Computer User’s Manual
961-054-039
CV30 Mobile Computer Quick Start Guide
930-165-002
CV30 Mobile Computer User’s Manual
935-005-001
CV60 Vehicle Mount Computer User’s Guide
961-054-033
Intermec Application Server User’s Guide
072242
TE 2000 Terminal Emulation Programmer’s Guide
977-055-008
The Intermec web site at www.intermec.com contains our documents (as
PDF files) that you can download for free.
To download documents
1 Visit the Intermec web site at www.intermec.com.
2 Click Service & Support > Manuals.
3 In the Select a Product field, choose the product whose documentation
you want to download.
To order printed versions of the Intermec manuals, contact your local
Intermec representative or distributor.
iLaunch User’s Guide
ix
Before You Begin
x
iLaunch User’s Guide
iLaunch Documentation
The goal of the iLaunch application is to launch other applications without
having to work in the standard Windows Mobile or Windows CE interface.
This is beneficial when you have more than one application that a user may
need to access, but the users need to keep from accessing the entire operating system.
iLaunch attempts to provide lock-down functionality but no application
can ever be completely locked-down on a Windows CE-based device. Windows CE platforms are multi-tasking environments where any number of
applications can be active simultaneously. In addition, Windows CE provides numerous services and utilities that launch and remain active when a
warm-boot or cold-boot is performed. These services and utilities may, at
any time, use pop-up menus, or windows that force their way on top of any
active application.
For example, when you Microsoft’s Connection Manager application, the
Network Status pop-up messages may display at any time and are beyond
the scope of iLaunch to control these messages.
iLaunch Details
iLaunch is an application for 700 Color, CK30, CK31, CK60, CN2A,
CN2B, CN3, CN30, CV30, and CV60 terminals that launch other applications via a configurable set of buttons. The label on each button and the
application the button launches is configurable via an INI file. Up to ten
programs can appear in the terminal.
In addition to providing a common interface for users to access the various
applications made available to them, iLaunch also locks down all applications that start while iLaunch is running. If Pocket Internet Explorer (PIE)
is one of the programs in the INI file, when the user runs that program, PIE
comes up and looks as it normally does but the user cannot bring up the
Start menu when tapping in the upper-left corner of the screen. When the
user taps the X in the upper-right corner, PIE is minimized and the user is
back at the iLaunch screen.
A “Locked-Down” application is an application that prevents the user from
leaving the application or from accessing the normal Navigation bar, Command bar, and Start Menu in PIE. Locked-down applications are extremely
important to prevent end users from getting “lost” in other parts of the system, in preventing users from changing system settings, and to ensure that
users are as productive as possible.
iLaunch User’s Guide
1
Requirements for Running iLaunch
• iLaunch runs on Intermec 730, 740, 741, 750, 751, 760, 761, CK30,
CK31, CK60, CN2A, CN2B, CN3, CN30, CV30, CV60 terminals.
• A nonvolatile form of storage must be available. This can include Compact Flash (CF) storage cards, SecureDigital (SD) storage cards, Flash file
storage, mini-SD, and disk on chip (DOC).
• iLaunch requires about 350 Kb of free storage space and about 350 Kb
of execution memory space.
About the INI File
The INI file associated with iLaunch controls many of the features of
iLaunch. The text that is placed on the buttons, the applications that each
button launches, a password to exit, the application key mappings, and a
custom bitmap to display are all controlled. The INI file can contain semicolons to act as comments in the INI files. You must save the INI file as an
ASCII file, if you edit the INI file be sure to save it as a standard ASCII file,
not as a Unicode file. Place the INI file in the same folder as the
SHELL.EXE or ILAUNCH.EXE application, which is found in the
“\iLaunch” or “\Launcher” subdirectory after the CAB file is extracted. Section and key names in the INI file are case-sensitive.
Reserved INI File Values
You can use the “CURRENTCARD” literal instead of an explicit path in
the INI file to indicate that the iLaunch application should use its internal
search path to determine which storage options are available and replace
CURRENTCARD with the path to that storage option. This allows the
use of the same INI file on multiple devices with different storage options.
The order of preference for non-volatile storage is the following:
• sdmmc disk
• Sd Card
• storage card
• flash file store
• CK_FFS
• DiskOnChip
• Program Files
For example if Button1 of the [exe] section contains:
\CURRENTCARD\testapp\app1.exe
when iLaunch encounters the CURRENTCARD tag, it finds the first
available directory from the search path and replaces CURRENTCARD
with that path. On a 700 Color terminal with a Secure Digital card
2
iLaunch User’s Guide
installed, the first path found would be “\SDMMC Disk,” thus Button1 of
the [exe] section points to “\SDMMC Disk\testapp\app1.exe.”
Note: Although CURRENTCARD is available for use, it is best when possible, to explicitly specify the path and file name to prevent issues that
might occur if the storage options on the device change.
[Caption]
The [Caption] section contains the text that is displayed on each button
when the iLaunch starts up. You can specify up to five buttons on CK30
terminals and up to ten on all other terminals. If text is not specified for a
button, the button does not display in iLaunch. If Button1 is the only button with a caption, then the application associated with that button is automatically launched immediately after iLaunch starts. See “[Auto start]” on
page 6 for more details.
Captions must be specified in sequential order. For example, if you only
have to display two buttons, you must use buttons 1 and 2. To display five
buttons, use buttons 1-5 under the caption section.
To use this section, add this line: ButtonX=text where “X” is the button
on the display to modify and “text” is what appears on the button. “1–10”
are the only valid buttons
[exe]
The [exe] section associates each button with a particular application. You
must specify the full path and file name. You can launch programs other
than EXEs, such as Visual Basic applications, WAV files, MP3 files, Word
documents, and other files that have a file association in the system. See
“[Auto start]” on page 6 for more details.
If only one application is in the INI file to launch from the menu, the
application specified after Button1 is automatically launched each time
iLaunch starts.
To use this section, add a line in the form:
ButtonX=path\app.ext
where “X” is the button number on the display to launch the application
located at “path\app.ext.” “1–10” are the only valid buttons. Use the full
path to the application, relative paths are not valid.
[Bitmaps]
The [Bitmaps] section points to a specific bitmap that is displayed at the
top of the iLaunch menu. You must include the full path and file name of
the bitmap in this section. If no bitmap is required, then the field is left
blank. Only bitmaps are displayed. The bitmap should be 280 x 80 in 16
colors for the CV60 terminal and 140 x 40 in 16 colors for all other terminals. The size does not have to be exact, it always centers smaller images and
larger images are automatically cropped.
iLaunch User’s Guide
3
To use this section, add a line in the form:
TopLogo=path\file.bmp
where “path” is the full path to the file and “file.bmp” is the file to display.
CK30 terminals cannot display the bitmap due to screen size limitations.
[password]
This contains the password required to exit the application. Leaving this
section blank or leaving the value after the key name blank results in no
required password to exit. The maximum size of the password allowed is six
characters, entering a password longer than six characters results in truncating the password after the sixth character. All alphanumeric values are valid
in the password but make sure a qualified user can enter the password
through the keypad or SIP keyboard available on the terminal.
Note: The SIP keyboard is not available on CK30 terminals.
To use this section, add a line in the form:
pwd=paswrd
where “paswrd” is the password required to exit the iLaunch application.
Note: When the iLaunch application initially starts up, the password is
read, encrypted, written back to the INI file in the cpwd key, then the pwd
key is deleted to prevent a user from getting the password from the INI file.
This does not change the password required to exit iLaunch. To change the
password, delete the cpwd setting and add a new pwd setting with the
desired password.
[ApplicationKeys]
Note: Application keys are only available on Windows Mobile terminals.
Beginning with the CN3 and CV30 terminals, the application keys were
removed from their respective keypads. The iLaunch application, when
installed on either the CN3 or the CV30, automatically sets up the [Windows] key as an application key for these terminals.
This parameter allows the INI file to map which applications to launch via
the application keys on the physical keypad. In early versions of iLaunch,
the application keys were blocked completely or in the case of the TE 2000
version were mapped to specific applications. If no ApplicationKeys are
specified, the non-TE 2000 version sets all application keys to launch
iLaunch. In the TE 2000 version, the non-TE 2000 version sets Application Key 1 as TE 2000, Application Key 2 as iBrowse, Application Key 3
and Application Key 4 as iLaunch.
4
iLaunch User’s Guide
Note: If the default mappings are changed, it is up to the INI file to ensure
any overwritten default is accessible in other ways if needed, including
iLaunch. Always map at least one Application key to iLaunch or the user
cannot get back to iLaunch to launch another application.
To use this section, add a line in the form:
AppKeyXExe=[ButtonY | LAUNCHER | path\app.exe]
where “X” in “AppKeyXExe” is the number of the application key on the
physical keypad to reassign.
You can choose one of three parameters for this application key. “ButtonY”
indicates to launch the application associated with ButtonY from the [exe]
section. “LAUNCHER” is a reserved word that causes the associated application key to bring up iLaunch. Use “Path\app.ext” to launch an application not assigned to an iLaunch Screen button. “1–4” are the only valid
AppKey buttons that can be remapped.
• Application keys on the 700 Color, CN2B are mapped to Gold [.] for
Application Key 1, Gold [4] for Application Key 2, Gold [5] for Application Key 3, and Gold [6] for Application Key 4.
• Once iLaunch is installed on CN3, CV30 terminals running Windows
Mobile 5.0, if the current keypad has a [Windows] key, it is remapped
to Application Key 1.
• Application keys on CK60, CN30 terminals running Windows Mobile
5.0 are mapped to Gold [Windows] for Application Key 1, Gold [smiley] for Application Key 2, Gold [frown] for Application Key 3, and
Gold [ok] for Application Key 4.
Application Key 1
Application Key 2
Application Key 4
Application Key 3
These soft keys are at the top of the keypad on the CK60 terminal.
[Disabled if no signal]
This disables specific buttons if no signal is available from the WLAN
radio. When the terminal is without signal from the WLAN radio, the buttons specified are grayed out and the user does not get to start those
options. When the terminal regains signal to the WLAN radio, the buttons
specified are enabled. This prevents users from starting an application that
requires a network connection when no network connection is present.
To use this section, add a line in the form:
ButtonX=true | false
where “X” is the button number on the display that is disabled based on
signal. Valid values are TRUE and FALSE (default).
iLaunch User’s Guide
5
[EnforceSingleAppInstance]
This prevents an application from starting up multiple instances of itself.
Most Windows Mobile applications are written to allow just one instance
of the application to start. Future attempts to start the application result in
bringing the original instance into focus. However, under Windows CE
operating systems, selecting to start an application multiple times starts
multiple instances.
To use this section, add a line in the form:
ButtonX=true | false
where “X” is the button number on the display on which the single instance
is enforced. Valid values are TRUE and FALSE (default).
[parameters]
This specifies optional parameters that may be useful when launching an
application. For example if the /f parameter can start APP1.EXE to run in
full screen mode, then the /f parameter would be specified here.
To use this section, add a line in the form:
ButtonX=/parm1 /parm2
where “X” is the button number on the display to which the parameters are
applied. Valid values are dependant on the application launched with these
parameters. The default value is no parameters.
[Auto start]
This enables or disables the ability to autostart an application when the
iLaunch application starts up. This auto start capability is only available
when a single application is specified in the [captions] and [exe] sections
using the button1 keyname.
To use this section, add a line in the form:
Enabled=true | false
Where TRUE indicates the iLaunch application automatically starts the
application when iLaunch starts up. FALSE indicates not to start any application. The default is TRUE.
Sample INI File
; specify the names that will be displayed for each application that can be
launched
[Caption]
Button1=Notes
Button2=Calculator
Button3=Internet Explorer
; specify the full path and filename to the applications to be launched
[exe]
Button1=\windows\notes.exe
6
iLaunch User’s Guide
Button2=\windows\calc.exe
Button3=\windows\iexplore.exe
; specify the parameters to pass to each applications
[parameters]
Button3=www.intermec.com
; specify whether or not to disable a button when there is no WLAN signal
[Disabled if no signal]
Button1=false
Button3=true
; Only allow a single instance of the application or not
[EnforceSingleAppInstance]
Button2=true
;password to exit
[PassWord]
pwd=123456
; The bitmap to display above the buttons
[Bitmaps]
TopLogo=\windows\launcher\intermecblue.bmp
; Specify if a single application should start when iLaunch starts
[Auto start]
Enabled=true
; Remap the application keys to specific applications
[ApplicationKeys]
AppKey1Exe=Button3
AppKey2Exe=Button1
AppKey3Exe=LAUNCHER
AppKey4Exe=LAUNCHER
Installing iLaunch onto the Desktop
These instructions explain how to install the iLaunch application onto your
Intermec terminal and configure the terminal for maximum performance.
Note that these instructions are alternative to installing this application via
installation CD.
Related Documentation
For help with installing a storage media card, or a battery pack, or to learn
about booting the terminal, see its documentation. See “Related Documents” on page viii for part numbers.
Installing the CAB Files
Your license allows you to install a number of copies of the iLaunch application. Have the quantity on hand before you initiate the installation.
iLaunch User’s Guide
7
1 Enter the License Quantity (number) of licenses you had purchased for
this application, then click Continue.
2 Select Yes, I accept this agreement to accept the conditions of this
license agreement, then click Continue to load all of the available CAB
files and related information into the default “C:\Program Files\Intermec\iLaunch” folder on your desktop.
8
iLaunch User’s Guide
3 Select what files to install, then click Install to continue.
4 Click Finish to complete the installation.
5 Wait for the default “C:\Documents and Settings\All Users\Start
Menu\Programs\Intermec\iLaunch” folder to open. Double-click the
Explore iLaunch Folders shortcut to access the CAB files.
6 Open the applicable folder, then copy the appropriate CAB file.
iLaunch User’s Guide
9
Below is a table defining what CAB files apply to which operating system
on a given Intermec terminal. Contact your Intermec representative for
more information about any of these files.
Note: The TEiLaunch .CAB file is only available for 700 Color terminals
using the Windows Mobile operating system.
Windows Mobile 2003
700
Windows Mobile 5.0
Windows CE 5.0
iLaunch.cab
teiLaunch.CAB
CK30,
CK31
iLaunch30.CAB
CK60
iLaunch_WM2005.cab
CN2A
CN2B
Windows CE 4.2
iLaunch_WinCE.CAB
iLaunch.CAB
iLaunch.cab
CN3,
CN30,
CV30
CV60
iLaunch_WM2005.cab
iLaunch.CAB
Copying the CAB File
Note: When “NVStorage” is mentioned, it references the folder name of
the card you installed in the device. This is “SDMMC Disk” or “Storage
Card,” “SD Card,” “Flash File Store,” “CK_FFS,” or other nonvolatile
storage option.
Copy the applicable ILAUNCH.CAB file to the “\NVStorage\CabFiles”
folder on the device. Warm-boot the device to automatically install the file.
If the “CabFiles” folder is not already on the “NVStorage” it may be necessary to create a “CabFiles” folder and install the “2577” directory that
allows for automatic CAB file extraction from the appropriate tools CD.
Do not tap on the CAB file via File Explorer to extract the file. This deletes
the CAB file. Extracting the CAB file automatically on a reboot leaves the
CAB file on the terminal for future extractions in the event of a cold-boot.
The default INI file installed by the CAB file is a sample file. You need to
change this INI file to include your preferred applications to launch, password, and other settings as applicable.
To update the INI file, copy the default INI file from the terminal to your
desktop, either with Microsoft ActiveSync or by removing the storage card
from the terminal and putting it into a card reader. In either case, the INI
file is in the “NVStorage\ILaunch” or “NVStorage\Launcher” directory.
10
iLaunch User’s Guide
Installing iLaunch onto the Terminal
Refer to the terminal’s user guide or user manual for information on installing CAB files. See “Related Documents” on page viii for part numbers.
Running iLaunch
iLaunch automatically starts up on a warm- or cold-boot if the CAB file
was installed properly.
To start iLaunch after exiting it on Windows Mobile operating systems,
select Start > Intermec Launcher or select Start > Programs > the Intermec Launcher icon.
On Windows CE, double-tap the Intermec Launcher icon on the desktop
or select Start > Programs > iLaunch.
This screen now contains indicators for battery status and signal strength.
Also the serial number is displayed on this screen for all terminals except
the CK30 terminal.
Tap Status to view the status screen, which contains IP status, MAC
address of the WLAN radio, authentication type, and the serial number of
the terminal. Note the CV60, CN2B terminal application does not display
any battery status as it does not use a battery.
iLaunch User’s Guide
11
Tap Exit to go to the Exit screen, then enter your six-character password to
close the iLaunch application. Tap Keyboard for an onscreen keyboard or
Soft Input Panel (SIP) keyboard with which to enter your password.
For keypad navigation on CK30 terminals, because the CK30 has no touch
screen, the iLaunch application displays numbers next to each button to
navigate to the specified application. You can also use the Tab and Enter
keys to select any button. From the Status and Exit screens, press Esc to go
to the previous screen and press Enter to go to the next screen.
Windows Mobile terminals can use the application keys to switch between
applications. Devices with the Windows CE operating system do not have
this option. On the CV60 terminal, use the taskbar at the bottom of the
screen to move between applications without closing any. On terminals
with smaller screen sizes and the Windows CE operating system, use the
small icon in the lower right to pop-up a list of running applications and
switch between them.
General Caution:
Although the iLaunch application attempts to block a user from accessing other parts of the system, other applications launched from within
iLaunch could allow the user to access other parts of the system. One
known example of this would be Internet Explorer. If Internet Explorer
is left as an option for a user, a savvy user could access the file system
through Internet Explorer. To prevent this, examine all applications
launched from within iLaunch to determine what type of system security risk each would represent.
Error Messages
When a problem occurs trying to launch an application, the full text of the
error is displayed. On the CV60 terminal, the full text is not displayed,
instead its error number is displayed. See details of the specific error number at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/
wcesdk40/html/cerefsystemerrors-numericalorder.asp
12
iLaunch User’s Guide
Uninstalling iLaunch from the Terminal
No automatic uninstallation is available at this time. To uninstall iLaunch,
remove the following files:
\windows\start menu\Intermec launcher.lnk
\windows\startup\Intermec launcher.lnk
\windows\launcher\*.*
NVStorage\launcher\*.*
NVStorage\Cabfiles\launcher*.cab
Rename the file
Autorunold.dat autorun.dat
where NVStorage is the folder name of the card you have installed in the
device. This is usually “SDMMC Disk,” “SD Card,” or “Storage Card.”
Uninstalling iLaunch from the Desktop
1 From the desktop, access the “C:\Program Files\Intermec\iLaunch”
folder.
2 Double-click the Explore iLaunch Folders shortcut.
3 Double-click the UninstalliLaunch.exe executable.
4 Click Uninstall to remove the iLaunch files from your desktop.
5 Click Finish to complete the uninstallation of the iLaunch application.
iLaunch User’s Guide
13
TE 2000 Version of iLaunch
The Terminal Emulation (TE) 2000 version of the iLaunch application is
slightly modified from the regular version. The TE 2000 version comes
with an INI file that already points to the locked-down applications
iBrowse and TE 2000. The TE 2000 version also sets the application keys:
Application Key 1 starts TE 2000, Application Key 2 starts iBrowse, Application Keys 3 and 4 start iLaunch. You can add two other locked-down
applications to the MENU.INI file this version of iLaunch uses.
Securing the System on a Cold Boot
The Launcher CAB file include a utility called SYSSTART.EXE. The
SysStart utility, when added to the AUTORUN.DAT file, runs on startup
to prevent the user from accessing the system during startup and CAB file
extraction. SysStart is not added to the AUTORUN.DAT file. To use
SysStart, perform these steps:
Note: “NVStorage” refers to the type of nonvolatile storage in terminals.
1Copy the Launcher CAB file to the 700 Color Computer and extract it.
2 Rename “\NVStorage\2577\autorun.dat” to
“\NVStorage\2577\autorunOLD.dat”.
3 Copy “\NVStorage\launcher\autorunXX.dat” to “\NVStorage\2577”
where the XX is “CF” if your storage card is a CompactFlash card or
“SD” if your storage card is a Secure Digital card.
4 Rename the “\NVStorage\2577\autorunXX.dat” to
“\NVStorage\2577\autorun.dat”.
Caution: Although SysStart attempts to block users from other parts of
the system, other applications launched at system startup may force
themselves on top. This eliminates SysStart’s ability to lock down the
terminal. This situation is beyond SysStart’s capability to correct.
Evaluation Version of iLaunch
Evaluation versions of iLaunch are available. These versions allow some
restricted use. The iLaunch application performs normally with the exception that it occasionally brings up a reminder that the version of iLaunch
used is only an evaluation version. You have 60 days from the date you first
start using the evaluation version of iLaunch to either purchase a license or
quit using iLaunch. If you decide to purchase licenses for iLaunch, contact
your Intermec representative. A license is required for each device that runs
iLaunch. The part number to purchase a single license is 235-107-001.
14
iLaunch User’s Guide
iLaunch Limitations and Restrictions
• iLaunch does not save the registry to a storage device.
• iLaunch runs on Intermec 730, 740, 741, 750, 751, 760, 761, CK30,
CK31, CK60, CN2A, CN2B, CN3, CN30, CV30, CV60 terminals.
Known Issues
If owner information is set to display on startup, the owner information
shows up on top of the iLaunch application. To disable the owner information, tap Start > Settings, then tap Owner Information. Uncheck (or clear)
Show information when device is turned on.
Troubleshooting
No buttons show when iLaunch starts.
• Make sure a valid Menu.INI file is in the same directory where the
iLaunch files were installed. Look in the “\NVStorage\Launcher,”
“\NVStorage\Launcher,” or “\Program Files\Launcher“paths.
• Is iLaunch running on a supported terminal? The application only displays the menu if it is running on either of these terminals.
• The section names and labels in the INI file are case-sensitive. Make sure
that you are using the correct case.
After copying the CAB file to the “\CabFiles” folder on my storage card, iLaunch does
not automatically start.
• Warm-boot the 700 Color Computer again. Early versions of the 700
Color software did not properly warm-boot a device after installing a
CAB file.
• To automatically extract files in the “\CabFiles” folder, other supporting
files must be on the storage card. Contact Customer Support to ensure
your 700 Color Computer is properly set up to autoextract CAB files.
iLaunch User’s Guide
15
iLaunch reports no network connection even though the network settings are done
correctly
On Windows Mobile 5.0 terminals, if the terminal is connected to ActiveSync, the ActiveSync application disables all network connections as a security measure.
The screen doesn’t rotate when the button is pressed to rotate it.
The iLaunch application does not support screen rotation at this time.
Contacting Customer Support
When contacting Customer Support, provide the following information:
• Model number of the terminal.
• Version number of the operating system.
• Version number of the iLaunch software.
See “Global Services and Support” on page vii for information on contacting your Intermec representative.
Application Updates
Version (1.19)
Corrected:
• “Space Contrained” keyboard for the CV30 did not have the Windows
Key correctly mapped to function as an application key (application key
1).
• Installation for version 1.18 did not create a folder for the CN3 and
CV30 installation cabinet files.
Version (1.18)
Added:
• Support for CN3, CV30 Windows Mobile 2005 terminals
Version (1.17)
Fixed:
• Disabled hotkey access to the Phone Dialer program available on Intermec devices loaded with the Phone Edition operating system. Once
iLaunch disables the hotkey, the hotkey remains disabled when iLaunch
exits. You may enable the hotkey again by cold-booting the device.
16
iLaunch User’s Guide
Version (1.16)
Fixed:
• iLaunch locks up when started on devices not using 802.11 radios
• iLaunch for TE 2000 was not activating the application keys on 700
Color (730, 740, 741, 750, 751, 760, 761) terminals.
Version (1.15)
Added:
• Support for CK60, CN30 terminals running Windows Mobile 2005.
• Support for CK30, CK31, CK60, CN30, CN2A, CV60
• Support for showing battery level, signal strength, other system settings
• Encrypted password support
• Support for up to 10 buttons (all devices except CK30s)
• Checks to only enable buttons if radio is connected (set in INI file)
• Support for installing iLaunch on devices without a SD or CF card
• [parameters] of INI allows parameters when launching applications
• [Disabled if no signal] section of INI disables buttons if no signal
• [Auto start] section of INI allows for autostart of first menu item if there
is only one menu item
• [EnforceSingleAppInstance] section of INI allows for only one copy of
an application to run at a time
• Added a Keyboard button to the Exit dialog to allow the user to key in a
password (not available on the CK30)
Fixed:
• INI file was kept open after first read and so could not be updated while
iLaunch was running
• Error reporting, when iLaunch attempted to exec an application but the
application was not at the path specified it would report “iLaunch Error”
“operation completed successfully”
• Password longer than six characters was allowed in the INI and not truncated leaving users unable to exit
Version (1.09)
Fixes
• When launching another application, the command bar was partially
erased by iLaunch in some instances.
iLaunch User’s Guide
17
• Users could still get into the system - open clock, hold action, and taphold in clock area, menu comes up for clock/run can run any application
in the system.
• User could get out of system by pressing and holding the Windows key
• If one application was specified, Launcher did not behave as desired
• On Windows Mobile 2003, the bitmap at the top of the screen was not
displayed correctly.
Added:
• Applications other than EXEs can now launch, including file extensions
with associations in the system, such as specifying ABC.PSW to launch
Pocket Word with ABC as the current document. This also means that
Visual Basic applications can launch directly from iLaunch
• Error messages return text instead of just the error number
• Updated to run on Windows Mobile 2003
Version (1.07)
Fixed
• Windows Mobile 2003 was not rendering the blank area around the bitmap correctly (fixed to paint the area drawn around the bitmap white)
• Applications keys that were set to none or other literals in < > now get
remapped correctly
Added
• Application keys can set via INI file
Version (1.05B)
• Changed some code that allows iLaunch to disable the Start button
when another application has focus
Version (1.05A)
• Added code so that iLaunch tries to disable the Start menu for applications that are not locked down
• Fixed the battery status page so that the timer is destroyed appropriately.
• Added the SysStart application to the CAB file to help lock down the
user interface while CABs are extracted
• Added AUTORUN files to CAB files to ease the SysStart installation
Version (1.01D)
• Now prevents user from exiting if the user were at the main dialog when
Enter was tapped
18
iLaunch User’s Guide
Version (1.01C)
• Updated the code to set the application keys appropriately on 700 Color
Computers with alphanumeric keyboards
Version (1.01B)
• Fixed the Esc key to not allow the user to exit iLaunch
• Changed the version slightly to display TE 2000 before the version if it is
a TE 2000 build
• Updated the copyright to include 2003
Version (1.01)
• Created a separate evaluation version of the application to evaluate for 60
days - during the trial period, reminder messages pop up after iLaunch
launches three applications
• Added Copyright information
• Added code to “lock-down” the Exit dialog
• Added TE 2000-specific features, such as application keys are mapped
and enabled
• Added CURRENTCARD as a special modifier to the EXE path section.
If CURRENTCARD is added to the front of the path to an executable
in the [exe] section, the application replaces CURRENTCARD with the
path of the card from which the iLaunch is running. This uses the same
INI file on both CompactFlash and Secure Digital storage cards.
iLaunch User’s Guide
19
20
iLaunch User’s Guide
Worldwide Headquarters
6001 36th Avenue West
Everett, Washington 98203
U.S.A.
tel 425.348.2600
fax 425.355.9551
www.intermec.com
iLaunch User’s Guide
*961-055-016G*
P/N 961-055-016G