Re: isapnp

[ichavero en buzon uach mx]

En el howto del modem viene que no se vale utilizar winmodems con Linux, el
porque no se puede.

4.4.  Internal Modems You Must Avoid: winmodems, etc.

  In late 1998, the majority of internal modems don't work with Linux
  since it they are "winmodems" or the like, although they often don't
  state it directly like this.  Such modems turn over much (or even
  almost all) of the work of the modem to the main processor (CPU) chip
  of your computer (such as a Pentium...).  Since only Windows (and not
  Linux) software is provided to do this, it will not work under Linux.

  There are other more precise names than "winmodem".  HSP (Host Signal
  Processor) means that the host processor (your CPU chip) creates the
  code needed to produce the electrical signal on the phone line.  In
  contrast to this, a "controllerless" modem can create the electrical
  signals (but can't control the modem).  It contains no facilities to
  deal with bytes being sent and received.  It can't compress strings of
  bytes; it can't check for errors; it can't put them into packets.  In
  other words it can't control the modem but instead has the CPU do all
  this work using a program for Windows.  If such programs could be
  ported to Linux then there wouldn't be this problem.  Besides the
  above, a modem which doesn't simulate a serial port will not work
  under Linux.

  How do you determine if an internal modem will work under Linux?  It's
  not always easy.  If you can look at the package it came in (or a
  manual) find the section on the package that says something like
  "Minimum System Requirements" or just "System Requirements".  It may
  be in fine print.  Read it closely.  If Windows is listed as one of
  the requirements then it will likely not work under Linux.  Also check
  out modem list <http://www.o2.net/~gromitkc/winmodem.html> which lists
  modems which do and don't work under Linux.

  Otherwise, it may work under Linux if it fails to state explicitly
  that you must have Windows.  By saying it's "designed for Windows" it
  may only mean that it fully supports Microsoft's plug-and-play which
  is OK since Linux uses the same plug-and-play specs (but doesn't
  support them very well as yet).  Being "designed for Windows" thus
  gives no clue as to whether or not it will work under Linux.  You
  might check the Website of the manufacturer or inquire via email.  I
  once saw a web-page that specifically stated that one model worked
  under Linux while implying that another model didn't.

  As far as the author knows, there is almost no effort underway to
  support winmodems in Linux.  You might request that modem
  manufacturers port their code to Linux (or the like).


Arturo Palacios wrote:

> Hace unos dias tuve un modem motorola interno(winmodem)y trate de echarlo a
> andar con los isapnptools. El problema fue que solo identifico un puerto que
> no corresponde a ningun comX en windows, me parece fue la direccion
> 0x0340.Trate de usar el dispositivo /dev/cua1 que no tengo ocupado y con
> setserial modifique el puerto y la interupcion pero jamas pude verlo
> funcionar. Mi pregunta es la siguiente:
> 1.- Es posible configurar estos tipos de modem?
> 2.- Si es que se pudiera, es necesario utilizar los dispositivos /dev/cuaX
> (en su defecto /dev/ttySX) o debo utilizar otro dispositivo?
>
> Hace tiempo configure un modem interno de marca Davicom, el cual con la
> ayuda de los isapnptools se podia configurar debido a que si se podian ver
> las direcciones de los comX (estos en windows)solo que se debia cambiar la
> interrupcion. Si alguien quiere comprar uno de estos adelante, es posible
> trabajar con el en linux.
>
> Alguien puede ayudar.
> Gracias.
>
> Atte: Arturo Palacios
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com