BV> What makes it even more difficult is that Bob has been playing
 BV> with his own COM routines written in VB, he's probably run some
 BV> of the stuff which Paul has posted after "extensive" testing

  Yes... I first noticed it after trying to compile Paul's DevilC, but
what got me most, was the total lack of logic to it. I went through
each step to isolate the problem (and I'm not exactly a beginner), but
each step defied logic.

  I *still* don't understand how it could have done it, and anyone who
thinks they can explain it is kidding themselves. I agree with Bill
that the most likely cause was the modem... but how? It's all very
well to throw around locked ports and error correction... but how? Why
did it do it in Telemate, using the same defaults for both a wazoo and
a BBS connect? How can you set up a modem to do that that?

 BV> , and he has also bought a new yum-cha computer which seems
 BV> schizoid.

  It was the old 386. The cruellest cut was that it went bad the day
I bought the new computer, and I wanted to get it sorted out before I
copied the whole thing across... on the off chance that it was a
virus. It's working in here with no problems.

 BV> You guy's are MAD for even attempting to diagnose it remotely.
 BV> Why do you think I've been quiet. You've been suckered.

  Not at all. It really happened, just as I said, and it was cured
when I modified the autoexec.bat file. I don't think Rod and Bill
understand how simple TinyPoint really is... it just uses Telix. It
also worked with my VB freq program that uses Telemate, and failed on
the Telemate BBS connect. It has something to do with the difference
between the wazoo connect and the BBS connect - something that both
Telix and Telemate do similarly - and I do not have a clue what.

  No one here has said anything that makes sense, in detail. Bill's
trust in magic init strings is touching, but unfounded... especially 
when I was using *his* string, anyway.

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

---