| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: M34F and Terminate 3.00 |
G'day Sam!
-=> In a message on 23 Apr 96 <=-
-=> Sam Benson said this to All <=-
SB> Is there anybody else out there running a Netcomm M34F and Terminate
SB> 3.00. I've got a few problems with Terminate I'd like to resolve.
Yes, me. Sorry the reply has taken so long but my phone line has been out
for over two weeks due to all the rain we've had.
By now you may have even upgraded to Terminate 4.00. I have, it works much
better than the previous version - faster screen writes, no hanging on next
connection after an upload, and some changes to the way it talks to the
FOSSIL. Alas, your problem is something different - but easily fixed...
SB> Specifially they are these:
SB> 1. When I call out, Terminate thinks that someone is ringing in
SB> and displays a message "Incoming Call, Press y to pick up the
phone ??"
SB> or something similar.
This is because NetComm SmartModems use RING for incoming call and RINGING
for outgoing calls; when you make an outgoing call the modem responds with
RINGING but terminate interprets this as RING and prompts you to answer the
call.
This little problem can be fixed simply by selecting "Options",
"Modem and
dialling" then adding a carriage return and a line feed after the Ring
string. The Ring string should be RING^M^J and Terminate will now be able
to distinguish between the RING and RINGING responses of the M34F.
SB> 2. I'm getting a lot of CRC download errors (though this is not
SB> specifically Terminate / the modems problem).
SB> 3. I cna successfully download 99% of a file before something
SB> goes wrong and either my end locks up or the other end locks up and I
SB> have to quit Terminate and start again. I did not say hang-up as I run
SB> Terminate under Windows.
These two problems probably both relate to the fact that you are operating
Terminate under Windows. To allow DOS comms programs to run properly under
Windows you need to make some alterations to you SYSTEM.INI file. I also
strongly recommend the use of a FOSSIL driver such as BNU or X00 and, of
course, a 16550 UART in your serial card.
Below are the relevant excerpts from my SYSTEM.INI file. I have my M34F on
COM2, a 16550 UART in COM2, X00 V1.53a with the DTE speed locked to 115200
and FIFO buffer enabled, and Terminate setup to use the FOSSIL.
The commented lines (;) are show previous settings and comments.
--- SYSTEM.INI ---
[boot]
; comm.drv=comm.drv
; 57,600bps Comm Driver (select 600 baud)
; comm.drv=comm56.drv
comm.drv=CyberCom.Drv
; CyberCom comes with COOEE and has max speed of 115200
CyberCom.drv=comm56.drv
[386Enh]
; device=*combuff
; Cherry Hill VM COM Buffer Driver for use with Terminate
device=chcomb.386
COM2AutoAssign=0
COMBoostTime=30
COM2Base=02F8
COM2Irq=3
COM2FIFO=1
COM2TxSize=16
COM2TxTrigger=8
COM2RxSize=14
COM2RxTrigger=8
COM2Buffer=10000
DMABufferSize=64
--- End of Excerpt ---
BTW if you don't have CYBERCOM.DRV and/or cannot find CHCOMB.386 let me
know and we should be able to tee-up a file transfer between us.
SB> I use ATZ as my initialisation string. The values
It might be useful to try running Terminate under DOS to satisfy yourself
that the problems are only related to Windows.
Feel free to NetMail me if you continue to have problems - I will try to
help if I can.
BFN
_
(_`
._)teve
___ E-mail: slennie{at}cin.gov.au
~~~ PGPWave v1.22a Gamma / PGP 2.6.3ia
... Dinosaurs did not use Terminate. Now they're extinct. Coincidence?
--- Blue Wave/386 v2.30
* Origin: Galaxy GateWay! - Brisbane Valley, Qld, Aust. (3:640/230)SEEN-BY: 50/99 620/243 624/300 640/201 217 230 305 702 820 821 822 823 829 SEEN-BY: 690/660 711/409 413 430 808 809 932 934 949 712/515 713/888 714/906 SEEN-BY: 800/1 @PATH: 640/230 820 711/409 808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.