Ok. I took a look at your link, this script works better indeed. BUT! It also doesn't produce an html interactive report, i.e:

123 - link to 123 - [modify] [delete] : Error description.

So you have to copy and paste every URL to check it, and then manually search it in database to modify or delete dead link. This report looks exactly as the one that nph-verify.cgi writes in a file as I described in my first post.

The second disadvantage is a webmaster need to manually start every next portion of verifying. But this process is very long on large databases. I.e. I have to wait about a hour while nph-verify finishes it's job in Unix.

So I think my way is faster and more effective, after all.

There is another way: to modify nph-verify.cgi to force it write all necessary info in .txt file (I mean in Unix) instead of just typing

ID - URL : Error reason.

But my knowledge about perl is too small to do it by myself.

So your script helps to solve the "verifying links in browser" problem, but doesn't solve "handy report" problem.