It's good that you are testing the return values of each call, and dying when a critical error occurs is generally a good idea. But in this case you don't want to actually die, as this also prints to STDERR - you just want to exit. For example, 
eval {
    copy($fileOne,$fileTwo) or die "Failed to copy $fileOne to $fileTw
+o - $!";
};
if ($@) {
    # Record the log information in here
    exit 1;
}

[download]
My personal preference when developing on windows nt/xp systems is to use the event log instead of a log file. I have had good luck with Win32::EventLog::Carp.

In reply to Re: Error output to screen by imp
in thread Error output to screen by Anonymous Monk

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.