> You get that error when trying to execute files on noexec filesystems > too, which is a considerably more likely reason on a functional system. I thought ti looked a lot like the error you get when you haven't chmod +x 'ed a script. Makes sense! Thanks for the info, -Chuck