Public Message 
Message # 1662 *MM1 TECH Echo*
To      : John A Donaldson
From    : George Hine
Subject : Kterm
Date    : 94/02/03 03:11:06
Next Reply is Message 1678

Dear John:
   While using Kterm I opened a capture file, downloaded the Tech Echo,
and then closed the capture file.  I proceded with a file download and
went to another window to read the just downloaded capture file while
Kterm was still running and found that the file was busy and remained so 
until I terminated Kterm. Would it be possible to change the program to
unlock the capture file when it is closed instead of when the program is 
terminated?        Thanks, George
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/343)


Public Message 
Message # 1678 *MM1 TECH Echo*
To      : George Hine
From    : Warren Hrach
Subject : Re: Kterm
Date    : 94/02/03 09:39:40
Previous Reply is Message 1662   

            On Thursday, February 3rd, 1994 - George Hine wrote:
 
GH> While using Kterm I opened a capture file, downloaded the Tech Echo,
GH> and then closed the capture file.  I proceded with a file download and
GH> went to another window to read the just downloaded capture file while
GH> Kterm was still running and found that the file was busy and remained 
GH> so  until I terminated Kterm. Would it be possible to change the 
GH> program to unlock the capture file when it is closed instead of when 
GH> the program is  terminated?        Thanks, George
 
George,
     I have tested this feature of Kterm both over my null modem and
over a Anchor 2400 modem.  I have used the /t3 port for the null modem
and /t0 port for my Anchor modem.  I find that I have no problems
listing the file in another window even with the capture file still
open (ALT C)  Of course it lists with extra spacing and if I call Ved
and list the file I can set it up with real CR's and then the extra
spacing is gone.
      This is after I close the capture buffer.
Now I have hardware handshaking set but doubt that is what the diff. is, 
maybe it is your 68340 cpu ?  I recall something about the 68340 UG
having new serial drivers for the rs232 ports, could this be it ??
      BTW I recall you mentioned sending me your revised 8 Meg upgrade
documentiation file when you got it debugged. Can you still do this ??
 
-Warren
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/343)


Public Message (Rec)
Message # 1777 *MM1 TECH Echo*
To      : Warren Hrach
From    : Paul Myles
Subject : Re: Modem Speed
Date    : 94/02/05  03:01:00
Next Reply is Message 1786

WH>       Are you using V.42b error control or none ?
WH> -Warren

Warren,
    I have the compression turned off. V.42 is still ON(MNP2-4). I think
this is right. 
                        Paul Myles

--- GEcho 1.00
 * Origin: Zuul's Catacombs, Coraopolis PA  (412) 264-9787 (1:129/164)


Public Message 
Message # 1786 *MM1 TECH Echo*
To      : Paul Myles
From    : Warren Hrach
Subject : Re: Modem Speed
Date    : 94/02/06 12:43:50
Previous Reply is Message 1777   

            On Saturday, February 5th, 1994 - Paul Myles wrote:
 
PM> I have the compression turned off. V.42 is still ON(MNP2-4). I think
PM> this is right. 
 
Paul,
    I have always stuck with V.42b but my ZyXEL will connect with
MNp1-4. I have mnp5 disabled on someone elses advice.
    The biggest thing is the fact I just discovered that RiBBS and lock
baud will work fine, just so long as you disable flow control on the
modem.  I am useing Aciadrv and its /t2 for my bbs along with Nitros9
and the ZyXEL set up with flow control off and lock baud on at 9600.
    The problems with the hardware handshaking are gone and noone
connecting at 12, 24, 9600, 14,400 or 16,800 baud has one bit of char.
loose or up/downloading problem. Previous to this I had hardware
handshaking enabled and the RS232pak could not handle the interupts.
Now with it disabled no more dropped chars. Its great, I am very pleased 
with my ZyXEL at this time.
    So anyone that calls here and had to use v.32 in lieu of v.32b can
just call at v.32b no problem now.
-Warren, RiBBS beta sysop, MM/1 Sales Rep.
 
--- RiBBS v2.10 (Beta) 
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/343)

=*= FIDO ECHO MESSAGES MENU =*=

<1> Scan  \
<2> Read   > OS9 Echo mail             
<3> Leave /
<4> Scan  \