Why does LogWatcher take forever to update when I click on some NT event logs?
When LogWatcher reads records from an NT Event log, some records may come with binary data attached. LogWatcher doesn’t need this data, but it must read it as part of the log anyway. Unfortunately, some events can provide a HUGE amount of this data, in which case LogWatcher has to make several network trips to get it all. For example, DrWatson dumps generate a single event log record, and dumps the state of the machine to a text file, the infamous DrWatson.log. However, it also attaches the dump text to the event record as binary data, which makes a very large event log record. If you are trying to read a computer with several of these events, you will see a delay before LogWatcher displays them.
