If you are new to Perl, do yourself a favor and always enable warnings and strictures at the start of your code, then do youself another favor and use diagnostics:
    use warnings;
    use strict;
    use diagnostics;

>perl -le "use warnings; use strict; my $s = \"c:\myfolder\my.bat\"; print qq{'$s'}; " Unrecognized escape \m passed through at -e line 1. Unrecognized escape \m passed through at -e line 1. 'c:myfoldermy.bat' >perl -le "use warnings; use strict; use diagnostics; my $s = \"c:\myfolder\my.bat\"; print qq{'$s'}; " Unrecognized escape \m passed through at -e line 1 (#1) (W misc) You used a backslash-character combination which is not recognized by Perl. The character was understood literally, but t +his may change in a future version of Perl. 'c:myfoldermy.bat'

In reply to Re: why isn't bat file getting called? by AnomalousMonk
in thread why isn't bat file getting called? by TourneyOfPerl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.