- 339 ED - 2448 -

Robozilla, our automated link checker, has just completed a run of the directory and has flagged up any addresses which are not working. Due to the growth of the directory in recent months and the long gap between this and the previous run, more errors were found than usual. This means that it is likely that, for the next few days, editors will be concentrating more on resolving these errors, as opposed to other duties. Therefore, submissions may take longer to process during this time. Sorry for the inconvinience, but we hope you'll agree that removing dead links from our existing listings is a good thing.

Departs from Gatwick on 17-November-200 6 @ 339

While doing some serious Indigo development I noticed that a process was up and running for a long period of timeafter any errors in the Indigo runtime occured. It was dw20.exe. Doctor Watson. Thank you Doctor, but I only read the brutal stack trace. So, if you're like me and don't care about sending specific self-induced pre-beta technology error traces to Microsoft, do this: Open Control PanelSystem Goto Advanced tab Click Error Reporting button Disable error reporting Disable critical error notifications Indigo develoment is a lot more enjoyable now. I normally disable this anyway, but this was inside a Virtual Server image, and as it goes, you learn it the hard way.

13,339 downloads

Agree it should read something like "valid pages" or "error free". I run validation all the time and the pages I feel the errors will have to stay until I have time to fix the, don't matter as the validation isn't going to make anything. Stacey

Rosemary Righter -- The Times