My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me. I’ve slain
devc-ser8250 and set it to recognize my modem, but I keep getting the
message ‘connection failed’ from phdial. Qtalk hasn’t been much help; I
tell it which port to use, etc. but nothing appears in the terminal when I
type, and so I have no idea how my modem is responding.
Any help would be greatly appreciated.
Hi Robert,
Is the modem a plug and play modem? If so turn off plug and play OS in the
BIOS.
Erick.
Robert Barker <rb@price.co.fn> wrote:
My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me. I’ve slain
devc-ser8250 and set it to recognize my modem, but I keep getting the
message ‘connection failed’ from phdial. Qtalk hasn’t been much help; I
tell it which port to use, etc. but nothing appears in the terminal when I
type, and so I have no idea how my modem is responding.Any help would be greatly appreciated.
I’m afraid that its not a PNP modem. Also, could someone tell me how
exactly Qtalk works? Unless I put it into ‘local echo’ mode (or some-such),
nothing I type appears in the terminal.
Hardware Support Account <hw@qnx.com> wrote in message
news:99njvd$arp$1@nntp.qnx.com…
Hi Robert,
Is the modem a plug and play modem? If so turn off plug and play OS in
the
BIOS.Erick.
Robert Barker <> rb@price.co.fn> > wrote:
My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me. I’ve
slain
devc-ser8250 and set it to recognize my modem, but I keep getting the
message ‘connection failed’ from phdial. Qtalk hasn’t been much help; I
tell it which port to use, etc. but nothing appears in the terminal when
I
type, and so I have no idea how my modem is responding.Any help would be greatly appreciated.
I have this exact same modem on my system at home (running QNX6 also)
It is COM3: on my Windows system. This means that it shares the interrupt
with COM1 (builtin to the motherboard)
When I slay and restart devc-ser8250, I set it up for all 3 of my serial
ports.
I believe that in order to properly share serial interrupts like this at
least 2 things have to be true…
a. The hardware supports this - i.e. the motherboard is designed so that the
on-board port AND the ISA-based port can both trigger the interrupt properly
without causing hardware interference with each other (as I understand it,
it is impossible to do this with two seperate ISA-based cards because of the
design of the ISA bus interrupt lines (active high) )
b. (I am guessing here) A single instance of devc-8250 should be running
both ports that share the interrupt.
BTW. My modem works just fine, and has ever since the initial version of
QNX6 distributed at the QNX2000 conference last year…
Robert Barker <rb@price.co.fn> wrote in message
news:99q3q5$d5n$1@inn.qnx.com…
I’m afraid that its not a PNP modem. Also, could someone tell me how
exactly Qtalk works? Unless I put it into ‘local echo’ mode (or
some-such),
nothing I type appears in the terminal.Hardware Support Account <> hw@qnx.com> > wrote in message
news:99njvd$arp$> 1@nntp.qnx.com> …
Hi Robert,Is the modem a plug and play modem? If so turn off plug and play OS in
the
BIOS.Erick.
Robert Barker <> rb@price.co.fn> > wrote:
My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me. I’ve
slain
devc-ser8250 and set it to recognize my modem, but I keep getting the
message ‘connection failed’ from phdial. Qtalk hasn’t been much help;
I
tell it which port to use, etc. but nothing appears in the terminal
when
I
type, and so I have no idea how my modem is responding.Any help would be greatly appreciated.
\
COM3 with an address of 03E8h, irq 4? Huh… I believe my hardware is good;
it works perfectly with Windows. This is getting somewhat weird. Any ideas
on the Qtalk thing? Or does it need to be in ‘local echo mode’?
Thanks
Bob
Steve Munnings, Corman Technologies <steve@cormantech.com> wrote in message
news:99q9ie$gmh$1@inn.qnx.com…
I have this exact same modem on my system at home (running QNX6 also)
It is COM3: on my Windows system. This means that it shares the interrupt
with COM1 (builtin to the motherboard)When I slay and restart devc-ser8250, I set it up for all 3 of my serial
ports.I believe that in order to properly share serial interrupts like this at
least 2 things have to be true…a. The hardware supports this - i.e. the motherboard is designed so that
the
on-board port AND the ISA-based port can both trigger the interrupt
properly
without causing hardware interference with each other (as I understand it,
it is impossible to do this with two seperate ISA-based cards because of
the
design of the ISA bus interrupt lines (active high) )
b. (I am guessing here) A single instance of devc-8250 should be running
both ports that share the interrupt.BTW. My modem works just fine, and has ever since the initial version of
QNX6 distributed at the QNX2000 conference last year…
Robert Barker <> rb@price.co.fn> > wrote in message
news:99q3q5$d5n$> 1@inn.qnx.com> …
I’m afraid that its not a PNP modem. Also, could someone tell me how
exactly Qtalk works? Unless I put it into ‘local echo’ mode (or
some-such),
nothing I type appears in the terminal.Hardware Support Account <> hw@qnx.com> > wrote in message
news:99njvd$arp$> 1@nntp.qnx.com> …
Hi Robert,Is the modem a plug and play modem? If so turn off plug and play OS
in
the
BIOS.Erick.
Robert Barker <> rb@price.co.fn> > wrote:
My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me. I’ve
slain
devc-ser8250 and set it to recognize my modem, but I keep getting
the
message ‘connection failed’ from phdial. Qtalk hasn’t been much
help;
I
tell it which port to use, etc. but nothing appears in the terminal
when
I
type, and so I have no idea how my modem is responding.Any help would be greatly appreciated.
\
A little more info - I got qtalk to work, somewhat. I can make the modem
dial, send commands (while in local echo mode), but I’m still not seein’
responses. The dialer still dies at ATZ, though it seems to take quite a
long while there. Any more information or advice would be greatly
appreciated.
Bob
Robert Barker <rb@price.co.fn> wrote in message
news:99sdeg$2m6$1@inn.qnx.com…
COM3 with an address of 03E8h, irq 4? Huh… I believe my hardware is
good;
it works perfectly with Windows. This is getting somewhat weird. Any
ideas
on the Qtalk thing? Or does it need to be in ‘local echo mode’?
Thanks
BobSteve Munnings, Corman Technologies <> steve@cormantech.com> > wrote in
message
news:99q9ie$gmh$> 1@inn.qnx.com> …
I have this exact same modem on my system at home (running QNX6 also)It is COM3: on my Windows system. This means that it shares the
interrupt
with COM1 (builtin to the motherboard)When I slay and restart devc-ser8250, I set it up for all 3 of my serial
ports.I believe that in order to properly share serial interrupts like this at
least 2 things have to be true…a. The hardware supports this - i.e. the motherboard is designed so that
the
on-board port AND the ISA-based port can both trigger the interrupt
properly
without causing hardware interference with each other (as I understand
it,
it is impossible to do this with two seperate ISA-based cards because of
the
design of the ISA bus interrupt lines (active high) )
b. (I am guessing here) A single instance of devc-8250 should be running
both ports that share the interrupt.BTW. My modem works just fine, and has ever since the initial version
of
QNX6 distributed at the QNX2000 conference last year…
Robert Barker <> rb@price.co.fn> > wrote in message
news:99q3q5$d5n$> 1@inn.qnx.com> …
I’m afraid that its not a PNP modem. Also, could someone tell me how
exactly Qtalk works? Unless I put it into ‘local echo’ mode (or
some-such),
nothing I type appears in the terminal.Hardware Support Account <> hw@qnx.com> > wrote in message
news:99njvd$arp$> 1@nntp.qnx.com> …
Hi Robert,Is the modem a plug and play modem? If so turn off plug and play OS
in
the
BIOS.Erick.
Robert Barker <> rb@price.co.fn> > wrote:
My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me.
I’ve
slain
devc-ser8250 and set it to recognize my modem, but I keep getting
the
message ‘connection failed’ from phdial. Qtalk hasn’t been much
help;
I
tell it which port to use, etc. but nothing appears in the
terminal
when
I
type, and so I have no idea how my modem is responding.Any help would be greatly appreciated.
\
Robert Barker <rb@price.co.fn> wrote in message
news:99sdeg$2m6$1@inn.qnx.com…
COM3 with an address of 03E8h, irq 4? Huh… I believe my hardware is
good;
it works perfectly with Windows. This is getting somewhat weird. Any
ideas
on the Qtalk thing? Or does it need to be in ‘local echo mode’?
Thanks
Bob
Are you telling me that that is where your modem is? or asking where mine
is?
Mine is indeed at 03E8, irq 4 and also works just fine under Windows 98 SE
I am not claiming that anything is wrong with your hardware, my drift is
that maybe you have to have a single instance of devc-ser8250 controlling
both /dev/ser1 and /dev/ser3
(Maybe you are already doing that?)
Mine also works just fine with QNX6 under the following scenario:
I am positive that ser1 and ser3 share the same interrupt - irq 4
I believe (though I am not absolutely sure) that - unless a single instance
of devc-ser8250 is running both ports that share the interrupt - the fact
that there are two different serial ports with the same interrupt can and
might screw up your communications.
This is, however, only one thought about what might be wrong.
There are others. (Believe me, I have debugged enough modem and serial
problems on QNX2, and QNX4 to last me a long, long while!)
Your subsequent post (to the one I am replying to) seems to indicate that
qtalk (and by implication, the driver) is not seeing any received data.
The “local echo” is an echo to the screen of the data sent to the serial
port.
If you were getting data back on the receive side, you would see your
characters “doubled” as in AATTZZ
Is is also possible to configure the modem to not echo command characters
(the norm is to echo them), and this might also be a potential source of
your problem.
The command “ATE1” to the modem turns command echo on, and “ATE0” turns it
off
Also, maybe (under qtalk) try an “ATI4” and see what information comes
back - is there any??
The problem might also be flow-control.
But, just maybe, because of shared interrupts, the driver is not seeing the
interrupt to tell it that a received character is available to be read?
Steve Munnings, Corman Technologies <> steve@cormantech.com> > wrote in
message
news:99q9ie$gmh$> 1@inn.qnx.com> …
I have this exact same modem on my system at home (running QNX6 also)It is COM3: on my Windows system. This means that it shares the
interrupt
with COM1 (builtin to the motherboard)When I slay and restart devc-ser8250, I set it up for all 3 of my serial
ports.I believe that in order to properly share serial interrupts like this at
least 2 things have to be true…a. The hardware supports this - i.e. the motherboard is designed so that
the
on-board port AND the ISA-based port can both trigger the interrupt
properly
without causing hardware interference with each other (as I understand
it,
it is impossible to do this with two seperate ISA-based cards because of
the
design of the ISA bus interrupt lines (active high) )
b. (I am guessing here) A single instance of devc-8250 should be running
both ports that share the interrupt.BTW. My modem works just fine, and has ever since the initial version
of
QNX6 distributed at the QNX2000 conference last year…
Robert Barker <> rb@price.co.fn> > wrote in message
news:99q3q5$d5n$> 1@inn.qnx.com> …
I’m afraid that its not a PNP modem. Also, could someone tell me how
exactly Qtalk works? Unless I put it into ‘local echo’ mode (or
some-such),
nothing I type appears in the terminal.Hardware Support Account <> hw@qnx.com> > wrote in message
news:99njvd$arp$> 1@nntp.qnx.com> …
Hi Robert,Is the modem a plug and play modem? If so turn off plug and play OS
in
the
BIOS.Erick.
Robert Barker <> rb@price.co.fn> > wrote:
My AOpen FM/ITU-2 (ISA hardware-modem) isn’t workin’ for me.
I’ve
slain
devc-ser8250 and set it to recognize my modem, but I keep getting
the
message ‘connection failed’ from phdial. Qtalk hasn’t been much
help;
I
tell it which port to use, etc. but nothing appears in the
terminal
when
I
type, and so I have no idea how my modem is responding.Any help would be greatly appreciated.
\
Just so you know, the default for qtalk is to NOT have local echo on. It is
assumed that the remote host that you are connected to will echo the
characters that you type IF and when it is ready.
Consider someone is looking over your shoulder while you are logging on.
And what is the system asking you? Your PASSWORD? DO you really wnt that
echoed unconditionally to your local screen?
–
Bill Caroselli - Sattel Global Networks
1-818-709-6201 ext 122
“Robert Barker” <rb@price.co.fn> wrote in message
news:99q3q5$d5n$1@inn.qnx.com…
I’m afraid that its not a PNP modem. Also, could someone tell me how
exactly Qtalk works? Unless I put it into ‘local echo’ mode (or
some-such),
nothing I type appears in the terminal.
Rule number one never ever share serial port
In the bios set Com1 IRQ4 3f8 i/o
Turn off Com2 in the Bios
Set the Modem on Com2 IRQ3 2f8 i/o
SHS <shs@nowhere.com> wrote in message news:99tnqs$8m4$1@inn.qnx.com…
Rule number one never ever share serial port
In the bios set Com1 IRQ4 3f8 i/o
Turn off Com2 in the Bios
Set the Modem on Com2 IRQ3 2f8 i/o
Rule 2: Ignore Rule 1 if you want to, but be prepared to return to Rule 1
anytime things do not work perfectly!
(Sometimes people ( hw and software designers) do actually
do things that make it possible to ignore Rule 1)
Rule 3: Never, ever, forget that both Rule1 and Rule 2 exist! Use as
appropriate.
i.e. be pragmatic!