in reply to Win32::Process - need help from an expert!

Your second argument to Win32::Process::Create is a bit strange, it should be the full path name of the child program (the others look OK). It should not wait for the child to complete, use $saSyncPL->Wait(INFINITE); for that.
I am not sure what you mean by "embedded processes". The UNIX ability to switch programs without creating a new process (exec) is not available on Windows, the perl exec is only pretending to act like the UNIX one.

Replies are listed 'Best First'.
Re^2: Win32::Process - need help from an expert!
by somuchh8 (Novice) on Sep 13, 2007 at 14:45 UTC
    The second argument ( $^X ) is the fully qualified path to perl.exe. I'll get rid of that for now and use what I know is the fully qualified path and see if it helps. I'll also use the Wain(INFINATE) that you mentioned to see if that helps as well. Thanks for the quick reply! Andy
[reply]
      Sorry, you are correct, $^X should have worked (I missed the fact that you were running another perl script).
      Is the second script actually running?
[reply]
        I don't believe the script I am trying to execute it running. I'm simplifying things now by using the helloworld.bat file which is: 
        echo helloworld > c:\helloworld.txt

        [download]
        To see if things are running. Also, I am using forward slashes "/" like I do for Linux / Unix on the path instead of using back slashes "\" like windows uses. I've switched these to see if it works like that.
[reply]
[d/l]

In Section Seekers of Perl Wisdom