OK...i'll be humble and ask for help now :)

OK, all i'm getting is a blank screen. No errors are being shown, in fact nothing is being shown. Any ideas? I'm running on WIN2K.

Here's some suggestions:

1. Check the NTFS permissions on the files.
2. Make sure you have the latest version of ActivePerl installed.
3. Read the FAQ questions regarding Windows 2000 at http://www.augustknights.com/tribesserverstat/
4. Turn on debugging options in the .conf file(s) and report any output you get here.

HTH!

Do I need to have qstat running already?

Yeah, if you don't have qstat installed, my stuff won't do a thing... The backbone of tribesserverstat is qstat. Once you get it installed, you can check to make sure it's [qstat] working by executing a line like this:

qstat -R -P -htmlname -raw +++ -t2s 157.238.46.39:28000

(I think that's right... sorry, doing it off the cuff there...)

OK, I checked the qstat installation and it all checks out, but i'm still getting a blank screen.

http://inner-workings.uintahbasin.or...erver...ect...

any other ideas?

Wow, now that's quite interesting. I don't think I've seen tss do that, like, ever! When you do a view source on those pages, the script seems to be building the header for the page, but that's it. It's like it's exiting before it does anything useful. Is it possible that the template files are inaccessible? Have you checked the file permissions on the scripts themselves?

According to Netcraft, the server that you're using is a Windows 2000 server with OmniHTTPd/2.08 as the web server. tss has never been tested with that web server, nor do I have any experience whatsoever with it, so other than the things I have hitherto suggested, I'm at a loss to explain what's going on. 90% of tss problems seem to do with misplaced files (or mispointed settings in the .conf files) or permission problems on the files themselves. If that's not the answer, I'm stuck. Sorry...

Well, I will go back over my installation and see if that is the problem. I will try it on my WIN IIS server and see if it is just the Omnihttpd web server. I will let you know, thanks.