Very tru. Thanks for the input. Wish I had even thought about about that before.
Now, how I got evertyhing back to working.
1 of 2 things must of happened.
A possible answer to why it quit:
They moved the perl program when they re-booted the server. The tech from my hosting company said that the program was looking at the wrong path to perl. After looking at the readme, it states that the first line of every .cgi must be changed if the default location to perl is not used. I KNOW i didn't do that before, but I may have put the full path to perl in the links.cfg. I'm not sure why this would have caused the links 2.0 to work properly except for the link checking (the error was "http not supported"). But even that problem is fixed now.
So at least fixing this problem did fix that one as well.
Unfortunately, it did give me another bug to fix...
When checking links the error reads:
Unable to load Parallel User Checker. System Error:
--
Can't locate HTTP/Request.pm in @INC (@INC contains: /iiw/cgi-bin/mistresss.com/links/admin /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 .) at /iiw/cgi-bin/mistresss.com/links/admin/Validator.pm line 23.
BEGIN failed--compilation aborted at /iiw/cgi-bin/mistresss.com/links/admin/Validator.pm line 23.
--
Using IO::Socket method instead.
I tried to find a request.pm file but couldn't find one. Is there supposed to be one? Is there possibly a different problem here I don't see? Thanks in advance for your help.