I expect the reason that the open(INDIR, $indir) part breaks is that, binmode() having been called on STDIN, $indir ends with a carriage return. 

my $indir = <STDIN>;   # $indir = "directory\r\n";
                       # binmode stops the \r\n -> \n translation
chomp $indir;          # chomp removes $/, which is "\n"
                       # the \r is left intact

[download]
A quick fix in your script is to make sure the \r is removed as well.

The ideal fix is for CGI not to call binmode() on STDIN when the script is run interactively.

In reply to Re: Win32 CGI breaks STDIN? by chipmunk
in thread Win32 CGI breaks STDIN? by the_slycer

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.