Hello again: In April 2010 I posted a thread on this issue. http://www.wilderssecurity.com/showthread.php?t=269578&highlight=parse+logs...
Thanks, Marcos. As the subject line says, a simple tab character separation between object and message would solve this. -- Roy
Marco: Ahh, that explains it. We're looking at different records. You have posted (very nicely I might add) the hex view of a summary record,...
Marcos: Using 4.0.417 here -- don't see that in this version. Is this a releatively recent change? There's no separation in the .xml file...
Hi: I've got some rather large (24MB) log files and would like to parse them outside of NOD32. The problem is that the error/information...
No -- that wasn't the task. The task was to scan and report, not to clean, w/o user intervention. I haven't tried strict, because I want to see...
Marcos: As it turns out, I run v2.7, 3.x and 4.x on three different machines. The 4.x scan completed this morning sometime and displayed the...
Hi: On-demand scan has been running for some time now, stopping at each alert for user interention. How to I get it to keep scanning through...
NOD32 v2.7 gave a false detection of a damaged GZ archive on what was an EXE executable. Is there any confirmation of this problem?
The search tool on this forum cannot search for short strings like UHA and GZ. As these are recognized file extensions, like ZIP and RAR,...
FYI: NOD32 2.7 doesn't appear to understand (some) UHA archives, and generates false "archive damaged" errors. Just successfully unpacked...
Marcos: "AH"? what mean? In any case, is it then safe to ignore the 'unpack error' messages? TIA
Marcos: Have no idea if they are patched FSG's. NOD32 doesn't scan them, apparently, but rather emits the "unpack error" message. Heres a...
Hello: Does NOD32 unpack FSG 1.33 or 2.0? I'm getting "unpack error" with some files that are packed with FSG (maybe all of them). Thanks...
Separate names with a comma.
