Hello all :-)
I've been having intermittant lockups when callers call my BBS through
Binkley, and tonight doing some testing calling in from a second computer, I
found out under what circumstances this happens, but don't know what to
change,(Binkley settings or my modem's INIT. STRING), to correct it. Hopefully
someone here can help.

 When I call in using data compression and error correcting, Binkley answers
fine,(I see "Connect 33600 /Arq/V34/Lapm/V42Bis" on Binkley's
screen), and it
passes the caller to the BBS. If I call in WITHOUT compression or
error-correction, I see "Connect 33600 /V34/None" and Binkley
locks my system
up tighter than a drum everytime,I see "garbage" on the calling
system, and I
have to re-boot to get it going again.
I've also seen entries in the log saying (Connect 2400/None )Which also locks
things up. I've got a caller with a 2400 modem that tries to connect everyday,
and I come home from work to see that the system has been locked up for hours.
I don't know who this is, and have no way to get ahold of them and tell them
to turn compression and error-correcting on. I need to fix this anyways for any
future callers that might call in this way.

 Is there something I can add/subtract from Binkley.cfg that will stop it
from locking up my system, or something I can do to my init string for my
modem that will prevent the lockups when someone calls without compression or
error-correction.

 I use a USR v.e modem, with init. ATZ which is comprised of AT&F1 only.
 I'm using Binkleyterm/win32 ver. 2.60 with Binkshim and Wildcat5 using Win'95
Thanks alot,
Rick

... I'll have what the guy on the floor is having...  
___ Blue Wave/QWK v2.12

--- Big Ted 1.1 for Wildcat/5