Application run time environment, Path, Launching applications at start-up – Rockwell Automation 6182 SDK User Manual
Page 27
![background image](/manuals/580154/27/background.png)
Introduction to the RAC6182
1–21
Publication 6182-UM002B-EN-P
In the Windows Explorer, the PCMCIA Memory Card will show up as an
icon named “\Storage Card2”.
Application Run Time Environment
Path
The notion of a path to executable files is much the same as with any
other Windows or DOS system. However, unlike other systems, which
refer to an environment variable for path settings, Windows CE utilizes a
registry entry. Thus, the path can be set only by editing the value of the
registry key \HKLM\Loader\SystemPath. Note the use of spaces to
separate items in the path list, as in the following example:
“\storage card\bin\ \storage card\ \ storage card2\bin\ \storage card2\ . . .”
Launching Applications At Start-Up
The Widows CE Registry entries at key HKLM\init determine the
programs that are started during system initialization, and the order in
which they are started. The Windows CE Platform Builder development
tool (not part of the Windows CE Toolkits for Visual C++ 6.0 and Visual
Basic 6.0) is used to establish these Registry entries.
Table G
RAC6182 Launch Order
Sequence
Program or File
Description
Launch10
shell.exe
Start the shell
Launch20
device.exe
Load and start the device drivers
Launch30
postdevice.exe
Start post device driver processing . . .
Depend30
14 00
when device.exe signals complete
Launch40
gwes.exe
Start graphics and events subsystems .
. .
Depend40
1e 00
when postdevice.exe signals complete
Launch50
explorer.exe
Start Windows Explorer . . .
Depend50
14 00 28 00
when device.exe and gwes.exe
complete startup
Launch90
(an OEM executable)
Start OEM executable…
Depend90
1e 00 28 00
when postdevice.exe and gwes.exe
complete startup
Launch90 provides a launch point at startup for an OEM that assures that
the device drivers, TCP/IP, registry and GUI functions are up and
running.
Explorer is launched during initialization because it handles the GUI
shell, taskbar, running items in \windows\startup, etc. Unlike other
executable files, Windows Explorer does not properly signal that it has