Shell customization problem

[nirajembedded]

Hi,
I have followed these msdn articles
1)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpeh...
2).http://blogs.msdn.com/mikehall/archive/2006/05/29/609857.aspx
for my shell customization.
I am confused about the location of the application specified in the
component designer using
cmiShellpath variable which is set to %systemroot%system32/xx.exe.
I have created a folder pathed at c:\MFCshell and put my application
and it's support dlls in to it. Now when and where I should locate this
folder in the image created so that it should appear as a shell.
Otherwise I am getting blue screen having windowsXP written in the
bottom right corner and nothing is done.
Can Anybody shade some light on it...?
Thanx
Niraj

 

[Lucvdv]

Hi,
I have followed these msdn articles
1)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpeh...
2).http://blogs.msdn.com/mikehall/archive/2006/05/29/609857.aspx
for my shell customization.
I am confused about the location of the application specified in the
component designer using
cmiShellpath variable which is set to %systemroot%system32/xx.exe.
I have created a folder pathed at c:\MFCshell and put my application
and it's support dlls in to it. Now when and where I should locate this
folder in the image created so that it should appear as a shell.
Otherwise I am getting blue screen having windowsXP written in the
bottom right corner and nothing is done.
Can Anybody shade some light on it...?
Thanx
Niraj

Your own shell is named xx.exe?

Either put it with its support dll's in the system32 directory, or change
cmiShellPath to point to where it is really installed.

i.e. cmiShellPath = C:\MFCshell\xx.exe should do it.

 

[nirajembedded]

Thanks a lot.
I did the same changes you have suggested. but problem remains same.
I have developed a demo application using MFC8.0.
I have changed my cmiShellpath with %systemroot%system32/xx.exe
and after building image i copied my xx.exe to that location and all
it's dependencies shows in the dependency walker.
I have also place all the .manifest file list in the msdn artical by
mikehall.
but the problem remains same..
Again expecting your response..
Thanks again.
Niraj

 

[Lucvdv]

Thanks a lot.
I did the same changes you have suggested. but problem remains same.
I have developed a demo application using MFC8.0.
I have changed my cmiShellpath with %systemroot%system32/xx.exe
and after building image i copied my xx.exe to that location and all
it's dependencies shows in the dependency walker.
I have also place all the .manifest file list in the msdn artical by
mikehall.
but the problem remains same..
Again expecting your response..
Thanks again.
Niraj

Does your app run OK on the target when you start it manually from a cmd
shell?



Sometimes applications seem to refuse to work if they are started as shell
(I've seen it with DirectX, but I've read about it in this group for other
apps too). Just adding a delay at startup, before they try to access the
display, usually fixes it.

On one target I changed my app so it keeps retrying to initialize Direct3D
with 15 second pauses between attempts, until it succeeds. It doesn't find
any display at first, but at the 2nd or 3rd attempt it suddenly starts
working.

 

[nirajembedded]

Hi,
Thanks a lot.
My problem is solved now.
There was some silly mistake in component creation.

Thanks again,