Do not chmod your cgi-bin folder to 777. The Apache suEXEC wrapper will see this as a security hazard, and cause a 500 error every time. Go ahead and chmod the non-script files to 777, as long as they arent in the cgi-bin.
Terra (aka ccTech, SysAdmin, co-owner) is running a highly modified version of suEXEC in order to make this server run absolutely perfectly *s*. What it does (aside from being pure magic) is it prevents scripts from other domains from messing with files on your domain (eg a script in my cgi-bin cannot write to files in your account). Because of that, there is an added bonus: Every script you run under your domain runs as your ID (most servers run scripts as user:nobody). That means that your scripts are allowed to use your files, as Apache thinks that your script is actually you. In other words, upload it all, chmod everything in the cgi-bin to 755, and run the thing. It should work dandily
The reason UBB wants the cgi-bin chmodded 777 is so the setup script(s) can write/modify the files in it, so you don't have to edit the real files by hand. Because of Terra's wrapper, those scripts already are allowed access to those files, therefore chmodding is virtually irrelevant (sp?).
If this didn't help, or caused more confusion, or anything, let me know and I'll help you out.
[This message has been edited by Del (edited 12-29-98).]