[ale] Linux can't see modem

[Jim Philips]

Thanks to Christopher.

I made some progress. The modem is a plug 'n play device. I went through all the
docs on isapnp and set up an isapnp.conf file. The device is now recognized at
bootup. And after all that, it doesn't behave any differently when I actually
try to use it.

And it turns out there is a diagnostic tool in Win95 (imagine that!). Go to the
control panel and click on modems. There is a tab called "Diagnostics". You can
select the modem and click on "More Info". If the modem is not busy, it will
dump information from several Hayes commands. Nothing about Winmodem. It does
say that it's plug 'n play.

Anyway, I know a little more about what ISN'T the problem.

Christopher Fowler wrote:

> In dos mode without windows running, try:
>
> echo ata > com[X]
>
> see if the modem responds with noise.  If not, it may be WinBlows modem that
> will not work under Linux.
>
> Chris
> -----Original Message-----
> From: Jim Philips <rebus at mindspring.com>
> To: Atlanta Linux Enthusiast <ale at cc.gatech.edu>
> Date: Sunday, May 10, 1998 5:36 PM
> Subject: [ale] Linux can't see modem
>
> >Ahh...the joys of setting up a new computer! I have solved all my other
> >hardware problems, but Linux is having trouble seeing my modem. It is a
> >no-name modem that came with the computer, a Quantex 333mhz. No
> >documentation, so I don't know if it's a dreaded "Winmodem". Port number
> >and IRQ are standard at port 2 and IRQ 3. Minicom never manages to
> >initialize. It just sits there. I used setserial to refine port settings
> >and everything is correct. As a test, I tried installing the modem that
> >worked on my old computer. Minicom just crawled through the init string,
> >but wouldn't finish and I couldn't dial. I am at a dead end. Are there
> >any diagnostics I can run to tell me what is happening? I'll settle for
> >diagnostics in Windows that would tell me whether or not this is a
> >Winmodem. Win95's Hyperterminal seems like a useless beast in this
> >situation.
> >