Replacing standard shell with taskman
Gary C
I'm trying to include taskman in my build. The first step is to unselect
both the standard shell and the thin client shell in the catalog.
MSDN has a new page from 11/11/2009 that has instructions that don't seem to
work at
http://msdn.microsoft.com/en-us/library/ee502244.aspx
The result was a black screen but none of the keyboard commands worked. I
had done a rebuild solution. Globally searching WINCE600 had no hits for
__SYSGEN_TASKMAN or SYSGEN_TASKMAN except in PBInitEnv.bat. Separately, I
found WCESHELLFE_MODULES_TASKMAN in reginit.ini and ce.bib.
Next, I tried the instructions at
http://msdn.microsoft.com/en-us/library/ee500144.aspx
which are also from 11/11/2009. Basically, I copied the TASKMAN directory
into the SHELL directory and followed the instructions. The only deviation
was the INCLUDES variable in "sources" for TASKMAN needed modification. The
end result after a build is Taskman.exe was in the release directory but was
not rolled into the nk.bin. One could manually add taskman.exe to a bib file
and then add the launch and depend in a reg file.
My question is how do I get taskman.exe to automatically show up in ce.bib?
I have all the pieces here but don't know how they go together.
These files seem relevant (public\cebase\common\oak\misc): wceshellfe.reg,
wceshellfe.bat. And, wceshellfe.bib.
Some other postings of interest are (many were filtered out).
http://www.pocketpcjunkies.com/Uwe/Forum.aspx/wince-pb/6663/Using-taskman-in-CE-5-0
Gary C
1. Uncheck all shells in the catalog (there are 2 for CE 6.0).
2. Make sure the battery driver is selected in the catalog to avoid a link
error.
3. TASKMAN/sources has a "stubs" path in the INCLUDE variable that is giving
a warning. It can optionally be removed.
4. Define SYSGEN_TASKMAN in the OSDesign environment variables.
5. Add the follownig in C:\WINCE600\PUBLIC\CEBASE\OAK\MISC\wceshellfe.bat
if not "%SYSGEN_TASKMAN%"=="1" goto noTaskMan
set WCESHELLFE_MODULES=%WCESHELLFE_MODULES% taskman
:noTaskMan
One of the links in my original post has the following on the right side of
the equals:
=%WCESHELLFE% taskman
If the lines are near the end of the wceshellfe.bat, then the
WCESHELLFE_MODULE variable will be wiped out and set equal to only taskman.
It seems that link has a typo because one of the other links has it the same
way that I have it above.
As an aside, the "dirs" file above the TASKMAN directory doesn't have the
line DIRS=taskman which makes one wonder how taskman is built. Apparently,
the PUBLIC directory is built differently using _DEPTREES in wince.bat.
Also, it seems the contents of WCESHELLFE_MODULES gets turned into the
sysgen variable @WCESHELLFE_MODULES_TASKMAN which is used for filtering.
Ditto for all the other strings in the WCESHELLFE_MODULES variable. Perhaps
one of the experts monitoring this group could elaborate.
"Gary C" <ga...@globaldialog.com> wrote in message
news:ek0zttva...@TK2MSFTNGP05.phx.gbl...
cjay
projects you work on from using the taskman shell. Good advice is never
change anything in PUBLIC:
[HKEY_LOCAL_MACHINE\init]
"Launch50"="taskman.exe"
"Depend50"=hex:14,00, 1e,00
Normally this is set to the following, but the platform.reg will override
this:
[HKEY_LOCAL_MACHINE\init]
"Launch50"="explorer.exe"
"Depend50"=hex:14,00, 1e,00
CJ
"Gary C" wrote:
> .
>
Gary C
the catalog? It seems people clone the explorer shell and strip it down to
accomplish similar goals.
"cjay" <cj...@discussions.microsoft.com> wrote in message
news:556ACA97-CC75-4F2E...@microsoft.com...