The "out of the package" DBMan with the original .cfg file and html.pl file. Just change the $db_dir_url in the .cfg file. Don't even change the path to perl at first. See if it works. If it doesn't, change the path to perl and see if that works.

We know for certain that the DBMan as distributed doesn't have any mistakes in it that would cause a 500 error, so the best thing to do is to start from there. If that doesn't work, then the problems can only be:
1-- one or more files uploaded in binary mode
2-- one or more files with the wrong permissions
3-- your server doesn't have the capacity to run the script.

It really has to be one of those three problems, if the demo doesn't run. There are no other possibilities that I can think of. (I'm sure someone will come along with another one. :-) )

Hmmmm. Just a thought, which would be within the "server not having capacity" category. Are you sure you can run cgi scripts from that directory? Often cgi scripts can only be run from a cgi-bin or another directory that has script-running turned on.


JPD
----------------------------------------------------
JPDeni's DBMan-ual
How to ask questions the smart way.