On Fri, 24 Mar 2000, Jesse Marlin wrote:
/dev/cua0 /dev/cua1 /dev/cua2 /dev/cua3
are COM1 thru COM4 you need to make sure that /dev/modem points to the correct device COM port. I think the definition of a WinModem is simply a modulator. Error correction and protocols are handled in a driver usually written for Windows, whereas a REAL modem has this stuff in hardware and are usually more expensive. Linux has support for the latter but none for the former (yet).
Since Windows finds the modem in question on COM1:, probably Linux could find it ad /dev/cua0. To do that: rm /dev/modem ln -s /dev/cua0 /dev/modem And now you should have a modem at /dev/modem, IF your modem is supported. Winmodems aren't supported. That's because they are so crappy the manufacturers won't tell anyone the truth about them, and without that truth nobody can write drivers -and the manufacturers can't be bothered to write drivers for an OS that isn't being run by a few hundred million people. So not only do they not have Linux support, they also don't have Mac or WindowsNT or Windows2000 support. As for cheaper - they typically sell for $25 to $60, where a 56K PCI *real* voice/fax/modem can be purchase with a slight bit of ad-watching for $35 to $50. (But if you really want to spend over $100, you can, and you'll get the satisfaction of knowing you paid more.) -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/