Hello all.

While nph-verify.cgi is still unable to deal with big link databases in browsers (lock up after 100-200 links checked) I offer a long, but working way to get a handy htm - formatted results using Telnet.

Here is complete instructions for amateurs like me:

1. Connect your server via Telnet (SecureCRT program recommended).
2. Go to your links directory:

cd cgi-bin/links/admin (in my case)

3. Start nph-verify script and tell it to store verifying results in txt file:

./nph-verify.cgi >deadlink.txt

4. Give the script a time to finish it's work (it may be a pretty long time). It's a perfect time to drink a couple of beer.

5. Launch your FTP program and enter links/admin directory. Download report file (deadlink.txt) to your computer in ASCII format.

6. Here is the best part of the trip: Open this file with Microsift Word and make a MACROS turning a plain text report to a formatted html one.

Here is how your pain text report string will look like:

1070 - http://www.some_of_checked.com/ : 500 - Internal Error

Here is how this string have to look like after applying Word macros:

<br>1070 - <a href=http://www.some_of_checked.com target=_blank> Check it </a> <font size=-1><b> [<a href=http://www.yoursite.com/cgi-bin/links/admin/admin.cgi?db=links&amp;modify_form=1&amp;ID=1070&amp;ww=1 target=_blank> modify </a>| <a href=http://www.yoursite.com/cgi-bin/links/admin/admin.cgi?db=links&amp;delete_form=1&amp;ID=1070&amp;ww=1 target=_blank> delete </a>]</b></font> : 500 - Internal Error

Apply this macros to all text strings and save this file as deadlink.htm

7. Launch your browser and open deadlink.htm.

You're done. Enjoy.

******************

It takes a while to write such a macros, but then you can easily turn boring text report to a nice html page with possibility of one-click checking/modifying/deleting dead links. Be extremely careful recording macros and double check every character you type.



Thank you.

PS. Please, don't ask me how to record Word macros. It's boring, but simpliest procedure ever. Just place your cursor at the beginning of plain report string and make all nesessary changes. To force ID number "variavle" copy the number while recording macros and then paste it after ID= in URL's . To the right navigation through plain string use Find and enter _:_ and _-_ where _ are spaces.
Remeber that error string lenght and URL lenght are vary in each report. So use only common elements, as I said above.

Sorry for such a lamer approach, but this is the only one working for now.

All professionals, please, do something with nph-verify.cgi.

Thank you.