An updated version of the AutoLaunch for Compact 7 component (v300) is released on Codeplex today.
http://autolaunch4ce.codeplex.com/
In this updated version, the following two sub-components are added:
When the Autolaunch CoreCon sub-component is added to an OS design project, it includes the build script to copy CoreCon files to the build release directory, BIB file entries to include the CoreCon files to the runtime image and registry entries to launch CoreCon during startup.
The Autolaunch CoreCon sub-component copy files from the following folder to the build release directory:
\Program Files\Common Files\Microsoft shared\CoreCon\1.0\Target\WCE400\<target CPU>
If you are working on a development machine with 64-Bit OS, the files are from the following folder:
\Program Files (x86)\Common Files\Microsoft shared\CoreCon\1.0\Target\WCE400\<target CPU>
To include the CoreCon files to the runtime image, it adds BIB file entries to the OS design.
To automatically launch CoreCon during startup, it adds the following registry entries to the OS design:
[HKEY_LOCAL_MACHINE\Init]
"Depend99"=hex:14,00,1e,00,32,00
"Launch99"="AutoLaunch.exe"
[HKEY_LOCAL_MACHINE\System]
"CoreConOverrideSecurity"=dword:1
[HKEY_LOCAL_MACHINE\Startup]
"Process0"="ConmanClient2.exe"
"Process0Delay"=dword:00001388
The CoreConOverrideSecurity entry display the system security to enable the Visual Studio development workstation to establish CoreCon connection to the Compact 7 device.
Note: It’s strongly recommended that you DO NOT include the CoreCon component as part of the runtime image for distribution to the end user.
When the "Autolaunch Remote Display application" sub-component is included to an OS design, it set the SYSGEN_CERDISP variable to include the Remote Display application (CERDISP.EXE) to the OS and registry entries to launch the Remote Display application during startup.
To automatically launch the Remote Display application during startup, it includes the following registry entries to the OS design:
"Process1"="cerdisp -c"
"Process1Delay"=dword:00002710
To launch application during startup, you need the following:
· Include the application executable to the Compact 7 OS runtime image. Or place the application in a storage location accessible by the Compact 7 device during startup.
· Add the following registry entries to the OS design project’s OSDESIGN.REG registry file:
"Process2"="MyApp1.exe"
"Process2Delay"=dword:00002710
· To launch additional application, add the following:
"Process3"="MyApp2.exe"
"Process3Delay"=dword:00002710
The process delay entry is the delay time in HEX, in milliseconds, the Autolaunch utility wait prior to launching the associated application.
2710 in HEX is equal to 10000 in Decimal, which is 10000 msec or 10 seconds.
The delay time provides control to launch multiple applications in a designated sequence.
View this page in another language: