On Mon, 21 Aug 2000, Kurth Bemis wrote:
> in win2k pro my modem shows up as com3, irq 3, IO 0x02f8 0x02ff
I'm going to reiterate this point because it is easily overlooked: Windows
actually doesn't really care about the older DOS COM1 through COM4 port
designations. However, it does use a "COM#" naming system for its serial
ports (whereas Linux uses a "ttyS#" naming system). This confuses things
endlessly. And to *really* mix things up, we have the fact that most serial
ports still follow the DOS conventions for hysterical reasons.
To make a long story short (I know, too late): The "COM3" you see in Windows
may not actually mean anything.
This is one of those cases. IRQ 3 with I/O base 0x2F8 is "COM2" under the
old DOS conventions, and "ttyS1" under Linux's default config.
> in linux /dev/ttyS1 is the device that corresponds to that IRQ and that IO
> address...
Yup. Again: Linux, by default, configures the first four serial ports to
match the old DOS conventions, on the theory that most people use them. (Why
do most people use them? Because OSes like Linux use those values by
default...)
Also, remember that Linux starts numbering serial ports at zero (ttyS0) but
DOS started at one (COM1).
> however ttyS2 is the device that should work!...
What is your basis for that statement? The "COM3" in Windows? If so, see
above about endless confusion. :-)
Also, we never found out: Is this a Plug'N'Pray device, or an old-fashioned,
Set'N'Work (i.e., jumpered) device?
> and it tells me that the resources are in use by another entry......how do
> i disable the entry that is already using that IO address...or do i want to?
"No" to the last question. The resources are in use by ttyS1, which
corresponds to DOS's COM2, which corresponds to Win9X's COM3 (on your system),
which corresponds to what your modem is apparently configured as.
If you really, *really* wanted to, you could use
setserial /dev/ttyS1 uart none
to disable the default configuration for the ttyS1 port. You could then
configure ttyS2 with the settings you want.
But you don't want to do that. Trust me. :-)
One last thing: When all is said and done, you will likely want to create a
symlink as /dev/modem to point to whatever /dev/ttyS? device you ended up
using.
Hope this helps!
--
Ben Scott <[EMAIL PROTECTED]>
| "He who fights monsters should see to it that in the process he himself |
| does not become a monster." -- Frederick Wilhelm Nietzsche |
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
