iTripoli KiXtart Messages DLL
Install this free KiXtart Messages DLL for clean KiXtart event log entries.
Latest Version: Beta 1
Using KiXtart's LogEvent function with a custom source ("KiXtart", for example) will generate one of the following errors:
Win2000/XP returns "The description for Event ID ( xxxx ) in Source ( KiXtart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:"
WinNT returns "The description for Event ID (xxxx) in Source (KiXtart) could not be found. It contains the following insertion string(s):"
The KiXtart Messages DLL allows the use of custom messages that have a source of "KiXtart" without the error messages.
Installation requires only one file, kixtartmsgs.dll. Setup.exe copies kixtartmsgs.dll to the system32 directory (and adds a couple of registry changes). The setup program will not run on Win9x systems. If distributing the setup via script, use the /verysilent switch for a silent installation. Using the /silent switch attempts to display a progress bar of installation, but since the installation is so rapid the prog bar screen flickers quickly and only proves to be a distraction. Although the setup program is over 200K, kixtartmsgs.dll itself is only 24K.
The example script below uses the LogEvent command to utilize the messages dll for clean event log entries (without all the warning text described above).
LogEvent(4, 1001, "Printer Connections Completed", ,"KiXtart")
LogEvent(2, 1002, "Could not map Z: drive", ,"KiXtart")
LogEvent(1, 1003, "COM Automation Error: DB is corrupt!", ,"KiXtart")
LogEvent(4, 1004, "This is a custom entry with no header", ,"KiXtart")
LogEvent(1, 1005, "Oops! This Event ID isn't in the DLL", ,"KiXtart")
The source type must be "KiXtart". Any icon type may be specified for any Event ID. Event IDs 1001-1003 add success, warning, and failure messages, respectively. Following these messages, the custom information in the LogEvent function is written to the event log. EventID 1004 contains no information header so the custom text is all that appears.