Just ran into this: replaced my hub with a new one,
and one of my machines no longer worked on the network.
Apparently, with Net.tulip, you have to now put the “-w100”.
Now everything works. 
This may save someone grief who runs into the problem later.
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/
What type of hub and what make of tulip do you have? What version
of the driver are you running?
Previously, Robert Krten wrote in qdn.public.qnx4:
Just ran into this: replaced my hub with a new one,
and one of my machines no longer worked on the network.Apparently, with Net.tulip, you have to now put the “-w100”.
Now everything works. >This may save someone grief who runs into the problem later.
Cheers,
-RK–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/
Hugh Brown <hsbrown@qnx.com> wrote:
What type of hub and what make of tulip do you have? What version
of the driver are you running?
It’s a new-fangled “switch” (the guy at Komputer Korner sez they don’t make “dual
speed hubs” any more). It’s a “StarTech” DS16105, “Fast Ethernet Switch”.
I didn’t configure it, he said it would work right out of the box.
The Tulip is a netgear FA310TX card. (If you give me additional commands
to run against it, I can give you more details).
Driver is
//6/bin/Net.tulip Net.tulip 4.25Q Aug 30 1999
Cheers,
-RK
Previously, Robert Krten wrote in qdn.public.qnx4:
Just ran into this: replaced my hub with a new one,
and one of my machines no longer worked on the network.Apparently, with Net.tulip, you have to now put the “-w100”.
Now everything works. >This may save someone grief who runs into the problem later.
Cheers,
-RK–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/
I’ve seen this at at customers site b4 also. It seems that the autodetect
doesn’t like some routers and or switches. You may also need to set the
full or half duplex mode via command line switch.
Paul
“Robert Krten” <rk@parse.com> wrote in message
news:bhu304$eeo$1@inn.qnx.com…
Just ran into this: replaced my hub with a new one,
and one of my machines no longer worked on the network.Apparently, with Net.tulip, you have to now put the “-w100”.
Now everything works. >This may save someone grief who runs into the problem later.
Cheers,
-RK–
[If replying via email, you’ll need to click on the URL that’s emailed to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/
I sent Rob the latest tulip driver, and it seems to have solved the problem.
Previously, Paul Vander Byl wrote in qdn.public.qnx4:
I’ve seen this at at customers site b4 also. It seems that the autodetect
doesn’t like some routers and or switches. You may also need to set the
full or half duplex mode via command line switch.Paul
“Robert Krten” <> rk@parse.com> > wrote in message
news:bhu304$eeo$> 1@inn.qnx.com> …
Just ran into this: replaced my hub with a new one,
and one of my machines no longer worked on the network.Apparently, with Net.tulip, you have to now put the “-w100”.
Now everything works. >This may save someone grief who runs into the problem later.
Cheers,
-RK–
[If replying via email, you’ll need to click on the URL that’s emailed to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/