FileSystemWatcher

[Reynieri]

hi I'm using your script works really good for me. thank you very much
i was wondering if you can add a File System Watcher when ever we finish download any .mkv then the BATCH file get triggered.

i found something that's working for that with powershell, but because i am not a programmer i have no idea of what I'm doing but it think you can make it shine.

### SET FOLDER TO WATCH + FILES TO WATCH + SUBFOLDERS YES/NO
    $watcher = New-Object System.IO.FileSystemWatcher
    $watcher.Path = "Z:\media_downloads\downloads"
    $watcher.Filter = "*.mkv*"
    $watcher.IncludeSubdirectories = $true
    $watcher.EnableRaisingEvents = $true  

### DEFINE ACTIONS AFTER AN EVENT IS DETECTED
    $action = { start-process C:\tools\Cleanup_Eng.bat
              }    
### DECIDE WHICH EVENTS SHOULD BE WATCHED 
    Register-ObjectEvent $watcher "Changed" -Action $action
    while ($true) {sleep 5}

source:
https://itectec.com/superuser/how-to-monitor-a-folder-and-trigger-a-command-line-action-when-a-file-is-created-or-edited/
https://powershell.one/tricks/filesystem/filesystemwatcher
https://www.jamsscheduler.com/blog/how-to-execute-a-bat-file-within-a-powershell-job/

[lavaground]

Hi @Reynieri,
i'm glad someone else finds the scripts useful and I have converted the batch scripts to powershell "recently". 🙂

I have also thought about a FileSystemWatcher, but there is some work to do with the PS Version first, mainly stopping to delete files which were already processed when the script is run a second time. 🙈
A cheap solution would be to move the processed files to another folder outside of cleanup.

I'll definitely have a look in your sources and will try to implement them.

Now some good news: You could run the scripts via the Task Scheduler (e.g. run it every 5 minutes in the background).

The PS Version:

• "General" settings can be defined as you like
• • To execute in the "background" you can try to run it as nt authority\system (leave the password blank) or create a local user account for that purpose
• • Activate Run whether user is loggged on or not
• "Triggers" can also be defined as you like, don't forget to enable them
• "Actions" would be (please pay attention to the "s):
• • Program: "DRIVE-LETTER:\PATH-TO-YOUR-POWERSHELL-FOLDER\pwsh.exe"
• • Add Arguments: -file "DRIVE-LETTER:\PATH-TO-YOUR-SCRIPT-FOLDER\_cleanup.ps1"
• • Start In: DRIVE-LETTER:\PATH-TO-YOUR-SCRIPT-FOLDER (that might not be necessary as we have a constant PATH in the script itself)
• "Conditions" can also be defined as you like, i do not recommend the "wake up to run" if you sleep next to your machine
• "Settings" make sure you have activated:
• • Allow task to be run on demand
• • Run task as soon as possible after a scheduled start is missed
• • If the running task does not end when requested, force it to stop

Or if you really want to go crazy you could make it a system service with NSSM and run it as a Task.