Issue with Feature Pack2007

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hallo,

I have an XPe SP2 configuration with a custom shell. I can build the target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following error:

Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"

The ExplorerShell is just a relict, because I used it before my own shell.
So I deleted the Explorer Shell. But after F5 it is pulled in automatically
because:

Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]", origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"

Ok, I tried to delete "Text Services Framework" but after F5 the same:

Adding component: "Text Services Framework [Version 5.1.2600.3333, R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"

So, what am I doing wrong? How can I get rid off "Explorer Shell" or can it
be coexistence with "MyCustomShell" as before without Feature Pack 2007?

Any hints are welcome
Klaus
 
Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.

Auf Wiedersehen,
~ Jodie
 
Dear Jodie,

thank you for your quick answer. I've disabled the Explorer Shell and
enabled my Shell just before building the image and then skipped the
dependencie check and it worked. So far it's a good workaround.
But I have explored the things a little more and found, that according to
component help not only "Keyboard German" has dependency on "Text Services
Framework", but also the "Keyboard: United States - International" and many
others. The only one I found, which has no dependencies is "Keyboard: United
States English". And the "Text Services Framework" seems to have a dependency
on "Explorer Shell", also it is not explicitly listed in component help. So
when I'm right this issue should appear by nearly everybody, who has a custom
shell and FP2007. It should then result in a conflict between Explorer Shell
and custom shell. So if there is anybody who has a custom shell with FP2007
and doesn't experience this issue, please tell me. Perhaps we can find out,
what you've done right and I've done wrong.

Klaus


MrJodie said:
Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.

Auf Wiedersehen,
~ Jodie

Hallo,

I have an XPe SP2 configuration with a custom shell. I can build the target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following error:

Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"

The ExplorerShell is just a relict, because I used it before my own shell.
So I deleted the Explorer Shell. But after F5 it is pulled in automatically
because:

Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]", origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"

Ok, I tried to delete "Text Services Framework" but after F5 the same:

Adding component: "Text Services Framework [Version 5.1.2600.3333, R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"

So, what am I doing wrong? How can I get rid off "Explorer Shell" or can it
be coexistence with "MyCustomShell" as before without Feature Pack 2007?

Any hints are welcome
Klaus
Click to expand...
Click to expand...
 
Klaus,

I have a custom shell component and no Explorer, but I'm using a US English
keyboard, and that apparently does not require the "Text Services Framework"
dependency.

I don't think you've done anything "wrong" except use the wrong language :).

Regards,
Dean


Klaus said:
Dear Jodie,

thank you for your quick answer. I've disabled the Explorer Shell and
enabled my Shell just before building the image and then skipped the
dependencie check and it worked. So far it's a good workaround.
But I have explored the things a little more and found, that according to
component help not only "Keyboard German" has dependency on "Text Services
Framework", but also the "Keyboard: United States - International" and
many
others. The only one I found, which has no dependencies is "Keyboard:
United
States English". And the "Text Services Framework" seems to have a
dependency
on "Explorer Shell", also it is not explicitly listed in component help.
So
when I'm right this issue should appear by nearly everybody, who has a
custom
shell and FP2007. It should then result in a conflict between Explorer
Shell
and custom shell. So if there is anybody who has a custom shell with
FP2007
and doesn't experience this issue, please tell me. Perhaps we can find
out,
what you've done right and I've done wrong.

Klaus


MrJodie said:
Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.

Auf Wiedersehen,
~ Jodie

Hallo,

I have an XPe SP2 configuration with a custom shell. I can build the
target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following
error:

Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"

The ExplorerShell is just a relict, because I used it before my own
shell.
So I deleted the Explorer Shell. But after F5 it is pulled in
automatically
because:

Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]",
origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"

Ok, I tried to delete "Text Services Framework" but after F5 the same:

Adding component: "Text Services Framework [Version 5.1.2600.3333,
R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"

So, what am I doing wrong? How can I get rid off "Explorer Shell" or
can it
be coexistence with "MyCustomShell" as before without Feature Pack
2007?

Any hints are welcome
Klaus
Click to expand...
Click to expand...
Click to expand...
 
Hi Dean,

yes probably I use the wrong language or better the wrong keyboard ;-)
But then there should be many others, like me, who got this error message
"Multiple active components collision" between two shells. Well I fear, that
I have to accept this little curiosity without ever learning what really the
cause is, unless some expert from MS can shine a light on this nebulous
behaviour? My idea is, that there should be a way to brake the dependency
from "Text Services Framework" to "Explorer Shell". I've tried this by
disabling some "Settings" from this component, which seems to relate to the
Explorer Shell (e.g. "Language bar setting on the desktop" = Hidden), but
unfortunately this doesn't help. Perhaps someone has another (better) idea?

Klaus


DPM said:
Klaus,

I have a custom shell component and no Explorer, but I'm using a US English
keyboard, and that apparently does not require the "Text Services Framework"
dependency.

I don't think you've done anything "wrong" except use the wrong language :).

Regards,
Dean


Klaus said:
Dear Jodie,

thank you for your quick answer. I've disabled the Explorer Shell and
enabled my Shell just before building the image and then skipped the
dependencie check and it worked. So far it's a good workaround.
But I have explored the things a little more and found, that according to
component help not only "Keyboard German" has dependency on "Text Services
Framework", but also the "Keyboard: United States - International" and
many
others. The only one I found, which has no dependencies is "Keyboard:
United
States English". And the "Text Services Framework" seems to have a
dependency
on "Explorer Shell", also it is not explicitly listed in component help.
So
when I'm right this issue should appear by nearly everybody, who has a
custom
shell and FP2007. It should then result in a conflict between Explorer
Shell
and custom shell. So if there is anybody who has a custom shell with
FP2007
and doesn't experience this issue, please tell me. Perhaps we can find
out,
what you've done right and I've done wrong.

Klaus


MrJodie said:
Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.

Auf Wiedersehen,
~ Jodie

Hallo,

I have an XPe SP2 configuration with a custom shell. I can build the
target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following
error:

Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"

The ExplorerShell is just a relict, because I used it before my own
shell.
So I deleted the Explorer Shell. But after F5 it is pulled in
automatically
because:

Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]",
origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"

Ok, I tried to delete "Text Services Framework" but after F5 the same:

Adding component: "Text Services Framework [Version 5.1.2600.3333,
R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"

So, what am I doing wrong? How can I get rid off "Explorer Shell" or
can it
be coexistence with "MyCustomShell" as before without Feature Pack
2007?

Any hints are welcome
Klaus
Click to expand...
Click to expand...
Click to expand...
 
Just to confirm. The dependency on the "Explorer Shell" was added to the "Text Services Framework" component only in FP2007 indeed.

IIRC, Text Services Framework only works properly with Winlogon. Not sure why it should depend on the Explorer shell though.
Klaus, maybe you just want to ignore that dependency check (turn the auto-dependency resolver off) and don't include the Explorer
shell at all. Obviously, you'd need to test your runtime for the IME carefully.

--
=========
Regards,
KM
Hi Dean,

yes probably I use the wrong language or better the wrong keyboard ;-)
But then there should be many others, like me, who got this error message
"Multiple active components collision" between two shells. Well I fear, that
I have to accept this little curiosity without ever learning what really the
cause is, unless some expert from MS can shine a light on this nebulous
behaviour? My idea is, that there should be a way to brake the dependency
from "Text Services Framework" to "Explorer Shell". I've tried this by
disabling some "Settings" from this component, which seems to relate to the
Explorer Shell (e.g. "Language bar setting on the desktop" = Hidden), but
unfortunately this doesn't help. Perhaps someone has another (better) idea?

Klaus


DPM said:
Klaus,

I have a custom shell component and no Explorer, but I'm using a US English
keyboard, and that apparently does not require the "Text Services Framework"
dependency.

I don't think you've done anything "wrong" except use the wrong language :).

Regards,
Dean


Klaus said:
Dear Jodie,

thank you for your quick answer. I've disabled the Explorer Shell and
enabled my Shell just before building the image and then skipped the
dependencie check and it worked. So far it's a good workaround.
But I have explored the things a little more and found, that according to
component help not only "Keyboard German" has dependency on "Text Services
Framework", but also the "Keyboard: United States - International" and
many
others. The only one I found, which has no dependencies is "Keyboard:
United
States English". And the "Text Services Framework" seems to have a
dependency
on "Explorer Shell", also it is not explicitly listed in component help.
So
when I'm right this issue should appear by nearly everybody, who has a
custom
shell and FP2007. It should then result in a conflict between Explorer
Shell
and custom shell. So if there is anybody who has a custom shell with
FP2007
and doesn't experience this issue, please tell me. Perhaps we can find
out,
what you've done right and I've done wrong.

Klaus


:

Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.

Auf Wiedersehen,
~ Jodie

Hallo,

I have an XPe SP2 configuration with a custom shell. I can build the
target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following
error:

Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"

The ExplorerShell is just a relict, because I used it before my own
shell.
So I deleted the Explorer Shell. But after F5 it is pulled in
automatically
because:

Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]",
origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"

Ok, I tried to delete "Text Services Framework" but after F5 the same:

Adding component: "Text Services Framework [Version 5.1.2600.3333,
R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"

So, what am I doing wrong? How can I get rid off "Explorer Shell" or
can it
be coexistence with "MyCustomShell" as before without Feature Pack
2007?

Any hints are welcome
Klaus
Click to expand...
Click to expand...
Click to expand...
 
Hallo KM,

ok - meantime I realize, that it is the best way, to simply ignore the
dependency check and either disable auto-resolver and remove Explorer Shell
or switch between the 2 shells by enabling only one of them as Jodie says.

Thanks to all of you for your help and excuse me for my poor English. For me
it's not the first time I found assistance here. So I think this is really a
great newsgroup.
Have a nice day,
Klaus


KM said:
Just to confirm. The dependency on the "Explorer Shell" was added to the "Text Services Framework" component only in FP2007 indeed.

IIRC, Text Services Framework only works properly with Winlogon. Not sure why it should depend on the Explorer shell though.
Klaus, maybe you just want to ignore that dependency check (turn the auto-dependency resolver off) and don't include the Explorer
shell at all. Obviously, you'd need to test your runtime for the IME carefully.

--
=========
Regards,
KM
Hi Dean,

yes probably I use the wrong language or better the wrong keyboard ;-)
But then there should be many others, like me, who got this error message
"Multiple active components collision" between two shells. Well I fear, that
I have to accept this little curiosity without ever learning what really the
cause is, unless some expert from MS can shine a light on this nebulous
behaviour? My idea is, that there should be a way to brake the dependency
from "Text Services Framework" to "Explorer Shell". I've tried this by
disabling some "Settings" from this component, which seems to relate to the
Explorer Shell (e.g. "Language bar setting on the desktop" = Hidden), but
unfortunately this doesn't help. Perhaps someone has another (better) idea?

Klaus


DPM said:
Klaus,

I have a custom shell component and no Explorer, but I'm using a US English
keyboard, and that apparently does not require the "Text Services Framework"
dependency.

I don't think you've done anything "wrong" except use the wrong language :).

Regards,
Dean


Dear Jodie,

thank you for your quick answer. I've disabled the Explorer Shell and
enabled my Shell just before building the image and then skipped the
dependencie check and it worked. So far it's a good workaround.
But I have explored the things a little more and found, that according to
component help not only "Keyboard German" has dependency on "Text Services
Framework", but also the "Keyboard: United States - International" and
many
others. The only one I found, which has no dependencies is "Keyboard:
United
States English". And the "Text Services Framework" seems to have a
dependency
on "Explorer Shell", also it is not explicitly listed in component help.
So
when I'm right this issue should appear by nearly everybody, who has a
custom
shell and FP2007. It should then result in a conflict between Explorer
Shell
and custom shell. So if there is anybody who has a custom shell with
FP2007
and doesn't experience this issue, please tell me. Perhaps we can find
out,
what you've done right and I've done wrong.

Klaus


:

Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.

Auf Wiedersehen,
~ Jodie

Hallo,

I have an XPe SP2 configuration with a custom shell. I can build the
target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following
error:

Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"

The ExplorerShell is just a relict, because I used it before my own
shell.
So I deleted the Explorer Shell. But after F5 it is pulled in
automatically
because:

Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]",
origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"

Ok, I tried to delete "Text Services Framework" but after F5 the same:

Adding component: "Text Services Framework [Version 5.1.2600.3333,
R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"

So, what am I doing wrong? How can I get rid off "Explorer Shell" or
can it
be coexistence with "MyCustomShell" as before without Feature Pack
2007?

Any hints are welcome
Klaus
Click to expand...
Click to expand...
Click to expand...
 
Hallo KM,

ok - meantime I realize, that it is the best way, to simply ignore the
dependency check and either disable auto-resolver and remove Explorer Shell
or switch between the 2 shells by enabling only one of them as Jodie says.

Thanks to all of you for your help and excuse me for my poor English. Forme
it's not the first time I found assistance here. So I think this is really a
great newsgroup.
Have a nice day,
Klaus



KM said:
Just to confirm. The dependency on the "Explorer Shell" was added to the "Text Services Framework" component only in FP2007 indeed.
Click to expand...
IIRC, Text Services Framework only works properly with Winlogon. Not sure why it should depend on the Explorer shell though.
Klaus, maybe you just want to ignore that dependency check (turn the auto-dependency resolver off) and don't include the Explorer
shell at all. Obviously, you'd need to test your runtime for the IME carefully.
Hi Dean,
yes probably I use the wrong language or better the wrong keyboard ;-)
But then there should be many others, like me, who got this error message
"Multiple active components collision" between two shells. Well I fear, that
I have to accept this little curiosity without ever learning what really the
cause is, unless some expert from MS can shine a light on this nebulous
behaviour? My idea is, that there should be a way to brake the dependency
from "Text Services Framework" to "Explorer Shell". I've tried this by
disabling some "Settings" from this component, which seems to relate to the
Explorer Shell (e.g. "Language bar setting on the desktop" = Hidden), but
unfortunately this doesn't help. Perhaps someone has another (better)idea?
Klaus
:
Klaus,
I have a custom shell component and no Explorer, but I'm using a US English
keyboard, and that apparently does not require the "Text Services Framework"
dependency.
I don't think you've done anything "wrong" except use the wrong language :).
Regards,
Dean
Dear Jodie,
thank you for your quick answer. I've disabled the Explorer Shell and
enabled my Shell just before building the image and then skipped the
dependencie check and it worked. So far it's a good workaround.
But I have explored the things a little more and found, that according to
component help not only "Keyboard German" has dependency on "Text Services
Framework", but also the "Keyboard: United States - International"and
many
others. The only one I found, which has no dependencies is "Keyboard:
United
States English". And the "Text Services Framework" seems to have a
dependency
on "Explorer Shell", also it is not explicitly listed in componenthelp.
So
when I'm right this issue should appear by nearly everybody, who has a
custom
shell and FP2007. It should then result in a conflict between Explorer
Shell
and custom shell. So if there is anybody who has a custom shell with
FP2007
and doesn't experience this issue, please tell me. Perhaps we can find
out,
what you've done right and I've done wrong.
Klaus
:
Klaus, it looks like you've got a real "tangled web" there. That's
the difficulty with many components, the dependencies are progressive
and can lead to components being added and re-added, ad infinitum.. My
recommendation (I'm assuming you need that German Keyboard feature,
which depends on Text Services Framework to display German language
characters and is part of the multi-language user interface (MUI))
would be to simply alt-click (right mouse) on the Explorer Shell and
"disable" and then do the same to "enable" your MyCustomShell, just
before building your image. When prompted to run a dependency check
before building say NO. That will make sure that the dependencies are
in place but will allow you to build with your custom shell in place
and active.
Auf Wiedersehen,
~ Jodie
Hallo,
I have an XPe SP2 configuration with a custom shell. I can build the
target
image without any problems under XPe SP2. Now I have upgrated the hole
configuration to FP2007. After Dependencie check I get the following
error:
Multiple active components collision between: "Explorer shell [Version
5.1.2600.1106, R1507]" and "MyCustomShell"
The ExplorerShell is just a relict, because I used it before myown
shell.
So I deleted the Explorer Shell. But after F5 it is pulled in
automatically
because:
Adding component: "Explorer shell [Version 5.1.2600.1106, R1507]",
origin:
"Text Services Framework [Version 5.1.2600.3333, R3333]"
Ok, I tried to delete "Text Services Framework" but after F5 the same:
Adding component: "Text Services Framework [Version 5.1.2600.3333,
R3333]",
origin: "Keyboard: German [Version 5.1.2600, R620]"
So, what am I doing wrong? How can I get rid off "Explorer Shell" or
can it
be coexistence with "MyCustomShell" as before without Feature Pack
2007?
Any hints are welcome
Klaus- Zitierten Text ausblenden -
Click to expand...
Click to expand...

- Zitierten Text anzeigen -
Click to expand...

Hi Klaus,

I had the same problem. It was the main reason for me to switch back
to SP2. For the future I would be very interested if you encounter any
more problems with FP2007 and your custom shell. It would be very nice
of you to keep me and other people who are affected informed.

Regards,
Susanne Stöhr
 
Hallo Susanne,

nice to hear, that I'm not the only one who experiences exactly this issue.
So it really seems, that there is nothing what I've done wrong. Otherwise we
both did the same thing wrong. All the more I'm a little disappointed, that
nobody "official" from Microsoft has commented on this issue. If this is
really a bug in FP2007 someone should acknowledge this. This would be
helpfull to all, who got this Error message, and could save much time in
searching for "what did I wrong". If this is not a bug, someone should show
us the proper way. But probably I'm completely wrong, hoping that someone
"official" is reading this thread. So I think we are left on our own. I will
further on "trial and error" with FP2007, because I want to use the new FBWF
perhaps with Registry Filter. This could be very usefull for my device. Where
applicable, I will post about other potential issues or success with FP2007.

Best regards,
Klaus


:
 
Back
Top