PPM Controls Command Window

n6532l has asked for the wisdom of the Perl Monks concerning the following question:

I ran PERL PPM to add a package. It issued a warning about the package I selected would interfere with another package. I exited the program and shutdown my computer. Next time I booted up and selected a command window (windows xp) it started PPM. PPM has taken over my command window and I can do nothing else in the command window. Ready to remove and re-install PERL unless I can get another solution.

Comment on PPM Controls Command Window

Replies are listed 'Best First'.
Re: PPM Controls Command Window by ww (Archbishop) on Nov 09, 2014 at 18:15 UTC
Not really enough information to understand what happened... and your description does not compute (for /me anyway) unless you have a script named PPM.pl because otherwise Perl should complain "script not found." If you're running Active State's Perl 5.nn and trying to find or install modules from a repository, you must run the `ppm` batch file from the command prompt (or maybe you can do so from the windows GUI?) BUT definitely not as if it were a Perl script. As to a cure: find `ppm.bat`; rename it to something like `ppm.bat.hold`; and open a cmd window and see what happens. If all is well again at that point (and your computer does not belch blue flames) try renaming `ppm.bat.hold` back to its original form. Then open cmd again... to see if it's still behaving. BTW, if para 2's "(i)f" clause is true, and para 3 doesn't work, you have problems that are unlikely to be resolved by removing and re-installing Perl (which, BTW to the preceding BTW, is written lower case or with an initial cap, depending on your meaning, but not all uc). *Questions containing the words "doesn't work" (or their moral equivalent) will usually get a downvote from me unless accompanied by:* code verbatim error and/or warning messages *a coherent explanation of what "doesn't work" actually means.*	[reply] [d/l]

Replies are listed 'Best First'.

Re: PPM Controls Command Window
by ww (Archbishop) on Nov 09, 2014 at 18:15 UTC

Not really enough information to understand what happened... and your description does not compute (for /me anyway) unless you have a script named PPM.pl because otherwise Perl should complain "script not found."

If you're running Active State's Perl 5.nn and trying to find or install modules from a repository, you must run the ppm batch file from the command prompt (or maybe you can do so from the windows GUI?) BUT definitely not as if it were a Perl script.

As to a cure: find ppm.bat; rename it to something like ppm.bat.hold; and open a cmd window and see what happens. If all is well again at that point (and your computer does not belch blue flames) try renaming ppm.bat.hold back to its original form. Then open cmd again... to see if it's still behaving.

BTW, if para 2's "(i)f" clause is true, and para 3 doesn't work, you have problems that are unlikely to be resolved by removing and re-installing Perl (which, BTW to the preceding BTW, is written lower case or with an initial cap, depending on your meaning, but not all uc).

Questions containing the words "doesn't work" (or their moral equivalent) will usually get a downvote from me unless accompanied by:

code
verbatim error and/or warning messages
a coherent explanation of what "doesn't work" actually means.

[reply]
[d/l]