That jibes with what I remember about a similar problem I experienced a few
years ago. I'll try and find a copy of the Windows Resource Kit and see if
that's the cause (I tried finding logevent on MSDN without success)...
Thanks Tom!

"Tom Galvin" <tom### [at] imporg> wrote in message
news:Xns### [at] 204213191226...
> "Scott Gammans" <nos### [at] scottgammansspamisevilcom> wrote in
> news:3e76414a@news.povray.org:
>
>
> > All three logs (application, system and security) are set to overwrite
> > events > 7 days old.
> >
> > --sg
> >
> >
> >
>
> If the log fills up and the oldest event is less than seven days old, it
> can sometimes hose windows.  With the logevent utility from the resource
> kit you can fill the event log up and see if that was the issue.

Post a reply to this message