-=> Quoting Jean Parrot to Dan Ceppa <=-

 JP> I have come to the conclusion that BWRepfx.exe can only deal
 JP> with one fix. If I get out of BW then back into replies, it
 JP> will work its stuff over the date 2k problem again and insert
 JP> something that crunges the .rep. At least this is my
 JP> impression. I wonder if Dale S. is still round to comment on
 JP> this ? 

   Yes.

 JP> ___ Blue Wave/QWK v2.12

   BW 2.12 is much more damaging to the *.REP packet than BW 2.30 is.
   Consequently, there are some errors that it introduces -- especially
   when you open up a closed packet -- that sometimes damage the packet
   beyond the ability of BWREPFIX to repair it.   I have seen it via
   examples sent to me, but have not been able to cure the problem.

   For those effected, I can only advise that they switch to the upgrade
   of BW 2.30.   It works when the patch is applied, and I have not
   heard of reports of damaged *.rep packets, even when reopened.

  [Of course, when you look at the date time group of a reopened packet,
  it will not look correct.   But unless it is mangled too badly, it
  gets fixed when you close the packet again.  BW 2.30 simply puts in a
  date of 1 Jan 1970 or something like that.   BW 2.12 puts in some
  character string with negative numbers, colons ":" and other things. ]

                        dale (at) min (dot) net
                              (1:261/1466)



... Shipwrecked on Hesperus in Columbia, Maryland. 00:21:03 25 Jan 10
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01