| Tool name : | EventLogViewer |
| Description : | EventLogViewer is a tool to browse through the different Windows Event logs. Currently you can only search for a specific key word (not case sensitive). But in the future I’ll add some further features. |
| Tested on : | Windows XP |
| Feedback : | In case you encounter any problems with the tool, you have suggestions to improve it, or you tested it with a Windows version i’ve not yet tested please drop me an email. |
| Downloads : | Version 0.1 – Binary & source |
| Screen shots : |  |
C# – Windows Event Log Viewer
Oct 7th, 2010 by carrumba
XP SP3, IE 8, currently updated/patched, US English, Visual Studio 2010.
Haven’t tried it on win 7 64 bit yet. This XP workstation is my baby..
The message it shows the high ascii boxes on is.. and it occurs after the line breaks for sure that’s what it is. I saved the log file and looked at it in a hex editor and it’s hex code 00 that’s making those square ascii boxes (like some foreign languages look like) it’s not a space a space would be hex code 20.
(keep in mine in your event log program this is displayed as single line, where we can see it has some kind of line break going on)
The audit log was cleared
Primary User Name: SYSTEM
Primary Domain: NT AUTHORITY
Primary Logon ID: (0×0,0x3E7)
Client User Name: heatshrink
Client Domain: BLACK
Client Logon ID: (0×0,0x1AF00)
(a cut an paste from the mmc snap-in same log entry. saved to disk then hex edited.)
00 00 01 01 00 00 00 00 00 05 12 00 00 00 53 00 ··············S·
59 00 53 00 54 00 45 00 4D 00 00 00 4E 00 54 00 Y·S·T·E·M···N·T·
20 00 41 00 55 00 54 00 48 00 4F 00 52 00 49 00 ·A·U·T·H·O·R·I·
54 00 59 00 00 00 28 00 30 00 78 00 30 00 2C 00 T·Y···(·0·x·0·,·
^^ ^^ ^^ ^ those are “00″ ‘s
I haven’t dug into your code, just ran it, and mostly played around the edges with the mainform as stated already. That’s it, I’ve kind of just been glad it works. If there’s a html translation going on, then could be what it is. I got to be honest I am more familiar with VB6 than .net but if I find an answer, I will pass it right back here.
And this is all I know so far. it could be something as simple as UTF-8 getting turned on somewhere. I don’t know.
hey heatshrink.
thanks for your feedback!
the HTML here became a little mess over the last 3 years and unfortunately somewhen in the far future i have to redesign anyway :/ and i am definitely not going to use the TABLE tags anymore so the thing with the screen space would be solved.
in the security section you say … i’ve found broken TD tags and fixed them. the rest “should” be ok. what browser/os are you using? i have win7 with IE/chrome/FF. they seem to be ok.
the idea behind it was to remove tracks.
Also, I found myself the first thing, was widening the form — big difference in productivity!
Since she isn’t wrapping each line’s text. Perhaps making the font smaller and fields smaller could make it use even less screen space?
Just thinking out loud. Again, thanks for the app.
I notice under security, there are either high ascii or escape codes which do not render properly.
I have no idea why. Sadly I only have one entry in that part of the logs, and it never changes so it probably doesn’t matter in the big picture. Or maybe it’s something as simple as filtering blank spaces or carriage returns?
I really love how it clears the log with one click. Too bad the snap-in doesn’t do it that way, which is probably why you wrote the app? ;o)