NS>
  > how would I redirect the printf?  I've done fprintf(stderr,
  > "blah) in the past...  but sometimes my program would crash
  > and there would be nothing in the file.  I wonder... no. I
  > bet it's the Lazywrite feature of the file cache.  What do
  > you think?
NS>

JP>  Nope.  It's the line buffering done by the standard library.  Either
JP>  use setvbuf() to remove all buffering on stdout/stderr, or explicitly
JP>  fflush() after every fprintf.

  Of course another solution is to use DosWrite(1,...).  If a write to a
file handle via DosWrite has returned then NOTHING should be able to
prevent it from eventually appearing on the output device.  This also saves
the overhead of the STDIO library.  Also (for me at least) most debugging
output is plain text and doesn't need any %d modifiers etc that printf()
provides.


  cya
___
 X MR/2 2.0 NR X If it walks out of your refrigerator, LET IT GO !!

--- Maximus/2 2.01wb