Outwit
Outwit is a suite of tools based on the Unix tool design principles allowing the processing of Windows application data with sophisticated data manipulation pipelines. The outwit tools offer access to the Windows clipboard, the registry, the event log, relational databases, document properties, shell links, and the event log.
| Tags | Database Front-Ends Desktop Environment tools Logging Systems Administration Text Processing Filters General |
|---|---|
| Licenses | BSD Original |
| Operating Systems | Windows Windows Cygwin |
| Implementation | C C++ |
Recent releases
- 05 Dec 2005 13:33
Changes: Winclip now supports an option for reporting the available data formats.
- 11 Feb 2005 13:32
Changes: The memory allocation and locking in winclip have been corrected to fix a crash.
- 10 Feb 2005 08:04
Changes: The winclip program now allows the specification of the data's language and sublanguage, while the readlog program is now more robust in the face of invalid data in the registry.
- 19 Nov 2004 11:05
No changes have been submitted for this release.
diomidis
19 Nov 2004 07:24
Heartbeat
- Popularity Score
- 102.20
- Vitality Score
- 2.21
- Subscriptions
- 27
- All comments
Recent comments64-bit winreg.exe?
Does anyone by any chance have a winreg.exe compiled as a 64-bit executable?
As you may know in Windows 64-bit there are separate 32-bit and 64-bit registries, and pre-Windows 2003 SP1, there is no way for 32-bit applications to access 64-bit registry values (or vice versa I think) via the API, so I think parsing the output of an application like winreg.exe would be the only way to do it.
Bug in readlink()
Hi there,
The following is bogus since strlen() may return a size less than 4. Ooops!
Alexis Wilke
if (strcmp(lpszLinkFile + strlen(lpszLinkFile) - 4, ".lnk") != 0)
return (-1);
Great, but not quite what I was hoping
I think I'm going to love these tools and get a lot out of them, but the first thing I tried to do does not work.
I was hoping to be able to use docprop to filter files based on the content of file summary properties set through the file properties dialog in Windows Explorer, and that doesn't seem to work (at least not in all cases). I added a keywords property to a text file in Windows explorer, but when I try to use docprop on it, it says "Unable to get properties for ...". Apparently, Windows Explorer is able to write the properties in a way other than how docprop can read them?
readlog feature request
Nice set of tools, these will come in handy!
One wish for readlog: it would be great to have a mode whereby readlog continues to run indefinately, effectively 'tailing' the eventlog.
Oh, and to select every eventlog (app,sys and sec) and to qualify each message with the log it came from.
Thanks for your efforts.