So Bink 2.60 is not as wonderful as you would makeout then , Paul... Even

it has its bugs.



I wonder if it is because they are also using Couriers with it.



=======================================================================

* Forwarded by Russell Brooks (3:640/305.55)

* Area : BINKLEY

* From : Harry McDow, 1:124/1019.1 (Wednesday, 10 April 1996  18:54:14)

* To   : All

* Subj : FREEZE!

=======================================================================

============================================================== *

Message Forwarded by Harry McDow (1:124/4218) * Using : GoldED/386 2.50+

* Area : NET124 (NET124)

* From : Gary Wright, 1:124/1019.1{at}fidonet (Wednesday April 10 1996

15:15) * To : Paul Lentz

* Subj : FREEZE!

* NOTE : Comments by Harry McDow appear at end of message.

============================================================== On Apr

09 06:04 96, Paul Lentz of 1:124/5025.1 wrote:



PL> It took it happening twice to prove it to me. The first time I

PL> woke up from a nap to find it'd been frozen for an hour and a half

PL> :-( after an old link called in without the password we'd used. 2nd

PL> time I watched it and bigger than Dallas it locked up under the same

PL> circumstances.



It looks like you are right. There is a problem with the DOS version.

It appears the lockup is caused by Binkley not writing and/or closing

the log file when you have a password error on an INBOUND call only.



If you notice it will have 0's in the screen display for the calling

system address when the call is over. The same information should be

written to the log file as it is with any other call but for some

reason it doesn't.



Maybe someone who is familiar with the language could take a look at

the routines to handle that situation and figure out the problem since

we have the source code.



For now I have gone back to 2.59 until a fix is available.



Gary



-+- Msgedsq 3.10 + Origin: The TEJAS Saloon BBS * (214) 724-0318 *

14.4k v.32b (1:124/1019.1)



=======================================================================



Hello All!



Could someone verify (Vince?) that DOS Binkley 2.60 does lockup when an

Inbound call produces a password error? It has been reported here in

the Dallas/Ft. Worth area that Binkley locks up when an inbound call

with non-matching passwords or passworded on the receive side and no

password on the calling side will produce a calling system with 0:0/0

and produce a lockup of Binkley?



 \|||||/

 ( o o )

 =====ooooO===(_)===Ooooo=======



 From Harry - Keeper of

 the Net 124 EchoMail Machine



 .oooO Oooo.

 ( ) ( )

 =======\ (=========) /=========

 \_) (_/



... Deep Space Nine: Looks like a Klingon steering wheel.

-!- GoldED/386 2.50+/1054

 - Origin:  TCR'S Revenge - USR DS V.Everything now with V.34.  (1:124/1019.1)



=======================================================================



Russell

--- Terminate 3.00/Pro