> I find it odd that MS would not give my access to STDERR, but it looks
> to be the case. :(
You do usually have have access to stderr on a Windows platform. However,
it is entirely possible that it has been hijacked by whatever the process is
that is calling SA and doesn't end up where you think; OR, depending on how
SA is started, SA might be a "non console" process, and will have
stderr>NULL.
The first thing I'd consider trying would be starting whatever is
creating/calling SA with something like "2>logfile.txt" and see if you can
get logging that way.
If that doesn't work, and you can't freopen stderr to something else inside
SA, than some other trick will probably be necessary.
Loren
