_EventLog__Report() $aData?

[Mechaflash]

#include <EventLog.au3>
_EventLog__Report($hEventLog, $iType, $iCategory, $iEventID, $sUserName, $sDesc, $aData)

In the parameters section for $aData, it just says,

Data array formated as follows:

[0] - Number of bytes in array

[1] - Byte 1

[2] - Byte 2

[n] - Byte n

Can someone help me understand what it's for?

EDIT: Damnit... I thought I clicked General Help & Support...

Edited October 10, 2012 by Mechaflash

[Mat]

http://msdn.microsoft.com/en-us/library/windows/desktop/aa363679.aspx

A pointer to the buffer containing the binary data. This parameter must be a valid pointer (or NULL), even if the dwDataSize parameter is zero.

Looks like its usually NULL anyway.

[Mechaflash]

I see... I noticed where they get put in the event log but just didn't know what their purpose was. Started noticing that some events don't have them as you stated.

Just passed $aData[1] = [0] to it.

Another question about this function if you're willing to answer it:

No matter what value I set for $iEventID, I get an error reporting that the source doesn't contain information on that eventID. I understand that it's event IDs created inside a "source" which allows the event viewer to report these in the event log. Is there a way to just bypass it and only include a general description?

If not, how do I create my own eventID information for a unique source?

EDIT: Found the answer to the strike-through question

http://stackoverflow.com/questions/446691/how-to-create-windows-eventlog-source-from-command-line

Still want to know if it can just be bypassed however. Make it easier.

pfft nvm. It's the same as just creating an event.

Edited October 10, 2012 by Mechaflash

[Mat]

What resources have you added to the exe? I'm guessing none.

You may want to have a look at this example: http://msdn.microsoft.com/en-us/library/windows/desktop/aa363680.aspx

Just be warned that what you are doing was not designed with languages like AutoIt in mind. I once did a lot of work on message tables in AutoIt. I'll see what I can dig out.

[Mat]

Meh, read this instead:

[Mechaflash]

Because of its complexity and my uneasiness to have to deal with this on every machine I want to run the program on, I think I'll just stick with a basic text-based log file. Easier to manage anyways.