RE: [PHP] exec on Windows
| From: | Stephano Mariani | Date: | Sun, 17 Feb 2002 15:49:09 +0000 |
| Subject: | RE: [PHP] exec on Windows | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-85107@lists.php.net to get a copy of this message | ||
Try exec "cmd /c start winamp.exe M000001.mp3" to avoid blocking...
Stephano Mariani
> -----Original Message-----
> From: DL Neil [mailto:PHPml@DandE.HomeChoice.co.uk]
> Sent: Sunday, 17 February 2002 2 3
> To: Scott; php-general@lists.php.net
> Subject: Re: [PHP] exec on Windows
>
> Scott,
>
> > I am trying to develop a music scheduling system on Windows using
the
> > command line to fire off WinAMP. The first exec works fine, then it
> > stops
> > and says that program execution time has been exceeded.
> >
> > An example would be:
> >
> > exec ("winamp.exe M000001.mp3");
> >
> > a while loop kicks off the second. I tried to send the output to
null
> > winamp.exe >null or nul and no luck. Anyone else try this on
Windows?
>
>
> Sounds interesting.
> I take it that it is the PHP script that stops (not the winamp
player)!? Looks like you are running
> into
> problems with the script execution time limit. Herewith a couple of
theories:
>
> 1 what happens if you specify that the winamp is to run in its own cmd
shell - will control return
> to PHP
> 'immediately'?
> 2 if the problem is time-out, and you can only play one .mp3 at a
time, so looping to 'the next'
> must be
> dependent upon the preceding track finishing first, what happens if
you adjust the set_time_limit
> to 0/no limit?
> (RTFM:
> http://www.php.net/manual/en/function.set-time-limit.php)
>
> Regards,
> =dn
>
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php