Very Computer

by **Miika Pulkkin** » Wed, 18 Oct 1995 04:00:00

: I connected two PC with linux and plip thanks to a parrallel cable.
: It works very well.

: But one of them is a 386sx25 and have only 4MB of RAM and i would like to use
: NCSA Telnet and
: crynwr packet drivers under msdos .

: After a few weeks (summer) i'am always at the same point:
: telnet says me that probably the cable is jammed in wire.
: I verified the cable but it seems good.

: Please help-me. Say me how to configure pktdrv and telnet (what to load if
: necessary).

: Thanks to mail me the answer too.

: Sined

We set up such a system last weekend. We also got notices from
the jammed wire, but we solved the problem by changing the IRQ
of SoundBlaster to something else than IRQ 7. IRQ 7 is the
hardware IRQ of LPT1 which you are probably using...

--

Miika Pulkkinen, Lutk/TOL

"Parempi viina paassa kuin rumassa putelissa"

-vanha savolainen sananlasku

"Better booze(liquor) in(side) one's head than in an ugly bottle"

-an old savonian proverb

by **Michael Ricka** » Fri, 20 Oct 1995 04:00:00

>: I connected two PC with linux and plip thanks to a parrallel cable.
>: It works very well.

>: But one of them is a 386sx25 and have only 4MB of RAM and i would like to
use
>: NCSA Telnet and
>: crynwr packet drivers under msdos .

>: After a few weeks (summer) i'am always at the same point:
>: telnet says me that probably the cable is jammed in wire.
>: I verified the cable but it seems good.

>: Please help-me. Say me how to configure pktdrv and telnet (what to load if
>: necessary).

>: Thanks to mail me the answer too.

>: Sined

> We set up such a system last weekend. We also got notices from
> the jammed wire, but we solved the problem by changing the IRQ
> of SoundBlaster to something else than IRQ 7. IRQ 7 is the
> hardware IRQ of LPT1 which you are probably using...

there's also a small bug in the released version of plip.com for ms-dos
machines that means it doesn't work unless you mend it or stick to using a
parallel port at 0x378

Mike

by **Steve Johns** » Mon, 20 Nov 1995 04:00:00

: : I connected two PC with linux and plip thanks to a parrallel cable.
: : It works very well.

: : But one of them is a 386sx25 and have only 4MB of RAM and i would like to use
: : NCSA Telnet and
: : crynwr packet drivers under msdos .

: : After a few weeks (summer) i'am always at the same point:
: : telnet says me that probably the cable is jammed in wire.
: : I verified the cable but it seems good.

: : Please help-me. Say me how to configure pktdrv and telnet (what to load if
: : necessary).

: : Thanks to mail me the answer too.

thanks

by **Brent M Hendric** » Mon, 20 Nov 1995 04:00:00

: thanks

I'm also having trouble with plip, but my problem is that I compiled my
kernel with plip support and added the correct lines to my rc.inet1
file, but I see nothing about plip in the NET-3 section when I
bootup. PPP is listed and it works great, but there is no mention of
plip, so when my rc.inet1 file runs, I get the following messages:

SIOCSIFADDR: no such device
SIOCSIFDSTADDR: no such device
SIOCSADDRT: network is unreachable.

My parallel port is at 0x378 on irq 7, so I'm using plip1.

Last year it worked great when I was using 1.1.90, but I completely
reinstalled this year from the Slackware distribution and this 1.2.1
kernel doesn't seem to like it.

Any ideas?

-Brent

by **Tim S. Pi** » Thu, 23 Nov 1995 04:00:00

> : thanks

> I'm also having trouble with plip, but my problem is that I compiled my
> kernel with plip support and added the correct lines to my rc.inet1
> file, but I see nothing about plip in the NET-3 section when I
> bootup. PPP is listed and it works great, but there is no mention of
> plip, so when my rc.inet1 file runs, I get the following messages:

> SIOCSIFADDR: no such device
> SIOCSIFDSTADDR: no such device
> SIOCSADDRT: network is unreachable.

> My parallel port is at 0x378 on irq 7, so I'm using plip1.

> Last year it worked great when I was using 1.1.90, but I completely
> reinstalled this year from the Slackware distribution and this 1.2.1
> kernel doesn't seem to like it.

> Any ideas?

> -Brent

Yup, this is an easy problem. It's no longer pl0/pl1/etc, now
it's plip1/plip2/etc. So you do an
ifconfig plip1 you.ip.goes.here pointopoint other.end's.ip.here up
route add plip1
And you've got a plip connection going no prob. I still can't get
mine to actually send data without returning "Transmit Timeout(1,87)"
errors on my 386 end. (My 486 is 33 bogomips, my 386 is 3, so I guess
it's possible to loose some bits there :) Anyhow, anyone that can help me
with the delays in plip.c, please do. Thanks

tsp

Very Computer

linux plip to msdos crynwr plip. HOWTO?

linux plip to msdos crynwr plip. HOWTO?

linux plip to msdos crynwr plip. HOWTO?

linux plip to msdos crynwr plip. HOWTO?

linux plip to msdos crynwr plip. HOWTO?

linux plip to msdos crynwr plip. HOWTO?