Rockwell Automation 2711P Software Development Kit User Manual User Manual
Page 26
![background image](/manuals/580240/26/background.png)
Publication 2711P-UM005A-EN-P - March 2007
26 Introduction to the PanelView Plus CE Terminal
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 card2\bin\
Launching Applications At Start-Up
The Widows CE Registry entries at key [HKLM]\init determine the
operating system programs that are started during system initialization,
and the order in which they are started. The Windows CE Platform
Builder development tool is used to establish these Registry entries.
PVPStart.exe launches Explorer during initialization, which then
handles the Window GUI, shell, taskbar, and launches the shortcuts in
\windows\startup, etc. Unlike other executable files, Windows
Explorer does not properly signal that it has completed startup, so
dependencies can not be placed directly on Explorer.exe.
Consequently, the start menu, taskbar, etc. may still be drawing when
the content of the \windows\startup folder is executed.
[HKLM]\init should be reserved for the operating system. The Shell
using shortcuts in the \Windows\Startup folder should launch
applications. The folder \windows\startup is RAM based, so its
contents will not persist from one operating session to the next. The
solution is to place shortcuts in \Storage Card\Windows\Startup. In a
normal system initialization sequence, everything in \Storage
Card\Windows\* is copied to \Windows by Postgwes.exe in the
startup order.
This copy operation is not performed when the system is in Safe
Mode.
PanelView Plus CE Operating System Launch Order
Sequence
Program or File
Description
Launch20
device.exe
Load and start the device drivers
Launch30
Depend30
gwes.exe
14 00
Start graphics and events subsystem
…when device.exe is complete
Launch40
Depend40
Postgwes.exe
14 00 1E 00
Copy \Storage Card\Windows\*
…when device.exe and gwes.exe are complete
Launch60
Depend60
Services.exe
14 00
Load and start System Services
…when Device.exe is complete
Launch75
Depend75
PVPIdentify.exe
28 00
Establish Product Identification
…when PostGwes.exe is complete
Launch80
Depend80
hardwareMonitor.exe
28 00
Start Hardware Monitoring
…when PostGwes.exe signals complete
Launch85
Depend85
PVPStart.exe
4B 00
Start Explorer Shell
…when PVPIdentify.exe is complete