If you have any Plug-n-Play devices the first thing you should do is tell
your BIOS that your OS is NOT a Plug-n-Play OS. When you see what
an improvement this makes you will realize that it is a true statement.
Best wishes,
jam
----- Original Message -----
From: "Kelley Terry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 01, 2000 2:51 AM
Subject: Re: [newbie] Modem Trouble
> It sounds like you have the wrong irq assigned. Try to find out which
port and
> irq it uses. I had to use windoze to set up my modem. You can find the
> properties in windoze either by right clicking on the mycomputer icon then
> selecting properties or by using the start/programs/accessories/ menu - I
> can't remember which one offhand so try both. In kppp you can set it by
> entering setup-modem. Set the modem for /dev/ttyS1 if your windows was
com 2,
> /dev/ttyS2 for windows port com 3, etc. Use setserial to set the irq:
> setserial /dev/ttyS(number) irq (number). For example on mine it's:
setserial
> /dev/ttyS2 irq 5. You can append this at the end of a startup file:
> /etc/rc.d/rc.local and it will be executed at system start-up.
>
>
>
> On Thu, 31 Aug 2000, you wrote:
> >
> > I have a modem, it is a Diamond SupraMax 56k v.90.
> > Linux finds the modem but it tell me the modem will
> > not respond? I was lead to believe that this modem was
> > not a WinModem, is this wrong?
> >
> > Maybe there is something that I am missing, which is
> > why I am talking to you fine people. I am real new to
> > this, I just got it up and running tonight. My eyes are
> > likely going to fall out soon so I think I may head off
> > to bed now.
> >
> > Thanks for helping me with this annoying problem.
> >
> > Stephen
> >
>
> ----------------------------------------
> Content-Type: text/html; name="unnamed"
> Content-Transfer-Encoding: quoted-printable
> Content-Description:
> ----------------------------------------
>
