You can
learn more about the event log in general on the Microsoft Web site at
http://technet2.microsoft
.com/windowsserver/en/library/9930c8f1-54ed-4d07-afa6-bc3c597bbe9c1033.mspx
.
However, effective event log usage goes even further. As you begin writing your own applications (even
batch file applications), consider adding event log entries to one of the standard logs or use a special log
for the purpose. The Code Project article (
http://www.codeproject.com/dotnet/evtvwr.asp
)
shows how to add new event logs using registry entries. You??™ll also want to review the MSDN ???EventLog
Key??? article at
http://msdn2.microsoft.com/en-us/library/aa363648.aspx
.
RECORDING SYSTEM STATUS INFORMATION
447
/T {ERROR | WARNING | INFORMATION}
Specifies the kind of event to create. Even though
the Windows event log accepts other event types, the only three acceptable types are error,
warning, and information. These three types reflect three levels of severity, with information
being the least severe and error being the most severe.
/SO
source
Defines the source of the event. You can use any string as the source. However,
providing a meaningful application identifier is usually the best idea.
Pages:
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058