In my experience of Internal modems (2 old ISA 2400, 9600) they produce
an extra com port in the listing on bootup.
I guess that if they dont do this then they wont work, even though they
appear as serial controllers in the PCI device listing?
Should they appear as a /dev/ttyS(n)??
Thanx
Neil - Wanting to buy a 56k EXTERNAL modem
Uncle Meat wrote:
>
> On 09-Jul-99 Gerald Walls opined:
> > A few times I've wondered why someone doesn't write a daemon/driver
> > to
> > replace the Windows-based programs that run these things...
> >
> >> Is it s WinModem?? If yes, you are out of luck: it won't work.
>
> Because:
>
> 1. Each manufacturer (MFR) writes its own version of a driver to satisfy
> the needs of the (non)modem it created.
>
> 2. No (that I know of) MFR will release source code of the drivers.
>
> 3. Some (pseudo)modems have several different versions of the drivers
> realeased for variations of the kludges they've created. In these
> cases a driver created for a 56K (artificial)modem model 1 that was
> released last week may not work with a 56K (artificial)modem model 1
> released week before last.
>
> 4. The above makes it totally impossible for any single driver in linux
> to fix it for all (phony)modems created, makes it just as impossible to
> make a driver for all of the different models from a single MFR, makes
> it virtually impossible to even do so for a single model from a single
> MFR, and without source code all work would require reverse-engineering
> to overcome all proprietary voodoo the MFR used to make it seem to work
> in the first place.
>
> ---
> Failure is not an option. It comes bundled with your Microsoft
> product.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
