🚀 go-pugleaf

In <6r3vmn$8q7$1@sol6.tvd.be>, "Simon Hampton" <simon.hampton@tvd.be> writes:
>Please stop me going crazy with setting up a little peer network between two
>computers using a co=ax cable.
>
>I've installed MPTS + fix pack to both, and installed peer from the Warp 4.
>The computer with the D=Link card is polling the cable as the little LED
>flashes.  I can't tell about the 3com card as it has no lights.  The 3com
>machine also registers some traffic statistics, so I think there is a bit of
>a connection.
>
>The problemis that neither machine will recognise the other and offer me the
>possibility to use the resources which I have set up to share.
>
>Please give me some advice
>
><simon

I've never used the 3COM card, but a lot has been posted on it about
sonething specific in the setting about 9600 baud or something like it.
My recall is that this a seeminly unrelated deal about serial port baud
rate you have to set in that driver for some reason I can't imagine.
The problem has been, per my recall, specific to the 3COM card(s).

Other than that, it seems you have to be very careful to use a NIC
driver that is really right for your particular NIC card.  This is
specially true if you are using the multi-media cards.  Unless you use
exactly the correct driver for that card, sometines OS/2 can't seem to
get the card cable type right.  For example the generic NE2000 type
driver supplied with OS/2 and the one it thinks is right for your card,
may never be able to get that card off thinking it is a thick cable on
the card instead of the thin cable.  I've had no end of trouble with
trying to get reliable sensing for thin-net coax.

When I finally gave up on thin net and went to 10bT or CAT-5, and got
the EXACTLY right driver from the vendor for my cards, my system came
alive POOF!  Without a hub and all NOTHING.

In my case, I even had to get the latest driver for the cards, two
different ones for two different models of the same company's cards in
this case!  OS/2 thought it could work with either of these as one of
the generic drivers.  It could not...

//-----------------------------
Mike.Luther@ziplog.com
Mike.Luther@f3000.n117.z1.fidonet.org