StartUp Control (StartUpCtl)

Version 1.8
Copyrights

The product described in this document may include copyrighted computer programs.
Laws in the United States and other countries preserve for certain exclusive rights for
copyrighted computer programs. Accordingly, any copyrighted computer programs
contained in the product described in this document may not be copied or reproduced
in any manner without the express written permission.

© 2015 Symbol Technologies LLC All Rights Reserved

No part of this document may be reproduced, transmitted, stored in a retrieval system, or

translated into any language or computer language, in any form or by any means,
without the prior written permission.
Furthermore, the use of our products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent
applications, except for the normal non-exclusive, royalty-free license to use that arises
by operation of law in the sale of a product.

Trademarks

Zebra and the Zebra head graphic are registered trademarks of ZIH Corp. The Symbol
logo is a registered trademark of Symbol Technologies LLC, a Zebra Technologies
company.
Contents

Table of Contents
1 Overview............................................................. 1
1.1 Introduction ............................................................... 1
1.2 Terminology................................................................ 1

2 General Information ............................................ 3

2.1 Installation .................................................................. 3
Automatic Installation ..........................................................3
Manual Installation................................................................3
2.2 Uninstalling StartUpCtl from the Device ................. 4
Uninstalling via Host PC ........................................................4
Uninstalling via Mobile Device............................................5
Manual Uninstalling ...............................................................5
2.3 StartUpCtlConfig.txt .................................................. 5
2.4 Application Features ................................................ 6
Storage Card Support ..........................................................6
Debugging .............................................................................6
Logging Application Data ..................................................7
2.5 Using Script Files ......................................................... 8
OnRestore.txt File...................................................................8
OnReset.txt File ......................................................................8
Sub-script File Processing .....................................................8

3 Process Flows ..................................................... 9

3.1 OnRestore .................................................................. 9
3.2 OnReset .................................................................... 10

4 StartUpCtl Commands ....................................... 11

4.1 Special Notes ........................................................... 11
4.2 Delay ......................................................................... 11
4.3 Reset ......................................................................... 11
4.4 Wait ........................................................................... 13
4.5 Regmerge ................................................................ 13
4.6 CopyFile.................................................................... 14
4.7 Copy ......................................................................... 14
4.8 Rename .................................................................... 15
4.9 Move ......................................................................... 15
4.10 Delete ....................................................................... 16
4.11 Mkdir ......................................................................... 16

StartUpCtl User Manual i

Contents

4.12 Comments ............................................................... 16

4.13 SplashOn .................................................................. 17
4.14 SplashOff .................................................................. 17
4.15 IdleTimerReset .......................................................... 18

5 Splash Screen.................................................... 19
5.1 Splash Screen Components .................................. 19
Custom Image .................................................................... 20
StartUpCtl Banner ............................................................... 21

6 Appendix .......................................................... 23
6.1 Sample StartUpCtlLog.txt File ................................ 23
6.2 Avoiding Syntax Errors in Scripts ............................ 23
6.3 Installation of .cab files using Wceload ............... 24

StartUpCtl User Manual ii

 StartUpCtl

1 Overview

1.1 Introduction
StartUpCtl is an extension to the Startup process found on Symbol enterprise
mobility devices. The Startup process controls the execution of certain file types
when a mobile device is reset, enabling applications to be installed and/or run
automatically.

Figure 1

During the startup process, StartUpCtl launches any files that it finds in the
\Application\Startup folder (See Figure 1), StartUpCtl goes further by allowing
user to control the order that files are executed on a reboot of the mobile device.

1.2 Terminology
To try and avoid confusion, throughout this document, a clean boot on a
Windows Mobile 5.0 and higher device and a cold boot on a Windows CE device
is referred to as “Restore”. A warm boot is referred to as “Reset”.

StartUpCtl User Manual 1

 StartUpCtl

StartUpCtl User Manual 2

 StartUpCtl

2 General Information

2.1 Installation

Automatic Installation
To install StartUpCtl on a mobile device follow the steps given below.

1. Download the StartUpCtl installation package from the Symbol

support website at http://support.symbol.com.
2. Run the installation package on the host PC. Follow the installation
wizard instructions to successfully install StartUpCtl on the host PC. After
a successful installation, StartUpCtl installation in the mobile device is
automatically initiated
3. If the mobile device is connected, device side installation is started
immediately. If the mobile device is not connected to the host PC,
connect the device to host PC via ActiveSync. Then the device side
installation will be started immediately after the connection. Follow the
installation instructions on the device to successfully install StartUpCtl
on the mobile device.
4. To install StartupCtl in any device , go to “Start – Programs –StartUpCtl
– Install StartUpCtl to mobile device” on host PC to initiate StartUpCtl
installation in the mobile device and follow the step 3

The following are saved to the mobile device, irrespective of the

destination folder chosen, during the installation.

\Application\Startup\StartUpCtl.exe – StartUpCtl executable file.

\Application\StartUpCtl\ – Folder containing the files needed

by StartUpCtl.

Manual Installation
StarUpCtl installation in the PC side provides a separate folder with contents
required to install StartUpctl in devices manually. This option is used to deploy
StartUpCtl by copying these files to device \Application folder. This is useful to
deploy StartUpCtl to multiple devices with a defined configuration.

To manually setup StartUpCtl on the mobile device do the following;

1. Download the StartUpCtl installation package from the Symbol

support website at http://support.symbol.com.
2. Run the installation package on the host PC. Follow the installation
wizard instructions to successfully install StartUpCtl on the host PC. After

StartUpCtl User Manual 3

 StartUpCtl

a successful installation, StartUpCtl installation in the mobile device is

automatically initiated
3. If the mobile device is connected, device side installation is started
immediately. If the mobile device is not connected to the host PC,
connect the device to host PC via ActiveSync. Then the device side
installation will be started immediately after the connection. Cancel
StartUpCtl installation in the mobile device.
4. Go to Start – Programs –StartUpCtl – Setup to open the Setup folder.
\Application folder inside the Setup folder contains the files necessary
for manual installation of the StartUpCtl.
5. Change the StartUpCtl script files.
6. Copy the contents of the \Application folder to device \Application
folder.
7. Copy any other relevant files according to the changes in StartUpCtl
script files. Ex: CAB installation file specified in the onRestore.txt
8. Reset the mobile device.

Note: File copying can be done by using manual file copying via
ActiveSync, Deployment servers such as MSP server etc.

After a manual installation, the mobile device needs to be reset

to allow StartUpCtl to run and for any changes to take affect.

2.2 Uninstalling StartUpCtl from the Device

To Uninstall StartupCtl device side, installed by using automatic installation can be
used following methods

Uninstalling via Host PC

1. Establish a Microsoft ActiveSync® connection between the mobile
device and the host PC.
2. In the Notification Area of the host PC, right click the ActiveSync icon
and select Open Microsoft ActiveSync option. Alternatively, double-
click the ActiveSync icon to open up the Microsoft ActiveSync
window.
3. In the Microsoft ActiveSync window go to Tools – Add/Remove
Programs.
4. De-select the checkbox alongside Symbol StartUpCtl and press OK to
remove StartUpCtl from the device. Alternatively, uninstall StartUpCtl
by highlighting Symbol StartUpCtl from the list box and pressing the
Remove button under Remove from both locations panel to remove
StartUpCtl from the PC and the device. Press OK when the Remove
Application dialog box appears, to confirm removal of StartUpCtl from
the mobile device and the host PC.

StartUpCtl User Manual 4

 StartUpCtl

NOTE: Please note that the above Remove option only removes the
temporarily stored CAB file from the host PC and does not remove
the StartUpCtl program group which includes Setup folder,
Readme, User Guide etc. It does however; remove all settings
related to StartUpCtl from the mobile device.

Uninstalling via Mobile Device

1. On Windows CE based mobile devices, go to Start – Settings – Control
Panel to open the Control Panel window. Click the Remove Programs
icon to open the Remove Programs window. Select Symbol StartUpCtl
from the list and press the Remove button.
2. On Windows Mobile based mobile devices, go to Start – Settings to
open the Settings window. In the Settings window select System and
click on the Remove Programs icon to open the Remove Program
window. Select Symbol StartUpCtl from the list of programs and press
the Remove button.
3. Press Yes when the Remove Program dialog box appears to confirm
removal of StartUpCtl from the mobile device.

Manual Uninstalling
The manual uninstallation method must be followed if StartUpCtl installation was
done using the manual installation method.

1. Remove the StartUpCtl.exe from the \Application\Setup folder.

2. Remove the \Application\StartUpCtl folder.
3. Using a remote registry editor, remove the following registry key from
the mobile device registry;

[HKEY_LOCAL_MACHINE\.startupctl]

2.3 StartUpCtlConfig.txt
StartUpCtlConfig.txt is copied to the \Application\StartUpCtl\ folder of the
mobile device during the StartUpCtl installation. This file defines the general
configuration information for StartUpCtl (described later in this guide) that cannot
be specified in script files. On each invocation of StartUpCtl, StartUpCtl reads this
file and re-configures itself.

StartUpCtl User Manual 5

 StartUpCtl

2.4 Application Features

Storage Card Support

StartUpCtl can access and execute files that are stored in storage cards inserted
in the mobile device. This feature allows storage cards to be used when the
storage space in the mobile device is limited.

To use this feature, create a folder titled “StartUpCtl” in the storage card. On the
host PC, go to Start – Programs –StartUpCtl – Setup to open the Setup folder and
open the Application folder within. Open the StartUpCtl folder located within the
Application folder and copy the OnReset and OnRestore folders into the
StartUpCtl folder inside the storage card.

StartUpCtl checks for any storage cards (See Process Flows). If the \StartUpCtl
folder is found on any storage cards, StartUpCtl processes each folder found.

Debugging
StartUpCtl has a debug mode that can be enabled/disabled manually. To
activate the debug mode, set the “Debug” parameter to “True” in the
StartUpCtlConfig.txt file.

Syntax

[Application_Properties]
Debug=True

This setting enables the debug mode in StartUpCtl. While in the debug mode,
StartUpCtl identifies any syntax errors in StartUpCtl specific commands.

While in debug mode, StartUpCtl validates each script file and processes it. If
there are no script files within the OnRestore and OnReset folders, StartUpCtl
processes the contents of these folders and logs the actions in the
StartUpCtlLog.txt file. In debug mode no file or executable is executed and only a
simulation takes place.

Note: The debug mode checks for syntax errors only in StartUpCtl
specific commands. Any other commands and their parameters
cannot be validated by the debug mechanism.

StartUpCtl User Manual 6

 StartUpCtl

Logging Application Data

StartUpCtl creates the StartUpCtlLog.txt file to log the startup process every time a
reset/restore occurs. The log file is used for maintaining operational records for
StartUpCtl. (See Sample StartUpCtlLog.txt File.)

The log file properties are defined in the StartUpCtlConfig.txt file.

[LogFile_Properties]
LogFileTempFolder=
LogFileFolder=\Application\StartUpCtl
MaxLogFileSize=

The LogFileTempFolder property defines the temporary storage location for the
log file. This location is used by StartUpCtl while generating the log file. This feature
is especially useful on Windows Mobile 5.0 based mobile devices which show
performance issues while accessing the slow flash file system. In such cases opt to
use the Cache Disk to store the temporary log file.

After completing the startup process, the log file is permanently stored in the
location specified in the LogFileFolder parameter.

At the start of an OnRestore operation, StartUpCtl renames the previous log file to
“StartUpCtlLog_Bak.txt” and creates a new file with the default name
“StartUpCtlLog.txt”.

At the start of an OnReset operation, StartUpCtl appends the existing log file with
the new data. If the log file size exceeds the specified size, then the log file will be
renamed to “StartUpCtlLog_Bak.txt” and a new "StartUpCtlLog.txt" file will be
created to enter the new log data. This maximum file size is specified in the
MaxLogFileSize parameter in bytes. The minimum allowed size for the log file is 1KB
and the maximum is 1000KB.

If there are no definitions for the LogFileTempFolder and LogFileFolder parameters

in StartUpCtlConfig.txt file, StartUpCtl searches for an alternative location, in the
order given below, and creates the log file in the path which is found first.

1. \Application\StartUpCtl

2. \Application

3. \[root]

StartUpCtl User Manual 7

 StartUpCtl

2.5 Using Script Files

The launch sequence after a Reset/Restore operation is predefined in script files.
The default script files are OnRestore.txt and OnReset.txt.

OnRestore.txt File
The OnRestore.txt is a script file that specifies the launch sequence after a Restore
operation.

StartUpCtl first processes OnRestore.txt and initiates the startup sequence

accordingly. It then checks for sub-script files in the OnRestore folder which follow
the “OnRestore_X” format (See Sub-script File Processing) and these sub-script files
are then processed.

OnReset.txt File
Similar to the OnRestore.txt file, the OnReset.txt file is a script file that specifies the
launch sequence after a reset operation. StartUpCtl processes this file and carries
out the procedures defined in it.

After processing the OnReset.txt file, StartUpCtl checks for sub-script files in the
OnReset folder which follow the “OnReset_X” format (See Sub-script File
Processing) and these sub-script files are then processed.

Sub-script File Processing

In addition to the default script files, launch sequences can be predefine in sub-
script files which are processed by StartUpCtl after processing the default script
files. The following convention is used for naming sub-script files;

 OnRestore_X.txt
 OnReset_X.txt

Where “X” can be a string of alphabetical and/or numerical characters, e.g.

OnReset_1a.txt.

StartUpCtl processes these sub-script files in alphabetical order.

The sub-script files must be stored in the same folder as the OnRestore.txt and
OnReset.txt files i.e. the OnRestore_X.txt must be stored in the OnRestore folder
and OnReset_X.txt must be stored in the OnReset folder.

StartUpCtl User Manual 8

 StartUpCtl

3 Process Flows
StartUpCtl modifies its behavior according to the device status. i.e. the process
flow after a reset differs from the process flow after a restore.

3.1 OnRestore
Below is a description of the actions performed upon Restore.

1. StartUpCtl checks for the \Application\StartUpCtl\OnRestore

folder.

2. If the \Application\StartUpCtl\OnRestore folder is located on the

mobile device, StartUpCtl checks for the OnRestore.txt file.

3. If the OnRestore.txt file exists, StartUpCtl executes only the entries

defined in the file. If the OnRestore.txt file is not found in the
OnRestore folder, then all executable files within that folder are
executed.

4. StartUpCtl then checks for sub-script files (i.e. OnRestore_X.txt,

where “X” can be a string of alphabetical and/or numerical
characters) within the Application\StartUpCtl\OnRestore folder. If
found StartUpCtl processes these files.

5. If one or more storage cards are found, steps 1 to 4 are repeated

on each storage card containing a StartUpCtl\OnRestore folder.

6. Upon completion of the above steps, the OnReset process flow is

performed.

StartUpCtl User Manual 9

 StartUpCtl

3.2 OnReset
Below is a description of the actions performed upon Reset.

1. StartUpCtl checks for \Application\StartUpCtl\OnReset folder.

2. If that folder exists, StartUpCtl checks for the OnReset.txt file

located within it.

3. If the file exists in the \Application\StartUpCtl\OnReset folder,

StartUpCtl carries out the launch sequence according to the
script. If the OnReset.txt is not found in the OnRestore folder, then
all executable files within that folder are executed.

4. StartUpCtl then checks for sub-script files (i.e. OnReset_X.txt where

“X” can be a string of alphabetical and/or numerical characters)
within the \Application\StartUpCtl\OnReset folder. If found
StartUpCtl processes these files.

5. If one or more storage cards are found, steps 1 to 4 is repeated on

each storage card containing a StartUpCtl\OnReset folder.

6. Upon completion of the above steps StartUpCtl exits.

In summary, a Restore launches applications first from the OnRestore folder, and
then from the OnReset folder. A Reset only launches applications from the
OnReset folder.

The OnRestore folder is intended for automated installation of applications; the

OnReset folder is intended for automated launching of (those) applications.

StartUpCtl User Manual 10

 StartUpCtl

4 StartUpCtl Commands
The order in which applications are installed and launched can be controlled
through the OnRestore.txt and OnReset.txt files. Within these files, StartUpCtl
supports the launching of files as well as some special purpose commands to
control the launch process.

4.1 Special Notes

Absolute file paths should be enclosed with double quotes when spaces are
present in the absolute path name. Without double quotes, StartUpCtl only
processes the first potion of the path. Enclosing paths in single quotes is not
supported.

Example

Copy “\Application\My Program.exe” “\Program Files\My Program”

The StartUpCtlLog.txt file, which logs the process flow of StartUpCtl, can be
examined to find the commands which were skipped due to syntax errors or
runtime errors.

4.2 Delay
Syntax

Delay [seconds]

The Delay command causes StartUpCtl to do nothing for the specified number of
seconds. If no parameter is provided the command is ignored.

Example

“Delay 10” stops StartUpCtl from launching any other files for ten seconds.

4.3 Reset
Syntax

Reset

The Reset command causes StartUpCtl to perform a Reset. This command is only
recognized within the OnRestore script/sub-script files. The Reset command is the
last command executed by StartUpCtl. Even if this command is detected in the
beginning or middle of the OnRestore script, StartUpCtl does not execute reset
the mobile device until the other operations in the OnRestore script are
completed.

StartUpCtl User Manual 11

 StartUpCtl

The Reset command may be useful in making some post-installation changes

such as driver registry changes, loading of new fonts, etc. to take effect.

StartUpCtl User Manual 12

 StartUpCtl

4.4 Wait
Syntax

Wait [seconds] {[/q|Q] [/c|C]}

The Wait command causes StartUpCtl to wait until the last file that was launched
has finished and terminated.

The Wait command optionally takes two parameters, a timeout value in seconds
and an action to perform if the timeout is reached.

If “/q” is provided as the action parameter then StartUpCtl waits the specified
number of seconds then exits without doing any further processing if the program
launched has not terminated during the given timeout.

With “/c” specified as the action parameter, StartUpCtl waits the specified
number of seconds and if the launched program has not terminated within the
given duration StartUpCtl continues with the other commands in the file.

By default if no parameters are provided, the Wait command waits for 300
seconds for the last file launched to complete and quits without continuing with
the rest of the commands if this timeout is reached.

4.5 Regmerge
Syntax

regmerge [/q|/Q] \Application\XXXX\myRegSettings.reg

RegMerge is a built-in driver that allows entries found in .reg files to be stored in
the Windows CE registry. RegMerge can be used from within the OnRestore and
OnReset script files to apply .reg files to the Windows CE registry.

The “/q” or “/Q” parameter specifies quiet mode. This causes RegMerge not to
prompt user before merging a file.

Regmerge.exe is normally found in the \Windows folder but on some mobile

devices it may not be present. In such cases StartUpCtl utilizes the Regmerge.exe
file located in the \Application\StartUpCtl\Bin folder.

StartUpCtl User Manual 13

 StartUpCtl

4.6 CopyFile
Syntax

copyfile \Application\XXXX\Test1.cpy

CopyFile is a built-in driver that is used to copy files from one location to another
as defined in .cpy files. CopyFile can be used from within the OnRestore and
OnReset script files to copy files from one location to another.

Copyfiles.exe is normally found in the \Windows folder but on some mobile

devices it may not be present. In such cases StartUpCtl uses the copyfiles.exe
executable located in the \Application\StartUpCtl\Bin folder.

Note: The behavior of the Regmerge and Copyfile drivers (which come
with the StartUpCtl installation package and are up-to-date) can
be slightly different to the Regmerge.exe and Copyfiles.exe
(found in \Windows folder) especially in cases of older operating
systems.

4.7 Copy
This command copies files from one location to another. The behavior of this
command is similar to the COPY command in MS-DOS, without the additional
switch support that is available in DOS.

Syntax

Copy <src> <dest>

<src> is the absolute path name of the file to be copied.

<dest> is the absolute path of the new location which the file is copied to.

Example 1

copy \Application\Temp\DEMO.CPY \Application\Temp2\

Example 2

copy “\Application\My Program.exe” “\Program Files\My Program\My

Program.exe”

StartUpCtl User Manual 14

 StartUpCtl

4.8 Rename
This command renames a file to a user specified name. The behavior of this
command is similar to the RENAME command in MS-DOS. A new path for the
destination file cannot be specified.

Syntax

Rename <src> <name>

<src> is the absolute path and file name of the file to be renamed.

<name> is the new file name.

Example 1

rename “\Application\My Program.exe” “My New Program.exe”

Example 2

rename \Application\Demo.cpy Demo_New.cpy

4.9 Move
Moves a file/s to a specified location. The behavior of this command is similar to
the MOVE command in MS-DOS without the additional switch support that is
available in DOS. If a file with the same name is present in the destination folder it
is overwritten with the new file without any prompting.

Note: The file move operation will fail on Windows Mobile devices, if
the destination folder does not exist.

Syntax

Move <src> <dest>

<src> is the absolute path of the file to be moved.

<dest> is the absolute path of the destination.

Example 1

Move “\Application\My Program.exe” “\Program Files\My Program\”

Example 2

Move \Application\CtlPanel.exe \Windows

StartUpCtl User Manual 15

 StartUpCtl

4.10 Delete
This command deletes a specified file from the mobile device. The behavior of
this command is similar to that of MS-DOS command DEL.

Syntax

Delete <name>

<name> is the file name or path of the file or to be deleted

Example 1

Delete “\Program Files\My Program\My Program.exe”

Note: Delete command only supports deleting individual files and it

does NOT support deleting Folders

4.11 Mkdir
This command creates a new folder. The behavior of this command is similar to
the MKDIR command in MS-DOS.

Syntax

Mkdir <folder>

<folder> is the absolute path of the folder to be created

Example 1

Mkdir “\Program Files\My Program”.

Example 2

Mkdir \Application\Temp_1\Temp_2

4.12 Comments
Comments can be added to the OnRestore and OnReset script files. Any line
beginning with the hash (“#”) or semi-colon (“;”) is taken as a comment and is
ignored during processing.

Syntax

StartUpCtl User Manual 16

 StartUpCtl

Example 1

# This is a comment.

Example 2

; This is also a comment.

4.13 SplashOn
Use the SplashOn command in OnRestore and OnReset script files to display the
splash screen on the mobile device. When this command is invoked, StartUpCtl
displays the splash screen in the foreground. This command does not affect the
start-up process which continues in the background while the splash screen is
displayed. Optionally, a time period (in seconds) for which the splash screen is
displayed can be defined.

Syntax

SplashOn [Timeout]

Example

SplashOn 10

The above example specifies that the splash screen should be displayed for 10
seconds. After the timeout, the splash screen is removed from the display area.
However if processing of StartUpCtl script commands are completed before 10
seconds, then it will destroy the Splash screen and exit.

Note: If a timeout is not specified for the SplashOn command, then the
default timeout of “0” is used. When the timeout is “0”, StartUpCtl
displays splash screen indefinitely until all StartUpCtl processes
are complete or until the SplashOff command is executed.

4.14 SplashOff
The SplashOff command is used in OnRestore and OnReset script files to force
StartUpCtl to remove the splash screen from the mobile device screen. When this
command is executed, StartUpCtl ignores the timeout period set in the SplashOn
command and removes the splash screen.

Syntax

SplashOff

StartUpCtl User Manual 17

 StartUpCtl

4.15 IdleTimerReset
The IdleTimerReset command tells StartUpCtl to periodically call the Windows
SystemIdleTimerReset function to prevent the device from going into a
suspended state.

Syntax

IdleTimerReset {[/a|A] [/z|Z]} [Period]

The IdleTimerReset command optionally takes three parameters:

The /a|A parameter activates the IdleTimerReset feature. This is the default
action when the IdleTimerReset command is called without any parameters.

The /z|Z parameter de-activates the IdleTimerReset feature, allowing the device
to enter a suspended state as it would have before the IdleTimerReset command
was called. The IdleTimerReset feature will also be de-activated when StartUpCtl
exits.

The [period] is an integer value greater than zero representing the interval in
seconds at which the Windows SystemIdleTimerReset function should be called.

If the [period] parameter is not specified, StartUpCtl will use the following
procedure to calculate a suitable value.

StartUpCtl will try to read the two registry values ‘ACSuspendTimeout’ and
‘BattSuspendTimeout’ in the following registry location…

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts].

If either or both of values are read successfully then the lowest of the two will be
used to calculate the period. Zero values are considered to represent 300
seconds.

If this lower value is greater than fifteen seconds, a further five seconds are
subtracted to arrive at the final value that will be used for the period. If the lower
value is 15 seconds or less, one second is subtracted to arrive at the final value
that will be used for the period.

If the [period] parameter is not given and the registry values above could not be
read, StartUpCtl will use a default value of fifteen seconds as the interval for
calling the SystemIdleTimerReset function.

Example:

IdleTimerReset /A 30 - Start calling ‘SystemIdleTimerReset’ every 30 seconds

IdleTimerReset /Z - Stop calling ‘SystemIdleTimerReset’

StartUpCtl User Manual 18

 StartUpCtl

5 Splash Screen
StartUpCtl can display a splash screen on the mobile device to hide the
OnRestore/OnReset processing from the user. The splash screen can be displayed
and controlled at anytime during the start up process through the use of the
SplashOn and SplashOff commands.

5.1 Splash Screen Components

Custom Image
Area

Fixed Banner Area

(Height 70 pixels)

Figure 2 - StartUpCtl Default Splash Screen

StartUpCtl User Manual 19

 StartUpCtl

Custom Image
The image displayed in the custom image area (upper portion of the splash
screen) can be customized by editing the StartUpCtlConfig.txt file. The custom
image must be a bitmap file (.bmp extension). The custom image is specified in
the StartUpCtlConfig.txt file as follows;

Syntax

[Splash_Properties]
ImagePath=\Application\StartUpCtl\StartUpCtlImg.bmp

The bitmap image is placed in the center of the custom image area. If the image
is larger than the custom image area, it appears clipped to fit. If the image is
smaller than the custom image area, the background color is shown around the
image.

Note: The defined image must be present in the location specified. If

the specified image does not exist at the defined location, then
the default StartUpCtl splash screen is displayed.

Splash screen
display on a
small screen

Splash screen
display on a
large screen

StartUpCtl User Manual 20

 StartUpCtl

StartUpCtl Banner
The bottom part of the splash screen is reserved for the banner. The banner area
has a fixed height of 70 pixels. This area is used for displaying StartUpCtl feedback
information to the user.

The left of the banner is designated for displaying feedback information. This
feedback information differs according to the booting process. ‘Initializing…
Please wait...’ is displayed during a restore process (see Terminology), whilst
‘Starting up… Please wait’ is displayed a reset operation (see Terminology). The
right side of the banner area displays the StartUpCtl product name, version and
copyright information.

Unlike the custom image area, the banner area contents dynamically change
according to the physical size and orientation of the mobile device.

StartUpCtl User Manual 21

 StartUpCtl

6 Appendix

6.1 Sample StartUpCtlLog.txt File

2003/22/05-08:21:51 StartUpCtl V1.1
2003/22/05-08:21:51 Settings : Debug mode ON
2003/22/05-08:21:51 Settings : LogFile Temp Folder :
\Application\StartUpCtl
2003/22/05-08:21:51 Settings : LogFile Folder :
\Application\StartUpCtl
2003/22/05-08:21:51 Settings : Max LogFile size : 3000
2003/22/05-08:21:51 OnReset folder detected
2003/22/05-08:21:51 OnReset.txt found
2003/22/05-08:21:51 Start Sub script File Process in folder :
\Application\StartUpCtl \ OnReset
2003/22/05-08:21:51 Sub Script File count is zero
2003/22/05-08:21:51 End Sub script File Process in folder :
\Application\StartUpCtl \ OnReset
2003/22/05-08:21:51 StartUpCtl Finished
2003/22/05-08:21:51 ____________________________________

6.2 Avoiding Syntax Errors in Scripts

Proper syntax is critical when creating StartUpCtl script files. Some of the more
common mistakes are related to correctly specifying file names. The full file name
with its extension is required. For example if a CAB file needs to be installed,
specifying “\Windows\wceload” does not work. Specify the full file name as
“\Windows\wceload.exe”.

Another common mistake is related to file names with embedded spaces. It is

always good practice to surround the file name with double quotation marks.
Below is an example of a properly formatted script command that installs a CAB
file.

Syntax

\Windows\wceload.exe “\Application\DataWedge.cab”

StartUpCtl User Manual 23

 StartUpCtl

6.3 Installation of .cab files using Wceload

As part of the Microsoft mobile device operating system, the Wceload tool
(wceload.exe) runs on the target device. This tool is typically used to install a
.cab file to a location that is specified. Most .cab files are configured to enable
the user to select the destination folder where the .cab file is installed. However,
user can choose to suppress the destination selection prompt and install the .cab
file to a default location, specified in the .inf file used to create the .cab file.

For example, the following script command silently installs the DataWedge.cab
file without prompting the user for any input:

Syntax

\Windows\wceload.exe /noui /delete 0 “\Application\DataWedge.cab”

The /noui parameter specifies whether user input is needed/dropped during

installation. By default, prompts are answered with ‘Yes’.

The /delete parameter specifies how Wceload removes the .cab file after
installation. /delete 0 does not remove the .cab file after the contents are
installed.

The Wceload parameters vary across the different operating system versions. The
following table lists some of the differences for frequently used options.

WM 5.0 WinCE
WinC
Parameter and 6.0 and Comment
E 5.0
above above
Specifies whether user input is
needed/dropped during
/noui    installation. By default,
prompts are answered with
‘Yes’.
Does not remove the .cab file
/delete 0    after the contents are
installed.
Removes the .cab file after
/delete 1   the contents are installed.
This is the default.
Specifies that the user is not
/noaskdest   prompted for the installation
folder.

Detailed information on Wceload can be found on MSDN at www.msdn.com.

StartUpCtl User Manual 24

 StartUpCtl

Note: If the necessary permissions to install a CAB file are not set, the
silent installation process fails, because it is not able to prompt
the user for authorization.

StartUpCtl User Manual 25