-=> Quoting Sean Dennis to Kevin Nunn on 09-16-09  15:50 <=-

Hi, Kevin
 
 -=> Quoting Kevin Nunn from a message to Sean Dennis <=-
 
 KN> That could have been a problem :) I used to be a real BW fanatic, but 
 KN> since I could not get TGW to work, I got pretty used to QWK and it's 
 KN> not so bad now. But if I were to use BW again, I'd probably never go 
 KN> back.

 SD> Yeah, Nancy (who's a regular here) uses BW heavily.  I think this
 SD> weekend  (maybe Sunday) I'll get around to tinkering.  It's been a busy
 SD> week. 

As long as he's "taking my name in vain", I'll just jump in. 
  Yup,
I got into BW way long ago... back when to read QWK files in it you
needed another utility to convert the reply packets to .rep form.  I
much prefer the native BW (using BW doors and BW packets in my BW
reader), but I still haven't given up the BW reader just because all I
could get were the QWK packets.  2.20 and following read and reply just
fine to those, too... and the fixes we've been talking about to fix the
Y2K bug in the reader with the QWK packets have kept that viable.  :)  

Fixes to the BW doors, and to such as the TGW, may take a little
longer... as a favor to my sysop, hubby worked out the fix for TG's BW
door (not the TGW), and with that fixes for the readers, and the batch
file(s) needed to fix the other BW doors (needs to have the BBS software
installed along with the BW door to be run, IIUC, or at least the door
itself?).  It's all in the same ZIPfile available various places.  TGW
used a different complier or language or some such, so he couldn't do
anything there.  (As I just mentioned to Jean, I'm no computer expert!)

ttyl     neb

... Dawn crept across the lawn, searching for her car keys.

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/WINServer v3.0pr5