Intermec cn30 User Guide
Chapter 3 — Configuring the CN30
100
CN30 Mobile Computer User’s Manual
Launching Your Application Automatically
You can configure the various media used in the Windows Mobile system
with a folder name and can change the media in the registry of the system.
Many of the startup components rely on folder names to locate information
files, applications, or other related data.
with a folder name and can change the media in the registry of the system.
Many of the startup components rely on folder names to locate information
files, applications, or other related data.
The registry keys used by FolderCopy and other startup components to
retrieve the folder names are as follows:
retrieve the folder names are as follows:
Flash File Store
[HKLM\Drivers\BuiltIn\FlshDrv]
“FolderName”=“Flash File Store”
[HKLM\Drivers\BuiltIn\FlshDrv]
“FolderName”=“Flash File Store”
SD Card (Storage Card)
[HKLM\System\StorageManager\Profiles\SDMemory]
“Folder”=“Storage Card”
[HKLM\System\StorageManager\Profiles\SDMemory]
“Folder”=“Storage Card”
Disk On Chip
[HKLM\System\StorageManager\Profiles\TRUEFFS_DOC]
“Folder”=“DiskOnChip”
[HKLM\System\StorageManager\Profiles\TRUEFFS_DOC]
“Folder”=“DiskOnChip”
During normal Windows Mobile system startup, there are Intermec-spe-
cific and non-Intermec components that require an orderly start to properly
function. These non-Intermec components may also need to start them-
selves so the Windows Mobile device can function properly. Since there are
possible configurations that come from using one or more optional built-in
peripheral devices, the platform components starting on the next page are
required to manage startup.
cific and non-Intermec components that require an orderly start to properly
function. These non-Intermec components may also need to start them-
selves so the Windows Mobile device can function properly. Since there are
possible configurations that come from using one or more optional built-in
peripheral devices, the platform components starting on the next page are
required to manage startup.
PreShell
PreShell (PRESHELL.EXE) is launched prior to the Microsoft Shell and
must execute a SignalStartup call before the Microsoft Shell launches.
must execute a SignalStartup call before the Microsoft Shell launches.
PreShell searches the “\Flash File Store\SYSTEM” directory for an execut-
able of the same name. If one exists, that application is launched. This
application can do what a customer desires prior to launching the Microsoft
Shell. This feature allows end customers to make their own application the
shell of the system. If desired, do not exit the custom shell nor call Signal-
Started.
able of the same name. If one exists, that application is launched. This
application can do what a customer desires prior to launching the Microsoft
Shell. This feature allows end customers to make their own application the
shell of the system. If desired, do not exit the custom shell nor call Signal-
Started.
PostShell
PostShell (POSTSHELL.EXE) can launch an application after the
Microsoft Shell has launched. There are utility applications that exist that
can take advantage of “hooking” the startup for maintenance, for example.
Microsoft Shell has launched. There are utility applications that exist that
can take advantage of “hooking” the startup for maintenance, for example.
Note: This describes the system component startup for Intermec provided
components only. It does not describe the bootstrap loader process. It only
describes the component installation process provided by Windows Mobile.
It is assumed that you understand the Microsoft Mobile startup procedures
and are familiar with how Microsoft components start up.
components only. It does not describe the bootstrap loader process. It only
describes the component installation process provided by Windows Mobile.
It is assumed that you understand the Microsoft Mobile startup procedures
and are familiar with how Microsoft components start up.