On Sunday 14 January 2001 01:25, you wrote:
> My BIOS is set to non-PnP. My ISA (real) modem can be
> jumpered to a specific IRQ, or to PnP. It's currently set to
> PnP, which works fine in Win98. Linux is a different story.
I think you'll have a more successful time if you jumper it to use a specific
IRQ / comm port. Doublecheck your configuration - usually you'll have the
modem on one IRQ/comm port and the mouse on another. If the mouse is already
working on one IRQ, choose the other one :).
>
> But when I try to connect to the Internet in KDE, I'm told
> that the modem "won't respond" to either /dev/ttyS0 or to
> /dev/modem (which would be the same, thanks to modemtool).
/dev/modem is usually a symbolic link to either /dev/ttyS0 or /dev/ttyS1,
whichever your modem is on. If your modem is on 'com 1' (in windows/dos) then
you should use /dev/ttyS0.
> If I try ttyS1 or anything else, I'm told that the device is
> "busy", so it knows something is different about ttyS0.
It's possible that /dev/ttyS1 is your mouse. It's busy :).
Like I said, the approach I would take first is to jumper the modem to use
the 'other' comm port (most systems have two of these, although it is
possible to have four total). You can try echoing characters to the modem
device from the command line if you want to check if it's hooked up right.
Alternatively try interfacing with the modem through 'minicom' which should
be installed on your system. It's a terminal-based comm program which is
pretty easy to use. At least you should be able to type out somehting like
"ATDT xxxxxxx' to see if the modem dials.
> Miark
--
------------------------------------------------------------------------
David E. Fox Thanks for letting me
[EMAIL PROTECTED] change magnetic patterns
[EMAIL PROTECTED] on your hard disk.
-----------------------------------------------------------------------
