BL> Why did it do it in Telemate, using the same defaults for both
 BL> a wazoo and a BBS connect? How can you set up a modem to do
 BL> that that?

 BV> Oh no you don't. Remember, I may be dumb, but I'm not stupid.
 BV> You're not going to drag me into this one.

  It's a pity, because it's a genuine mystery. Is it possible for BC++
to corrupt a file without leaving evidence?

  When I first started using pointers in C, I rooted pkt2qwk. I forget
what it did now, but it stuffed my mail somehow. I always pack my hard
disc so there are no spare spaces (I don't like the idea of programs
all mixed up together), and pkt2qwk was on the end, with BC++. 

  I did a fc/b (binary file compare) between the suspected corrupt
file and the original, and there were no differences, but I replaced
it anyway... first doing a Norton SD to clean up the space it had
occupied. The problem went away.

  It has since happened a second time, when bc.exe ate itself, and
gave me 17,400 errors when I tried to compile hello.c! rofl! I did a
fc/b and found no errors, but then I erased bc.exe, ran SD, and put it
back again and it worked.

  This is what I did with autoexec.bat to cure my modem problems...
and it worked.

  Unfortunately, I had long-since lost track of all the changes I had
made to the modem init string, and it is possible that I unhooked
something bad there too, but I don't think so. The original problem
was basically impossible to explain with modem init strings... and the
last thing I remember doing was trying to compile Paul's DEVIL-C with
BC++.

  In my ignorance, I suspect that BC++ somehow connects junk to
another file, without it showing in a file-compare or the FAT. Maybe
it rewrites the boot. Have you ever heard on anything like this? I 
think I may have invented a do-it-yourself virus.

Regards,
Bob
  
___ Blue Wave/QWK v2.12
@EOT:

---