For Citrus Perl, but won't interfere with DWIM Perl?

Why would it do that?

You said Remove Citrus Perl from the path and use bin/citrusterm.bat to open a terminal.

Citrusterm doesn't interfere with citrusperl :)

dwimperl, which is just a build of strawberryperl, adds strawberry perl to path

citrusterm opens up cmd.exe, and calls citrusvars, which adds citrus FIRST in path

strawberryperl should no longer interfere

Although I always patch and rereun pl2bat for safety, see Fix_pl2bat

Yes, I understant that Citrus Perl would work properly, even if left in the PATH, thanks to citrusvars.bat. My question was if DWIM Perl would still work, if both are left in the PATH.

Yes, I understant that Citrus Perl would work properly, even if left in the PATH, thanks to citrusvars.bat. My question was if DWIM Perl would still work, if both are left in the PATH.

Sure it was not :)

DWIM perl will still work, but it won't get called when you type perl.exe -V from the current session, because citrus is first in path

all citrusterm/citrusvars is for current session only

Now if you call explicitly absolutedwimperlpath\cpan.bat , it won't call the dwimperlcpan because default pl2bat uses first perl in path ....

Not sure that this has much to do with OPs situation

stefbv: DWIMPerl is not in the PATH (although a DWIMPerl installation exists on the machine).
Like I said in the OP, I went religiously through the Citrus Perl installation steps, including citrusvars.bat.

Here is the current PATH (newlines inserted for readability):

Read more... (997 Bytes)

It refers to Citrus Perl only.
It seems like somehow CPANPLUS decided to locate its extraction top directory (tree-top) (for all Perl versions) below the DWIMPerl top directory.

But that is not supposed to influence installing modules.