Thanks guys, this works, but found the problem to be the fact that
Winamp does not shut down, therefore the script sits and waits.  If I
close Winamp the script will fire off the next event.  I might try
mpg123 for Win.


-----Original Message-----
From: Stephano Mariani [mailto:[EMAIL PROTECTED]] 
Sent: Sunday, February 17, 2002 10:49 AM
To: 'DL Neil'; 'Scott'; [EMAIL PROTECTED]
Subject: RE: [PHP] exec on Windows
Importance: High

Try exec "cmd /c start winamp.exe M000001.mp3" to avoid blocking...

Stephano Mariani

> -----Original Message-----
> From: DL Neil [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, 17 February 2002 2 3
> Subject: Re: [PHP] exec on Windows
> Scott,
> > I am trying to develop a music scheduling system on Windows using
> > 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
> > winamp.exe >null or nul and no luck.  Anyone else try this on
> 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
> 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:
> Regards,
> =dn
> --
> PHP General Mailing List (
> To unsubscribe, visit:

PHP General Mailing List (
To unsubscribe, visit:

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to