# Chemin du dossier contenant les fichiers
$sourceFolder = "C:\temp"

# Obtenir tous les fichiers dans le dossier source
$files = Get-ChildItem -Path $sourceFolder

foreach ($file in $files) {
   # Extraire le préfixe du nom de fichier (tout ce qui se trouve avant "S01")
   $prefix = $file.Name -replace "(S01.*)", ""

   # Créer le dossier de destination si nécessaire
   $destinationFolder = Join-Path -Path $sourceFolder -ChildPath $prefix
   if (-not (Test-Path -Path $destinationFolder)) {
       New-Item -ItemType Directory -Path $destinationFolder
   }

   # Déplacer le fichier vers le dossier de destination
   Move-Item -Path $file.FullName -Destination $destinationFolder
}

Clear-RecycleBin -Force

To execute a script when a specific event, such as the occurrence of the word "baba," appears in a log file, you can use a combination of PowerShell and a file system watcher. This method will continuously monitor the log file for changes and trigger the script when the specified event occurs.

Here's how you can set this up using PowerShell:

### Step 1: Create the PowerShell Script

1. **Create a PowerShell Script**: Open a text editor and paste the following PowerShell script. Save it with a `.ps1` extension, e.g., `MonitorLog.ps1`.

  ```powershell
  # Define the path to the log file and the script to execute
  $logFilePath = "C:\path\to\your\logfile.log"
  $scriptToExecute = "C:\path\to\your\script.bat"  # or .ps1 for PowerShell script

  # Create a file system watcher to monitor the log file
  $fileWatcher = New-Object System.IO.FileSystemWatcher
  $fileWatcher.Path = Split-Path $logFilePath
  $fileWatcher.Filter = (Split-Path $logFilePath -Leaf)
  $fileWatcher.NotifyFilter = [System.IO.NotifyFilters]'LastWrite'

  # Define the action to take when the log file changes
  $action = {
      # Read the log file and check for the event
      $content = Get-Content -Path $logFilePath -Tail 10
      if ($content -match "baba") {
          # Execute the script
          Start-Process -FilePath $scriptToExecute
      }
  }

  # Register the event handler
  Register-ObjectEvent -InputObject $fileWatcher -EventName Changed -Action $action

  # Start monitoring
  $fileWatcher.EnableRaisingEvents = $true

  # Keep the script running
  while ($true) {
      Start-Sleep -Seconds 1
  }
  ```

### Step 2: Run the PowerShell Script

1. **Open PowerShell as Administrator**: You may need administrative privileges to execute scripts, especially if they affect system settings or files.

2. **Set Execution Policy**: If your system's execution policy prevents scripts from running, you can change it temporarily by running:
  ```powershell
  Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
  ```

3. **Execute the Script**: Run the PowerShell script you created:
  ```powershell
  .\MonitorLog.ps1
  ```

### Explanation

- **File System Watcher**: This PowerShell feature monitors changes to the specified log file.
- **Action**: When the file changes, the script reads the last few lines and checks for the presence of the word "baba."
- **Script Execution**: If "baba" is found, the specified script is executed.

### Notes

- **Script Path**: Make sure to replace the paths in the script with the actual paths to your log file and the script you want to execute.
- **Log File Path**: Ensure the log file path is correct and accessible.
- **Continuous Monitoring**: The script runs continuously, monitoring the log file for changes.

This setup provides a simple and effective way to automate responses to specific events in a log file.

A check

Voici une réponse concise et précise à votre question :

Le problème que vous rencontrez est lié à la limitation du nombre de caractères dans les chemins d'accès des fichiers sur Windows. Cette limitation est de 260 caractères pour le chemin d'accès complet et de 248 caractères pour le nom du répertoire.[1][5]

Pour outrepasser cette limitation, vous pouvez utiliser le préfixe "\\?\" devant le chemin d'accès. Cela permet d'étendre la limite à 32 767 caractères.[5] Voici comment modifier votre script :

```powershell
$date = Get-Date -UFormat "%d-%m-%y"
$old = (Get-Date).AddDays(-7)

Get-Date >> "\\?\c:\search\avi-mp3-$date.txt"
Get-ChildItem "\\?\d:\" -Recurse -Include *.mp3,*.avi >> "\\?\c:\search\avi-mp3-$date.txt"
Get-Date >> "\\?\c:\search\avi-mp3-$date.txt"
Get-ChildItem "\\?\c:\search" -Include *.* -Recurse | Where {$_.LastWriteTime -le $old} | Remove-Item -Force
```

Cela devrait vous permettre de contourner l'erreur liée à la limitation du nombre de caractères dans les chemins d'accès.[1][5]

[1] https://www.powershell-scripting.com/index.php/forum/5-entraide-pour-les-debutants/4972-limitation-nombre-de-caract%C3%A8res-dans-le-path[5] https://learn.microsoft.com/fr-fr/powershell/module/microsoft.powershell.utility/measure-object?view=powershell-7.4

Citations:
[1] https://learn.microsoft.com/fr-fr/powershell/module/microsoft.powershell.utility/select-string?view=powershell-7.4
[2] https://www.editions-eni.fr/livre/debuter-avec-powershell-9782409039645/manipuler-les-chaines-de-caracteres
[3] https://www.it-connect.fr/powershell-grep-rechercher-des-chaines-de-caracteres-avec-select-string/
[4] https://learn.microsoft.com/fr-fr/powershell/module/microsoft.powershell.utility/measure-object?view=powershell-7.4
[5] https://www.powershell-scripting.com/index.php/forum/5-entraide-pour-les-debutants/4972-limitation-nombre-de-caract%C3%A8res-dans-le-path

A check