Hey Ben!   
      
   If the perl command didn't work as I previously posted try this   
   instead;   
      
     perl -e "print \"Please do not adjust your set.\n\""   
      
   I read somewhere that DOS-think perls have issues with single quotes.   
   Note the internallized double quotes are escaped so that perl doesn't   
   confuse them with the double quotes that enclose the command farmed out   
   to perl from the bash prompt.  Let me know which one works, if either.   
   Also there might be the path issue outstanding.  I've seen a few   
   examples in Windows perl script that require the entire path such as;   
      
     c:\wherever\bin\perl.exe   
      
   but I think that might be an older issue with ActiveState Perl and   
   not the cygwin one.  However it looks like the more Unixie bash single   
   quotes for the command to be farmed out with internal unescaped double   
   quotes within the command may not work.  In an actual Linux enviroment   
   either/or will work as shown below;   
      
   ----- ye ol gpm cut n' paste starts   
   maurice@xena [ ~ ]$ perl -e "print \"Please do not adjust your   
   set.\n\""   
   Please do not adjust your set.   
   maurice@xena [ ~ ]$ perl -e 'print "Please do not adjust your set.\n"'   
   Please do not adjust your set.   
   ----- ye ol gpm cut n' paste ends   
      
   Neat eh?  Let me know what works there and I will act accordingly.   
      
   Life is good,   
   Maurice   
      
   --- GNU bash, version 4.2.10(2)-release (x86_64-atom-linux-gnu)   
    * Origin: Pointy Stick Society (1:261/38.9)