To avoid that problem, you'll want to set -o noclobber in scripts or, better, for your login shell, and let it be inherited by subshells, including those that run your shell scripts.

The Test-Path cmdlet can keep you from going bonkers by offering a little bit of script pre-error-handling.

Anyhow, I was writing a script and given that CTP3 now supports the good old try and catch error handling methodology. My error handling logic, of course, was using it.

To avoid errors, it's important to write PowerShell scripts that prevent code from running on an unintended platform. Luckily, this is easier to do than it sounds.

Windows makes it possible to schedule PowerShell scripts to run at a predetermined time. The mechanism of choice for automating PowerShell scripts is the Windows Task Scheduler.