BBS: Inland Empire Archive
Date: 01-15-93 (15:29) Number: 358
From: MATT ROBERTS Refer#: NONE
To: ALL Recvd: NO
Subj: OPEN COM Conf: (2) Quik_Bas
Hi. There's been some talk about problems with opening the communications
port with OPEN COM for some modems. Some modems seem to
generate a "device time-out", making the sample
TERMINAL.BAS about useless. I got a general note file from
the Microsoft BBS about dealing with such problems (among
other things) and finally got around to experimenting with
it. I was able to use their suggestions to successfully
call a local BBS, and thought others with the same problem
would be interested in the simple change I made to
TERMINAL.BAS.
All I did was change the OPEN COM line, so it reads
OPEN COM2: 9600,N,8,1,CD0,CS0,DS0,OP0 FOR RANDOM AS # 1, LEN=256
The CD0 nulls out the timeout for carrier detect.
CS0 nulls out clear to send
DS0 nulls out data set (?)
OP0 nulls out timeout for open.
I don't guarantee I've got the above exactly right (I'm doing it from
memory), but I think that's the way it goes. Anyway, I was
able to log on with no problems, except that ANSI was no
longer supported. Dunno why, though I haven't tried
compiling to an .EXE and it's possible that it was because
I was doing it from the integrated environment? Dunno.....
Also, I got numeric codes instead of verbose after I
changed it from 1200 to 9600 for the speed.
By the way, if you're calling Microsoft BBS, make sure you're set for a
"direct connect"....the transfer-protocol checking your
modem does may be the reason you can't get on (if you
can't). I can offer the init string that let me get on,
but I don't know if it'll work on your machine. Probably
won't do any major damage though since you can just reset
your modem and you'll be back to the defaults.
Matt
---
---
* Origin: StarCom (1:325/602.8)
