Launching ncpa.cpl with custom shell

[aflynt]

Having read through some past posts on this subject, my impression is
that the ncpa.cpl (network connections control panel) cannot be
launched independently if you are using a custom shell. You can launch
it by double clicking the "Network Connections" icon from the control
panel, but opening it from code or the command line with "control.exe
ncpa.cpl" will not work.

Before I go crazy and recreate the entire Network Connections UI with
C# and WMI I just want to make absolutely sure that my assumption is
correct, and this is still not possible.

-=Aaron=-

 

[KM]

Just wanted to mention that "control.exe ncpa.cpl" works fine for me here on some XPe images.
If it doesn't work for you I'd think you are missing out some components from the image.

 

[aflynt]

After much searching, and experimenting with adding various
components, I've given up on directly running this control panel
applet. I have, however, found a workaround that accomplishes exactly
the same thing.

In case anybody else runs into this issue, the fix is to run the
following command instead of "control.exe ncpa.cpl":

explorer ::{7007ACC7-3202-11D1-AAD2-00805FC1270E}

This just launches explorer.exe passing the GUID of the Network
Connections special folder.

 

[KM]

Nice workaround!

Just for the sake of experimenting, do you happen to have Netshell component in your image? If you don't , that might be the reason
for that command line not to work.

--
=========
Regards,
KM


After much searching, and experimenting with adding various
components, I've given up on directly running this control panel
applet. I have, however, found a workaround that accomplishes exactly
the same thing.

In case anybody else runs into this issue, the fix is to run the
following command instead of "control.exe ncpa.cpl":

explorer ::{7007ACC7-3202-11D1-AAD2-00805FC1270E}

This just launches explorer.exe passing the GUID of the Network
Connections special folder.

 

[aflynt]

Netshell is there. I tried a whole bunch of stuff suggested in related
topics from this newsgroup, and nothing worked. It always came back
with a 'null' error message and a blank explorer dialog. The
workaround posted works perfectly, though.