User`s Guide

Transcription

User`s Guide

iLaunch
User’s
Guide
Intermec Technologies Corporation
Worldwide Headquarters
6001 36th Ave.W.
Everett, WA 98203
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-2008 by Intermec Technologies Corporation. All rights reserved.
The word Intermec, the Intermec logo, Norand, ArciTech, Beverage Routebook, CrossBar, dcBrowser, Duratherm,
EasyADC, EasyCoder, EasySet, Fingerprint, INCA (under license), i-gistics, Intellitag, Intellitag Gen2, JANUS,
LabelShop, MobileLAN, Picolink, Ready-to-Work, RoutePower, Sabre, ScanPlus, ShopScan, Smart Mobile
Computing, SmartSystems, 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 patents 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 version A.
Version
Number
Date
Description of Change
934-045-001
11/2008
Updated for software version 1.21 to include support
for CK3 and Windows Mobile 6.0. Converted to new
visual identity. Rewrote text in “About the .ini File.”
961-055-020
04/2007
Updated for software version 1.20 to include support
for CK32 and 700 series computers with Windows
Mobile 5.0 and for CV30 computers with Windows
CE .NET 5.0.
G
11/2006
Updated for software version 1.19 with two
corrections.
F
05/2006
Updated for software version 1.18, Removed
references to Pocket PC 2002 and 700 Monochrome
computers. Added information for CN3 and CV30
computers.
E
05/2006
Updated for software version 1.17, updated to
correct one bug.
D
04/2006
Updated for software version 1.16, updated to
correct two bugs.
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, and
CN30 computers.
B
02/2004
Added information that pertains to the CK30
Handheld Computer.
iii
iv
Contents
Contents
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Global Services and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Warranty Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Web Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Telephone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Who Should Read This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Introducing iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
iLaunch Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Requirements for Running iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Using a PC to Install iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Installing the .cab Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Copying the .cab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Installing iLaunch Without a PC Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
About the .ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Editing the .ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
[Caption] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
[exe] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
[Bitmaps] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
[password] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
[ApplicationKeys]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
[Disabled if no signal] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
[EnforceSingleAppInstance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
[parameters]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
[Auto start] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Saving and Transferring the .ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Sample .ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Reserved .ini File Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Starting iLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Uninstalling iLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Uninstalling iLaunch From the Mobile Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Uninstalling iLaunch From the PC Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Versions of iLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Evaluation Version of iLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
TE 2000 Version of iLaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Securing the System on a Cold Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
v
Contents
Troubleshooting iLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Application Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Version 1.21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Version 1.20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Version 1.19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Version 1.18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Version 1.17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Version 1.16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Version 1.15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Version 1.09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Version 1.07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Version 1.05B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Version 1.05A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Version 1.01D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Version 1.01C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Version 1.01B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Version 1.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
vi
Before You Begin
Before You Begin
This section provides you with safety information, technical support information,
and sources for additional product information.
Safety Information
Your safety is extremely important. Read and follow all warnings and cautions in
this document before handling and operating Intermec equipment. You can be
seriously injured, and equipment and data can be damaged if you do not follow the
safety warnings and cautions.
This section explains how to identify and understand dangers, warnings, cautions,
and notes that are in this document.
A caution alerts you to an operating procedure, practice, condition, or
statement that must be strictly observed to prevent equipment damage or
destruction, or corruption or loss of data.
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 Support > Returns and Repairs > 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
In the U.S.A. and Canada, call 1-800-755-5505.
Outside the U.S.A. and Canada, contact your local Intermec representative. To
search for your local representative, from the Intermec web site, click About Us >
Contact Us.
vii
Before You Begin
Service Location Support
For the most current listing of service locations, click Support >Returns and
Repairs > Repair Locations.
For technical support in South Korea, use the after service locations listed below:
AWOO Systems
102-1304 SK Ventium
522 Dangjung-dong
Gunpo-si, Gyeonggi-do Korea, South 435-776
Contact: Mr. Sinbum Kang
Telephone: +82-31-436-1191
Email: mjyunkang@awoo.co.kr
IN Information System PTD LTD
6th Floor
Daegu Venture Center Bldg 95
Shinchun 3 Dong
Donggu, Daegu City, Korea
E-mail: jmyou@idif.co.kr or korlim@gw.idif.co.kr
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.
viii
Introducing iLaunch
iLaunch allows users to launch applications without accessing the applications
through the standard Windows Mobile or Windows CE interface. Using iLaunch, a
system administrator can grant users access to more than one application while
denying access to other applications, or 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 launch Microsoft’s Connection Manager application, the
Network Status pop-up messages may display at any time and it is beyond the scope
of iLaunch to control these messages.
iLaunch Details
iLaunch is an application for 700 Color, CK3, CK30, CK31, CK32, CK61, CN2A,
CN2B, CN3, CN30, CV30, and CV60 computers. It handles launching up to ten
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.
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
are started while iLaunch is running. If Pocket Internet Explorer (PIE) is one of the
programs listed in the .ini file, it launches 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
returned to the iLaunch screen.
A “locked-down” application is an application that prevents the user from leaving
the application or prevents the user from accessing the normal Navigation bar,
Command bar, and Start Menu in PIE. Locked-down applications are extremely
important; they prevent end users from getting “lost” in other parts of the system,
prevent users from changing system settings, and help ensure that users are as
productive as possible.
9
Requirements for Running iLaunch
•
iLaunch runs only on Intermec 730, 740, 741, 750, 751, 760, 761, CK3, CK30,
CK31, CK32, CK60, CN2A, CN2B, CN3, CN30, CV30, and CV60 computers.
•
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.
•
iLaunch does not save the registry to a storage device.
Using a PC to Install iLaunch
You can enable your PC with the ability to install iLaunch on a mobile computer.
Use these instruction to install iLaunch using your Intermec computer and to
configure the computer to maximize its performance.
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.
To install .cab files
1 Enter the License Quantity (number) of licenses you have purchased for this
application, and then click Continue.
2 Select Yes, I accept this agreement to accept the conditions of this license
agreement, and 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 PC.
10
3 Select all the files of mobile computers on which you want to install iLaunch and
then click Install.
‘‘
4 Click Finish to complete the installation.
5 When the default C:\Documents and Settings\All Users\Start
Menu\Programs\Intermec\iLaunch folder opens, double-click the Explore
iLaunch Folders shortcut to access the .cab files.
6 Open the folder of the mobile computer files you want to copy and then copy
them to your mobile computer.
The next table lists which .cab file is necessary based on which operating system is
installed on your Intermec computer. Contact your Intermec representative for
more information about any of these files.
Note: The TEiLaunch.cab file is only available for 700 Color computers using the
Windows Mobile operating system.
11
.cab Files Installed Based On Computer Model And Operating System
Windows
Model Mobile 2003
700
Windows Mobile
5.0
Windows CE
4.2
Windows CE
5.0
Windows
Mobile 6.0
iLaunch.cab
iLaunch_WM2005
teiLaunch.cab .cab
teiLaunch_WM20
05.cab
CK30
CK31
CK60
CV30
iLaunch30.cab
iLaunch_WM2005
.cab
CN2A
iLaunch_Win
CE.cab
iLaunch.cab
CN2B iLaunch.cab
CN3
CN30
iLaunch_WM2005
.cab
CV60
CK32
iLaunch_WM
6.cab
iLaunch.cab
iLaunch_WM2005
.cab
CK3
iLaunch_WM
6.cab
Copying the .cab File
Use .cab files to install iLaunch on your mobile computer.
To copy a .cab file
1 On your mobile computer, search for the folder \NVStorage\CabFiles. If one
does not exist, in the NVStorage directory, create a folder called “Cab Files.”
2 Install the 2577 directory that allows for automatic .cab file extraction from the
appropriate tools CD.
3 From your PC computer, copy the appropriate .cab file to the
\NVStorage\CabFiles folder on the mobile computer.
4 Warm boot the mobile computer to automatically install the file.
Do not extract the files by tapping on the .cab file in File Explorer. This will
delete the .cab file. Instead, extract the .cab file by performing a warm boot.
Note: NVStorage refers to the folder name of the card you installed in the on your
mobile computer. This may either be a SDMMC Disk or Storage Card, SD Card,
Flash File Store, CK_FFS, or other nonvolatile storage option.
Installing iLaunch Without a PC Computer
Refer to the computer’s user’s guide or user’s manual for information on installing
.cab files.
12
About the .ini File
The .ini file controls how iLaunch operates on your mobile computer. By default, a
sample .ini file is installed on your mobile computer when you install iLaunch.
Open and edit the .ini file to include your preferred application to launch, password,
and other settings in iLaunch. For a complete list of values you can edit in the .ini
file, see the next section, “Editing the .ini File.”
Before you edit the .ini file, you must first:
•
Install the iLaunch application on your mobile computer.
•
Make sure that Active Sync is installed on your PC computer.
Editing the .ini File
After you install iLaunch, copy the .ini file from your mobile computer to your PC.
To copy and open the .ini file
1 Use a USB cable to connect the mobile computer to the PC computer.
Or,
Remove the storage card from the mobile computer and insert it into a card
reader attached to the PC computer.
2 On the PC computer, go to Start > Programs > Remote Display Control >
Remote Display Control Host.
3 On the mobile computer, go to Start > Programs > certdisp. On the About
CerDisp page, tap OK.
4 On the remote Display Control page, tap, Connect and then OK. The mobile
computer screen appears on your PC computer.
5 Using the PC computer, open a File Explorer window on the mobile computer.
6 Navigate to the NVStorage\launcher folder, where NVStorage is the folder name
of the card you installed in on the mobile computer.
7 Copy the ini file from the NVStorage\launcher folder to your PC computer.
8 Double-click the .ini file.
After you open it, you can edit one or all of the sections in the .ini file. For a sample
.ini file, see “Sample .ini File” on page 18.
Make sure to save the .ini after you edit it and then, transfer the file from your PC to
your mobile computer.
[Caption]
The [Caption] section contains the text that is displayed on each button when
iLaunch is launched. Captions must be specified in sequential order.
To edit the text that is displayed on a button
1 Go to the [Caption] section of the .ini file that reads: ButtonX=text.
2 Change X to a numberical value from 1 through 10.
13
3 Change “text” to the text you want to appear on the button.
4 Type another line for each button text you want to add. You can specify up to
five buttons on CK30 computers and up to ten on all other computers.
Note: If no text is specified for a button, iLaunch does not display the
button. If Button1 is the only button with a caption, the application
associated with that button may be launched automatically after iLaunch
starts. For more details on automatic launching at startup, see “[Auto
start]” on page 17.
[exe]
The [exe] section associates each button with a particular application. After you
associate a button with an application, you can press that button to launch the
application.
You can use the [exe] value to associate Visual Basic applications, WAV files, MP3
files, Word documents, and other files with file associations to launch when a
specific button is pressed.
To associate an application with a button
1 Go to the [exe] section that reads: ButtonX=path\app.ext.
2 Change X to the numerical value of the button that will launch the application.
The value for X must be a number from 1 through 10.
3 Change path\app.ext to the directory that contains the application you want to
launch.
[Bitmaps]
The [Bitmaps] section points to a specific bitmap (.bmp) image that is displayed at
the top of the iLaunch menu. If you do not have a bitmap to display, leave this field
blank.
To display a bitmap at the top of the iLaunch menu
1 Create a .bmp image and place it in a folder.
The bitmap should be 280 x 80 in 16 colors for the CV60 computer and 140 x 40
in 16 colors for all other computers. The size does not have to be exact; smaller
images will be centered and larger images will be cropped.
2 Go to the [Bitmaps] section, that reads: TopLogo=path\file.bmp.
3 Change path to the full path to the file.
4 Change file.bmp to the bitmap you want to display.
Note: CK30 computers cannot display the bitmap due to screen size limitations.
[password]
This section sets the password required to exit iLaunch. If you leave this section, or
the value after the key name blank, you will not be prompted for a password to exit
the application. Note that:
14
•
A password may be comprised of any alphanumeric character and must be no
more than six characters long.
•
Make sure that the characters you chose for the password can be entered using
the keypad or SIP keyboard available on the computer.
To change the password required to exit iLaunch
1 Go to the [password] section, that reads: pwd=paswrd.
2 Change paswrd to the password you want to exit iLaunch.
3 Delete the cpwd setting.
Note: When iLaunch initially starts up, the password is read, encrypted, written
back to the .ini file in the cpwd key, and then the pwd key is deleted to prevent
retrieving the password from the .ini file.
[ApplicationKeys]
This section associates an application with an application key on a mobile computer
keypad. If no application is specified:
•
For computers not running TE 2000, all application keys are mapped to
iLaunch.
•
For computers running TE 2000, iLaunch sets Application Key 1 to TE 2000,
Application Key 2 to iBrowse, and Application Keys 3 and 4 to iLaunch.
If the default mappings are changed, use the .ini file to ensure any overwritten
default is accessible. Always map at least one application key to iLaunch so the user
can navigate back to iLaunch to launch other applications.
Note: Application keys are only available on computers running the Windows
Mobile operating system.When iLaunch is installed on the CN3, CK3, CK32, or
CV30, the [Windows] key is automatically mapped as the application key.
To map an application key to the keypad
1 In the [ApplicationKeys] section, type: AppKeyXExe=[ButtonY | LAUNCHER |
path\app.exe].
2 Change X in AppKeyXExe to the number of the application key on the physical
keypad.
3 Enter one of the three values for the parameter:
•
Use ButtonY to launch the application associated with ButtonY from the
[exe] section.
•
Use LAUNCHER to launch iLaunch.
•
Use path\app.ext to launch an application not assigned to an iLaunch Screen
button. The only valid AppKey buttons that can be remapped are 1 - 4.
Use the information below to determine the application key a button is associated
with. Depending on the type of mobile computer you have, different buttons are
associated with different application keys:
15
•
On the 700 Color, CN2B Application Key 1 is mapped to A1, Application Key 2 is
mapped to A2, Application Key 3 is mapped to A3, and Application Key 4 is
mapped to A4.
•
On CN3, CK3, CK32, or CV30 computers, Application Key 1 is mapped to the
[Windows] key, if one exists.
•
On the CK60 and CN30 computers running Windows Mobile 5.0 Application
Key 1 is mapped to Gold [Windows], Application Key 2 to Gold [smiley],
Application Key 3 is mapped to Gold [arch], and Application Key 4 is mapped to
Gold [ok].
CK60 and CN30 Application Keys
[Disabled if no signal]
This section allows buttons to be disabled when no signal is available from the
WLAN radio. When the computer is not receiving a signal, the specified buttons are
inactive. When the computer regains a signal, the buttons are re-enabled.
To disable a button when no WLAN radio signal is available
1 In the [Disabled if no signal] section, type: ButtonX=TRUE | FALSE.
2 Change X to the button number that is disabled when no signal is available.
3 Choose TRUE or FALSE (default).
[EnforceSingleAppInstance]
This section 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 and any additional attempts to start the application bring the
original instance into focus. However, under Windows CE operating systems,
starting an application multiple times results in multiple instances.
To enforce a single application instance
1 In the [EnforceSingleAppInstance] section, type: ButtonX=TRUE | FALSE.
2 Change X it to the number of the button mapped to the application that will be
limited to a single instance.
3 Choose TRUE or FALSE (default).
16
[parameters]
This section specifies optional parameters to append when launching an
application. For example, if adding the /f parameter launches APP1.EXE in full
screen mode, the /f parameter is specified here.
To specify optional parameters
1 In the [parameters] section, type: ButtonX=/parm1 /parm2.
2 Change X to the number of the button that launches the application that takes
this parameter.
3 Choose a value for the parameters for the application. The default value is no
parameters.
[Auto start]
This section enables or disables the ability to auto start an application when
iLaunch starts up. If Button1 is the only button with text applied in the [Caption]
section, and if only one application is listed in the [exe] section, that application can
be auto-started when iLaunch starts.
To enable or disable auto start
1 In the [Auto start] section, type: Enabled=TRUE | FALSE.
2 Choose TRUE or FALSE.
•
TRUE directs iLaunch to auto-start the target application when iLaunch is
launched. The default is TRUE.
•
FALSE disables auto-starting.
Saving and Transferring the .ini File
After you edit the .ini file, you must save it on your PC and then, transfer it to your
mobile computer.
17
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
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]
18
AppKey1Exe=Button3
AppKey2Exe=Button1
AppKey3Exe=LAUNCHER
AppKey4Exe=LAUNCHER
Reserved .ini File Values
You can use the CURRENTCARD literal instead of an explicit path in the .ini file to
indicate that iLaunch 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:
•
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 computer with a Secure Digital card installed, the first path found would
be \SDMMC Disk, so Button1 of the [exe] section would point to \SDMMC
Disk\testapp\app1.exe.
Note: Although CURRENTCARD is available, specify the path and file name when
possible to prevent issues that might occur if the storage options on the storage
device are changed.
Starting iLaunch
iLaunch automatically starts up on a warm or cold boot if the .cab file
installed properly.
To restart iLaunch
1 On a Mobile Operating System:
•
Select Start > Intermec Launcher
•
Select Start > Programs > the Intermec Launcher icon.
Or,
On a CE Operating System:
19
•
Double-tap the Intermec Launcher icon on the PC.
•
Select Start > Programs > iLaunch.
The initial launch screen appears. The screen contains indicators for battery
status and signal strength. The serial number is also displayed on this screen
for all computers except the CK30 computer.
2 Tap Status to view the status screen, which displays the IP status, the MAC
address of the WLAN radio, authentication type, and the serial number of the
computer. Note that the CV60 computer does not display battery status as it
does not use a battery.
3 Tap Exit to go to the Exit screen, and then enter your six-character password to
close iLaunch.
4 Tap Keyboard for an onscreen keyboard or Soft Input Panel (SIP) keyboard with
which to enter your password.
.
Note: 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.
20
Windows Mobile computers can use the application keys to switch between
applications. The Windows CE operating system does not provide this option. On
the CV60 computer, use the taskbar at the bottom of the screen to switch between
applications without closing them. On mobile computers with smaller screen sizes
or those using the Windows CE operating system, use the small icon in the lower
right to display a list of running applications and choose between them.
Although iLaunch attempts to block a user from accessing other parts of the
system, other applications launched from within iLaunch may allow the user
to access other parts of the system. One known example of this is Internet
Explorer. If Internet Explorer is left as an option, an experienced user may
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 computer, the error number is displayed instead of the full
text. Visit http://msdn.microsoft.com and search for the error number for more
details.
Uninstalling iLaunch
You can uninstall iLaunch from the mobile computer or PC.
Uninstalling iLaunch From the Mobile Computer
No automatic uninstallation is available at this time.
To manually uninstall iLaunch
1 Remove the following files:
\windows\start menu\Intermec launcher.lnk
\windows\startup\Intermec launcher.lnk
\windows\launcher\*.*
NVStorage\launcher\*.*
NVStorage\Cabfiles\launcher*.cab
where NVStorage is the folder name of the card you have installed in the device.
This is usually an SDMMC Disk, SD Card, or Storage Card.
2 Rename Autorunold.dat to autorun.dat.
Uninstalling iLaunch From the PC Computer
1 From the PC, access the C:\Program Files\Intermec\iLaunch folder.
2 Double-click the Explore iLaunch Folders shortcut.
3 Double-click the UninstalliLaunch.exe executable.
21
4 Click Uninstall to remove the iLaunch files from your PC.
5 Click Finish to complete the uninstallation of iLaunch.
Versions of iLaunch
The evaluation version and terminal emulation version of iLauch are available.
Evaluation Version of iLaunch
Evaluation versions of iLaunch are available. These versions allow some restricted
use. iLaunch 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 stop 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.
22
TE 2000 Version of iLaunch
The terminal emulation version (TE 2000) 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. When you add the
SysStart utility to the Autorun.dat file, the utility runs at startup to prevent the user
from accessing the system during startup and .cab file extraction. SysStart is not
added to the Autorun.dat file.
Note: NVStorage refers to the type of nonvolatile storage used in the computer.
To use SysStart.exe
1 Copy 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
XX is CF if your storage card is a CompactFlash card or SD if your storage card is
a Secure Digital card.
4 Rename \NVStorage\2577\autorunXX.dat to \NVStorage\2577\autorun.dat
Although SysStart attempts to block users from other parts of the system,
other applications launched at system startup may still start up, creating
only a partial lock down of the computer.
Known Issues
If owner information is set to appear at startup, the owner information shows up on
top of iLaunch.
To disable displaying the owner information
1 Tap Start > Settings, then tap Owner Information.
2 Clear the Show information when device is turned on checkbox.
23
Contacting Customer Support
For information on contacting your Intermec representative, see “Global Services
and Support” on page vii. When contacting Customer Support, have the following
information ready:
•
model number of the computer.
To find the model number, go to Start > Inernet Explorer > Intermec.
•
version number of the operating system.
To find the version number of the operating system, go to Start > Settings >
Systems tab > About.
•
version number of the iLaunch software.
To find the version number of the operating system, go to Start > Settings >
Programs > Intermec Launcher > Status.
Troubleshooting iLaunch
This section includes lists of problems and possible solutions.
24
iLaunch Problems and Solutions
Problem
Solution
No buttons show when iLaunch starts. Check these conditions:
•
Make sure a valid Menu.ini file is
in the same directory as the
iLaunch files. Look in the
\NVStorage\Launcher,
\NVStorage\Launcher, or
\Program Files\Launcher paths.
•
Make sure that iLaunch is running
on an Intermec computer.
•
Make sure that you are using the
correct case. The section names
and labels in the .ini file are casesensitive.
The screen does not rotate when the
button is pressed to rotate it.
iLaunch does not support screen rotation.
After copying the .cab file to the
\CabFiles folder on my storage card,
iLaunch does not automatically start.
Warm boot the Intermec computer again.
To automatically extract files in the
\CabFiles folder, other supporting files
must be on the storage card. Contact
Customer Support to make sure your
Intermec computer is properly set up to
autoextract .cab files.
iLaunch reports no network connection On Windows Mobile 5.0 computers, if the
even though the network settings are
computer is connected to ActiveSync, the
correct
ActiveSync application disables all
network connections as a security
measure.
Application Updates
Version 1.21
Added:
•
Support for CK3, CN3, Windows Mobile 6 computers.
Version 1.20
Added:
•
Support for 700 Color and CK32 computers running Windows Mobile 2005.
•
Support for CV30 computers running Windows CE 5.0.
25
Version 1.19
Fixed:
•
“Space Constrained” keyboard for the CV30 did not have the Windows Key
correctly mapped 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 computers.
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.
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) computers.
Version 1.15
Added:
26
•
Support for CK60, CN30 computers 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 CK30).
•
Checks to only enable buttons if radio is connected (set in INI file).
•
Support for installing iLaunch on computers 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
Fixed:
•
When launching another application, the command bar was partially erased by
iLaunch in some instances.
•
Users could still get into the system - open clock, hold action, and tap-hold 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.
27
Version 1.05B
Added:
•
Changed some code that allows iLaunch to disable the Start button when
another application has focus.
Version 1.05A
Fixed:
•
Fixed the battery status page so that the timer is destroyed appropriately.
Added:
•
iLaunch now tries to disable the Start menu for applications that are not locked
down.
•
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
Fixed:
•
User prevented from exiting iLaunch if the user were at the main dialog when
Enter was tapped.
Version 1.01C
Fixed:
•
The application keys are set appropriately on 700 Color Computers with
alphanumeric keyboards.
Version 1.01B
Fixed:
•
The Esc key no longer allows user to exit iLaunch.
•
Changed the version slightly to display TE 2000 before the iLaunch version
number if it is a TE 2000 build.
•
Updated the copyright to include 2003.
Version 1.01
Added:
28
•
Created a separate evaluation version of the application to evaluate for 60 days during the trial period, reminder messages pop up after every time iLaunch
launches three applications.
•
Added Copyright information.
•
Added code to lock down the Exit dialog.
•
Added TE 2000-specific features, such as the application keys are automatically
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 where iLaunch is running. This uses the same INI file on both
CompactFlash and Secure Digital storage cards.
29
Worldwide Headquarters
6001 36th Avenue West
Everett, Washington 98203
U.S.A.
tel 425.348.2600
fax 425.355.9551
www.intermec.com
© 2008 Intermec Technologies
Corporation. All rights reserved.
*934-045-001*
P/N 934-045-001

User`s Guide

Transcription

Similar documents

Brochure - Mountain Home Public Schools

Travel Information for Vienna UZA2/Pharmaziezentrum Althanstraße

33 Series Sweeperweb

Time Sheet Reminder

Beneteau First 45F5 (3 cab)

Flatbed

DAF FT XF105.460

powerful•flexible•gentle

Fire Fighting PDF

XF105 series cabs