Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SOS on TaskMan Shell in WindowsCE 5.0

2 views
Skip to first unread message

Arthur Jiang

unread,
Jan 24, 2005, 8:59:50 PM1/24/05
to
Dear Experts,

How to include the taskman shell in WindowsCE 5.0?

In WindowsCE 4.2, I can set the environment variable "__SYSGEN_TASKMAN"
to 1 to include the taskman shell environment, but the same way doesn't work
in WindowsCE 5.0.

According to MSDN documents on how to custimize shell, I have tried the
following way to include taskman shell in WindowsCE 5.0,but failed.
1) Copy the files and directories in
%_WINCEROOT%\PUBLIC\WCESHELLFE\OAK\TASKMAN to
%_WINCEROOT%\PUBLIC\Shell\OAK\TASKMAN
2) Replace the existing codes in the dirs file with DIRS=TASKMAN
3) Assign the variable BUILD_OPTIONS to TASKMAN
4) Add following codes in project.reg
[HKEY_LOCAL_MACHINE\init]
"Launch50"="taskman.exe"
"Depend50"=hex:14,00, 1e,00
5) Mask the sentence "INCLUDES=..\stubs" with comment in
%_WINCEROOT%\PUBLIC\Shell\OAK\TASKMAN\sources file. Otherwise, it cannot be
compiled successfully.
As a result, this platform can be built successfully. But there're black
screen when the platform is attached.

Could you give me some advice?

Thanks & Best Regards,

Arthur


mobilevil

unread,
Jan 24, 2005, 9:11:39 PM1/24/05
to
in my case device.exe was stuck with one of the driver so GWES, explorer.exe
didn't get loaded.
I had to new a platform project without any network support to get anyway
show in my device.
or, use ce target control,
s gwes
press Y
s explorer
to force it boot. i still didn't fix the device.exe problem but i think it
will be fixed as I move on work on the other drivers.
"Arthur Jiang" <Arthur...@wadin.com> wrote in message
news:e%23J5MGoA...@TK2MSFTNGP14.phx.gbl...

Yannick Chamming's [eMVP]

unread,
Jan 25, 2005, 2:21:50 AM1/25/05
to
Here is what I'd rather do:

- copy taskman directory from Public to Platform\mybsp
- change sources file so that it would generate an exe but not a lib (it
will imply adding some targetlibs entries, as you'll have to handle
unresolved external)
- have taskman.exe built succesfully
- add taskman.exe to your bib file, and modify reg file so that it is
"Launch50" (as you've already done)

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADESET
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"Arthur Jiang" <Arthur...@wadin.com> wrote in message

news:e#J5MGoAF...@TK2MSFTNGP14.phx.gbl...

dongweilong

unread,
Jan 25, 2005, 6:21:31 AM1/25/05
to
Dear Friends,

Maybe we can try these:

- Delete Standard Shell from your project Catalog items

- Set the environment variable "SYSGEN_TASKMAN" to 1

- In %_WINCEROOT%\PUBLIC\CEBASE\OAK\MISC\wceshellfe.bat add:
if not "%SYSGEN_TASKMAN%"=="1" goto noTaskMan
set WCESHELLFE_MODULES=%WCESHELLFE% taskman
:noTaskMan

- Build TaskMan to generate a lib

- Sysgen

That's OK! :->

DongWeilong
2005.1.25

"Arthur Jiang" <Arthur...@wadin.com> wrote in message
news:e#J5MGoAF...@TK2MSFTNGP14.phx.gbl...

0 new messages