In correction to my original post (since updated) it does work with callperl.exe but originally it was
and that didn't work , which added to my confusion(I should have noticed this when posting). Seeing this, I then actually started adding and deleting letters from the shebang line and got what seemed to be random results.!#/c/apps/pp3.exe
worked but!#/c/apps/callperl.exe and !#/c/apps/callperllllll.exe
I didn't happen to think that it might be to do with the word perl
Thanks again for the quick response, You get good service here!!!
This is the second time I have come across mysterious (yes, should have read the docs) perl (related - though not perls fault) problems on windows. At first callperl.exe kept stealing spaces from my command line arguments until I realised that you need to double quote all command line parameters containing spaces. This is important for system and exec in c which call CreateProcess on windows platforms.