>My only thought offhand is that newlines might be messed up. - Chris Chris is absolutely right! I was fooled by the fact that M$Word on the PeeCee opened the transmitted x.pl file just fine. Apparently that piece of software recognizes the Mac return convention and doesn't bother to say anything about it. Doing a "save as" from Word on the PeeCee allowed the script to execute. Also: I had placed a test for the "MacOS" in my script and changed to "\r\n" for the line terminator in my output files. That's wrong. Apparently perl on the PeeCee puts out the right thing when you simply specify \n. That means \n is the right terminator to use for output for all three systems. Just why the perl parser doesn't recognize all three, as does M$Word, is a mystery beyond my simple mind. The right book is "Learning Perl on Win32 Systems" by Randal L. Schwartz and others published by - you guessed it - O'Reilly. Not quite MPP&E but still $30 well spent. Perl scripts on the PeeCee use the extension .plx and it's possible that if I had sent the file as a .plx instead of a .pl, AND if perl had been installed at the time, M$Outlook on the PeeCee would have fixed the linefeeds as the file was received. At least my girlfriend thinks so. Files sent as .txt have never exhibited the problem. I'll report when we have tried again. -->From the USA, the only socialist country that refuses to admit it. ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org