permissions issue on print to a file

[Kenneth Brody]

Quoting Fairlight (Mon, 4 Dec 2006 17:51:56 -0500):
[...]
> The only thing I've ever seen on STDERR from fP is a \007 bell
> character. Everything else goes to STDOUT, so in Windows you should
> be able to use a simple ">wherever" and omit "2>&1" entirely unless
> you're generating errors in fP that will ring the bell.  I'm not even
> sure it's possible to redirect STDERR under Windows.  I think I tried
> once when porting Lightmail, and it was so non-doable that I duped
> the fd's internally and sent it all to STDOUT internal so that it
> would all come out on one channel.

Outputting a Ctrl-G via the console API doesn't cause the bell to
beep.  Instead, you get a character consisting of a small dot in
the middle of the cell.  The Windows version of filePro uses the
MessageBeep() API call to beep.

As for I/O redirection, XP's cmd.exe recognizes "2>filename" as
well as "2>&1".

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com