TECHNICAL SPECS

Global Paths & Environment Variables

MountMate initializes hardcoded directory targets to maintain persistent state and logs:

$script:ScriptsDir        = "C:\Scripts"
$script:CacheDir          = "C:\RcloneCache"
$script:ConfigFile        = "C:\Scripts\mounts.json"
$script:LogFile           = "C:\Scripts\manager.log"
$script:MutexTimeoutMS    = 5000 # Inter-process Sync Lock

Concurrency Control & State Persistence

To avoid race conditions and corrupt state writes, configuration serialization is strictly guarded:

• Mutex Lock: Global\MountMate_Config_Mutex guarantees thread-safe atomic access across background watcher threads and interactive console sessions.
• Atomic Swaps: Configuration changes are written first to mounts.json.tmp before replacing target state files via [System.IO.File]::Replace().

Cryptography & Backup Specification

System state backups (Option [12]) use PBKDF2 key derivation and AES-256 CBC encryption:

Core Execution Subroutines

Key PowerShell functions responsible for privilege isolation and non-blocking drive health checks:

# Dynamic Executable Discovery
Get-RcloneExecutablePath

# Non-Blocking Drive Async Ping
Test-DriveReadiness ($driveLetter)

# Privilege Isolation Wrapper (Avoids Explorer Token Lock)
Start-ProcessAsUser ($vbsPath)

Default Mount VFS Flag Architecture

MountMate passes hardened VFS parameters to Rclone to guarantee high read/write throughput and background stability:

--vfs-cache-mode=full
--vfs-cache-max-size=5G
--vfs-cache-max-age=6h
--vfs-write-back=5s
--dir-cache-time=168h
--poll-interval=30s
--buffer-size=32M
--vfs-read-chunk-size=64M
--vfs-read-chunk-size-limit=2G
--network-mode
--drive-use-trash