- IoAllocateErrorLogEntry fails.
- Posted by Maxim S. Shatskih on February 3rd, 2004
Yes, IoWriteErrorLogEntry does this.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com
"Rushikesh Patil" <rushi_pict@hotmail.com> wrote in message
news:uyBhesk6DHA.2568@TK2MSFTNGP10.phx.gbl...
- Posted by Walter Oney on February 3rd, 2004
Rushikesh Patil wrote:
Perhaps you're logging events too fast for the logger service to keep
up.
--
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com
- Posted by Rushikesh Patil on February 4th, 2004
Dear All,
I am using IoAllocateErrorLogEntry and IoWriteErrorLogEntry to log the
events. Does the system free the memory allocated for ErrorLogEntry
structure using above function on its own? Or is there any explicit way of
freeing this memory once IoWriteErrorLogEntry is done.
Is there any restriction on the number of events that can be logged for each
driver?
In my driver I realize that after logging say N errors successfully,
IoAllocateErrorLogEntry always returns NULL to me. Can anyone help me in
figuring out why this is happening?
Thanks in Advance.
Regards,
Rushikesh.
