That is a bit hard to believe, but I will caution you on a few things.

The scripts you are using are likely to be built with PHP4 in mind. That said you need to have and idea of whether or not the server is running PHP4 and if it is running the new PHP5 what the exact context of the errors are. Is ...

This particular feature will only work with browsers who display content as they get them. IE and firefox are known to work this way. Also if you have a proxy between you and the internet, this problem will occur. There is not a whole lot I can do about third party software not conforming to spec.

I am actually working on Radio Toolbox v2 at the moment so it will be in that version. Work has slowed me down in development of this version unfortunately.

It isn't steamcast it appears to be something affecting their database. I'd give it a few days and wait for them to fix it. Steamcast will relist once the issue with their db clears.

Actually with plesk this is not so, you must specifically login as the user or set the execution to the appropriate level for the plesk user. If you are using it as admin then it would be the admin user.

There is no real reason why steamcast can't run as an unprivileged user. Look at your event log and resolve the Warnings.

This section is completely wrong

; SOURCE CONFIG
; -------------
SourceIsSC=Yes
SourceIsDefault=Yes

These variables cannot be defined without first defining a SourceMount

I ...

I'll see if I can duplicate on my setup.

this also works with steamcast

The issue is between his source (oddcast) and the server. Timed out on Recv call is basically steamcast's way of saying that it waited for a a little bit to get data from the encoder but the encoder hasn't sent any in a reasonable timeframe. The end result is that steamcast kills the connection ...

The user-agent field is supplied by the browser, steamcast has no way of altering it. If that is your browser's request then your browser has something installed in it that is supplying that identifier.

Got me, that's just someone using a browser to view the steamcast admin page. Looks to be on your local network so someone is messing around with you if you are not familiar with it.

Actually to clarify this message usually comes up when a client establishes a connection to the server but never send a request or the request is not following spec. Most times this type of error occurs when a monitoring service is checking ports or someone is port sniffing. It does not mean that ...

I hope this is the right board to post to: My company is just now in the beginning and research stages of looking into starting up an internet radio station. We have looked into Live365 and Shoutcast… and have decided Shoutcast would be a better option since we are not wanting advertising and a ...

Sorry gotten a bit busy with work, once I get some downtime I will revisit this and get a new version out. Life's been a bit hectic lately.

when I say location I meant the URL. Have you tried taking steamcast out of crontab, it was never really designed to be run from there. Just run it from a shell prompt and if it dies again we can look at the log for some possible signs for why it went missing. If you need to run a cron job to ensure ...