You can use Win32::Process to start a second copy of Perl as a seperate process, and run the second script there if that will fulfill your requirements. You can specify DETACHED_PROCESS when you call Win32::Process:Create(...); which will deal with that part.
What you haven't said so far is whether you want the ability for the 2 scripts to communicate. You can do this with either Win32::Pipe or sockets.
You also haven't said whether you need to actively kill the background process in the event that it goes ary or runs too long. Win32::Process::KillProcess() or $pid->Kill(); will take care of the first part if needed and then you only have to decide when. Whether by timing or some other mechanism, but more details on your requirements would help.
Examine what is said, not who speaks.
In reply to Re: Re: Re: Re: Re: perl fork cmd on Windows 2000
by BrowserUk
in thread perl fork cmd on Windows 2000
by TheYoungMonk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |