“Daniel Szymanski” <szymanski@sanyo-machine.com> wrote in message
news:3CA8C512.2A84708E@sanyo-machine.com…
Some addtional information and questions:
Is there a utility for QNX 4 that can survey your PC and determine
available
interrupts and I/O port addresses?
Not really. There is a free isapnp driver available on QNX ftp site, it can
help
deal with ISA devices, but that driver doesn’t interact with any of the QNX
drivers.
Specifically, for a NIC, I ran nettrap and it returned what should (or
could)
be used, this included the I/O port, but not the interrupt address.
It return what it things is the current resources use by the card,
I beleive on some hardware it can’t find the interrupt (or lets
the driver detect it)
I have
plug and play disabled on my NIC, and have manually set the I/O and inte
INT,
but still have the problem explained above. I do not think it is
guaranteed
that everything returned by nettrap is in fact available, is it?
< Is there another way to confirm what is?
No, you have to look at the hardware in your machine an resolved
all conflict yourself.
Thank you,
Dan Szymanski
Mario Charest wrote:
“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3CA24590.70903@csical.com> …
Daniel Szymanski wrote:
I thought that this 3COM card was “the mother of
all network cards” as far a compatibility with QNX is concerned.
This
is the
first time I have had any problems in using it with QNX.
Actually no. The 3com 509 is the one card for which there is a QNX
driver, but QSSL explicitly recommends against using (due to the
fact
that it has such a pathetically small buffer IIRC).
QNX used to ship with a rather humourous technote regarding the 509
(in
/etc/technotes) but I suspect the lawyers and marketeers have long
since
done away with that technote…
Yeah, if you want to be successfull you have to not tell the thruth ;-(
Rennie