Hi, Bill.

BG> BG> Could be either modem at fault here, although my gut reaction is that
BG> it's
BG> BG> the Thunder which is the problem, especially when one considers that
BG> David
BG> BG> has 5 or 6 Thunder callers who connect without any difficulties at all.

BG> FM> Eh? Aren't you contradicting yourself here?

BG> BG> I don't think so.  I can't see any contradiction in the above.

BG> FM> "the Thunder which is the problem"

BG> FM> "Thunder callers who connect without any difficulties"

BG> FM> just seemed to be a contradiction.

BG> Sorry, in retrospect, I could have worded that a bit better, as I see what
BG> you mean now.  Assuming no V.32ter problems with the Courier (and neither
BG> Dave nor anybody else has reported any), and given that several other
BG> Thunder users connect OK with Couriers, it seemed to me that the problem ma
BG> have been with just that one Thunder (which of course, is yours).  Have you

Oh, I see. Thunders in general cf my Thunder.

BG> connected OK at V.32ter with any other Couriers, BTW?

I don't talk to anyone regularly except Paul. I don't know what Glen
Crouch is running in WA, the only other board I've talked to recently.

BG> BG> Very strange.  Must be poltergeists then.

BG> FM> Or the changes he was making at his end, the ROM code maybe. Although I
BG> FM> thought we might have had at least one problem connect after his new
BG> FM> code, didn't really know the dates though.

BG> There was one SDL which appeared to be slightly buggy, and Paul was running
BG> it for a while, but I thought that even though he'd flashed the modem with 
BG> later one, you were still unable to connect at V.32ter.  There was so much
BG> going on at the time that I've forgotten the sequence now.

Yeah, ditto.

Regards, FIM.

 * * Speed scare you?  Use MS-Windoze 3.0!
@EOT:

---