One of the problems with using STDIN to pause a program is that input is often buffered. Thus you may actually be getting data that was previously entered when you are attempting to pause. You can test this by adding this change to your program:
if ($course eq "ERROR") { 
  print "Fatal Error - see errorLog.txt for details \n" ;    
  print "Hit 'ENTER' to quit\n" ; 
  my $temp = <> ;
  warn "\n**$temp**\n";#show what was read from STDIN
  sleep 5;#give yourself time to see it
}

[download]

If the Win32 package is available and a popup is permissable, try the Win32::MsgBox() function mentioned above as an alternative. It is a better solution to this problem.

In reply to Re^2: dos window by jrsimmon
in thread dos window by cammac

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.