Unless someone has some other suggestions,
There are three standard names: Application, Security & System. Which map to the system logs:
C:\windows\SYSTEM32\CONFIG\AppEvent.Evt C:\windows\SYSTEM32\CONFIG\SecEvent.Evt C:\windows\SYSTEM32\CONFIG\SysEvent.Evt
And the underlying system APIs default to the Application Log on the current system. Ie. The defaulting is done by the system not the module, and is done when: a) the underlying APIs are passed NULLs for the serverName and sourceName parameters; b) one of the passed values is unrecognised. (Dumb defaults, it should return an error, but there you go.)
As far as I'm aware. the only other files that you can access through these apis, are backups of those three produced by calling the appropriate system API (exposed by the module using the ->Backup() method). You can only do that once you have successfully opened one of those 3, or (perhaps, it is unclear) an existing backup of one of those three. And the way you open a backup is to pass the fully qualified pathname to the New() constructor.
There are no other options.
In reply to Re^3: Using Win32::Eventlog
by BrowserUk
in thread Using Win32::Eventlog
by Al_Gee
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |