Monitor File Events v1.0

[felice2011]

Monitor File Events v1.03

For Friends Is ... "Sniffing"









"Monitor File Events" Stable Version at v1.03 ... subject to Fix or possible Bugs ... Enjoy

https://sourceforge.net/projects/mon...e-events-v1-0/

[Joe Forster/STA]

And there's Process Monitor.

[felice2011]

Originally Posted by Joe Forster/STA

And there's Process Monitor.

Ohh my God, from that filth of Windozz that you posted and my work, the difference is night with day, in addition to having a much more orderly and not messy output Log like Windozz Process Monitor, which repeats the scan Loop recursive on a process with the same ID using unnecessary memory resources. Furthermore, the long repeated list makes it difficult for the user to read about the various processes scanned in the entire system. I have given the possibility to scan up to 5 different directories and their relative sub-directories with search filters for directories and files, obtaining precise targets, without messing up the list with hundreds of processes in other paths that are not of interest.

Saving Logs in txt, Well much clearer in reading and less heavy in order of size for scan time.

You noticed the Notify Event Filter, I think not, you would not have posted the link.

These filters determine what you are watching and thus, which events can be triggered. So what is going on in your system, something that even the Task-Manager cannot say.

● Something is Changed : Occurs when a file or directory in the specified Path is changed.

● Something has been Created: Occurs when a file or directory in the specified Path is created.

● Something has been Deleted : Occurs when a file or directory in the specified Path is deleted.

● Something has been Renamed : Occurs when a file or directory in the specified Path is renamed.

And finally with a single click you get the event option of attributes based on the change of the single file or folder to be monitored in :

● Attributes : The attributes of the file or folder.

● CreationTime : The time the file or folder was created.

● DirectoryName : The name of the directory.

● FileName : The name of the file.

● LastAccess : The date the file or folder was last opened.

● LastWrite : The date the file or folder last had anything written to it.

● Security :The security settings of the file or folder.

● Size : The size of the file or folder.

Why did you come to a conclusion convinced that the "Monitor Files Event" had been the same as the Link you posted.??

In the future, try car driving before drawing conclusions about whether to use it or not.

You have read my signature, well you should have already understood everything.

[Joe Forster/STA]

Originally Posted by felice2011

Ohh my God, from that filth of Windozz that you posted and my work, the difference is night with day

I'm sorry, I didn't want to hurt your feelings! (Yes, I use Process Monitor often. )

[felice2011]

Originally Posted by Joe Forster/STA

I'm sorry, I didn't want to hurt your feelings! (Yes, I use Process Monitor often. )

Rest assured you didn't hurt any feelings... "Process Monitor" I never used, I tested it thanks to your link, tried and trashed after 5 minutes. I generally use "Process Hacker", which is a whole other story, congratulations to the team that created it.

[felice2011]

In Down ... for those interested in testing it, you can confirm any bugs and fixing.

[felice2011]

UPD v.1.01 ... Scan Processes Fix in Different Local Disk.

[felice2011]

UPD v.1.02 ... Added Numerical Counting of Event Activities Based on the Selected Filters and Running Processes.

[felice2011]

UPD v.1.03 ... In Processes Section Fixed Monitoring Command Line Without a Root Directory.