According to the Bitsurfer Pro manual, it requires a VT100 Terminal Emulator.
I don't think minicom fits the bill because it's a VT102. I have no idea what
the difference is, but I do know it doesn't work. When typing commands, both
the recieve and transfer lights flash at what seems to be the same time, and
the command is echoed, but nothing else happens. "AT" doesn't give me an "OK,"
or any message for that matter. I really don't know what's going on here. I'm
using a Siig Twincom Professional card for the serial port set at irq 5, io 3e8.
I couldn't figure out how to disable the 2 com ports on the 386 motherboard,
so I went with tty2 instead of worrying about it. No io ports or irqs are
conflicting as far as I know. Any more ideas? I know I'm kind of going into
the realm of a serial port/modem group, but the subject does apply somewhat
because *everyone* did, at one point, have to get their own modem working.
Thanks for the help...keep it coming :)
Jacob Joseph
On Wed, 11 Aug 1999, Ed Doolittle wrote:
> On Tue, 10 Aug 1999, Jacob Joseph wrote:
>
> > ...
>
> None of the problems you listed above this point are really major.
>
> > Then, after all that, I've got pppd problems. The network
> > script fails. I don't think it's communicating at all with the
> > bitsurfer because it gets no response. And, YES, the modem is
> > connected to ttyS2. I can't test it, however becuase it
> > requires a VT100 terminal.
>
> The linux console is a VT100 terminal. (But I've never heard of a
> modem that sends response codes in VT100 format ... are you sure
> that's the reason you can't test it?) The real issue is talking
> to the modem at the right speed, and getting all the control lines
> correct (I believe RS-232 is now up to 30 or so different control
> lines (joking)). It is possible to do that at the console, but:
>
> > Seyon is one such terminal, but it requires X, which I don't
> > have.
>
> Probably the simplest thing for you to do is to get minicom, a
> character based terminal emulator that will take care of most of
> those details for you. Kermit would too, but it's not for the
> faint of heart. (The problem with kermit is that it does
> everything exactly right. :-)
>
> > I included a few files(maybe I've got something obvious wrong?)
> > to look at. My main priority is simply getting PPP working and
> > then I'll figure out diald.
>
> That's the way to do it.
>
> At first glance your diald.conf looks OK. Before you try diald
> you should make sure you remove certain options from the
> /etc/ppp/options file (actually, don't remove them completely,
> just move them to the files in /etc/ppp/peers/). Things like
> lock, modem, etc. Check the diald man page for a complete list.
>
> Ed
>
> --
> Ed Doolittle <mailto:[EMAIL PROTECTED]>
> "Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
