Ok, well I just tried "2>&1" on that job and it worked. Stupid me. I was looking for instructions rather than experimenting.
However, I did find a different problem; things go really wrong if you try something like this:
dir | get-content
because "get-content" takes a list of objects from the input pipe that are interpreted as file names.
Still, my first problem is solved, I have egg on my face, and so it goes. I never said I didn't like Powershell--I enjoy working with all of the common shells (except maybe MS-DOS Command prompt) and would like to see Powershell be more easily integrated with existing tools.
I suspect there is a way to get "dir | get-content" to act more like UNIX shells would, but we could argue all day about the merits.