Re: hopefully a good answer to Re: Cornell CUSeeMe Version 1.0 Locks Up

Phil (chrome@lcol.net)
Wed, 24 Jun 1998 05:27:16 -0400


>I just tried to connect to a reflector that is at my office, and I happen
>to know that our router is down. The program hung up on me big time. I
>tried WS_Ping32 and got this:
>
>PING 204.64.168.2 (204.64.168.2): 50 data bytes
>[Timer-BLOCK_SEND]
>timed out
>[Timer-BLOCK_SEND]
>network unreachable from 141.198.1.2: time=269 ms
>[debug] 11002 00 00 00 00
>[data]
>
>So, in some cases, you definitely can get hung up, but this hopefully won't
>happen very often. My standard answer is still very helpful, especially
>when dealing with the older Cornell reflectors, which don't support
>multiple conferences. Also, with QuickConnect turned on, attemping to get
>into a busy reflector is easier. Double click on the reflector entry in
>the phonebook, and if you get "The B-Street is full. Too much partyin' &
>tequila!" message, just hold down the ENTER key to do the OK on the
>message, and then the CONNECT in the phonebook until you finally get
>connected.

I particularly like this feature, especially if your mouse driver has the
option to put the cursor on the default button. When this happens, it's
just a matter of clicking the left button until you're connected or your
patience wears too thin.