vy22 — Thu, 22 Jun 2000 09:35:00 +0000

Well Vulken you are about to recieve a medal cause I got it working!!! Wooohooo!
No joke man I was summersaulting around my house yesterday as you have no idea how much this has been driving me round the bend.

~I did what you said and connected using telnet. I ran the perl -c on all my cgi scripts and all of them but one said Syntax ok! One of them said I was missing a bracket somewhere.

I noticed that a huge chunk of one of my cgi scripts had disapeared so I uploaded a new one and that worked! Telnet also helped me find my absolute path which helped me repair my links page.

Feel free to send me a button and a decription of your site to webmaster@noggy.net and I will add it to te Noggy network with a good word for ya.

One last thing. if you go to my site and then look at the links page you will see that the links page works. However how do I place this page in my template and stilll keep it working? You will see what I mean when you have a look.

Thanks

~Vy~

Ken Elliott — Wed, 21 Jun 2000 15:46:00 +0000

Well once you telnet to your server you can move around just like dos but the cd(change directory) is not cd.. it is cd .. to move back a directory.

Since you know the absolute path you could just press cd /htdocs/www/noggy.com/cgi-noggy/
and that will put you in your cgi folder. Then type "ls" to see it's contents. Then type

perl -c scriptname.cgi

and see what it's output is. My host has the benefit of having a PERL checker on their website so I don't have to go through all this. Well I also have perl installed so I do most of my debuggin' here.

Try that and then post the output.

VulKen

vy22 — Wed, 21 Jun 2000 13:54:00 +0000

Ok I can telnet my host but unfortunatley my knowledge on telnet allows me to log in and thats it!

dos?

I have my own NT server with perl installed on it so I suppose I could upload it to IIS but how I would diagnose the script is beyond me,

Cheers

~Vy~

Ken Elliott — Wed, 21 Jun 2000 13:45:00 +0000

well see if you can telnet to your server and run the script with the -c operator. That will give you all of the compilation errors including what line they were on. That standard error isn't worth the color it's displayed with...or something.

perl -c scriptname.cgi

if you can't telnet to em try ftping' with dos or something. I've never tried using dos to run a PERL script on a foreign host, but I imagine it might work.

Or if you have PERL installed on your computer just do the same thing to the script via a dos prompt and see what it gives you there.

Hope this helps.
Just keep this post going and we will rectify your problem sooner or later .

VulKen

vy22 — Wed, 21 Jun 2000 12:55:00 +0000

I have! Look at line 8

"The server has encountered an internal server error please contact webmaster@noggy.net"

~Vy~

Ken Elliott — Wed, 21 Jun 2000 12:52:00 +0000

It would help some if you posted the error message that you recieve when you run the script.

VulKen