djc@duke.cs.duke.edu (David J. Cherveny) (11/06/90)
We've been using BYU's version 2.01 Novell to packet driver interface, version 7 packet drivers ( ni5210 ) and Clarkson's version of telnet, CUTCP. It works most of the time be we occasionally have the workstation go read with a network connection message from Novell: NETWORK ERROR on server PLUTO: Connection no longer valid A)bort, R)etry or C)ancel? ( PLUTO is Novell file server ). Only a reboot seems to cure it. Sever no longer "sees" the workstation. You can control-break out. Trying to run CUTCP while in this state gets you: Board initialization failed!. Error code=-1 It seems to happen with or without Telnet being active. BYU's IPX and appropriate v7 packet driver is being used of course and all works fine most of the time. No other network programs ( ie non-packet driver ones ) are being started. It sounds like the packet driver and/or the card is getting confused. Kelly at BYU says their new 3.0 version of the packet interface may fix it but it is not freeware as was the version 2 stuff. Any ideas? David Cherveny djc@rm2000.mc.duke.edu (919)684-6804
nelson@sun.soe.clarkson.edu (Russ Nelson) (11/06/90)
In article <657839430@lear.cs.duke.edu> djc@duke.cs.duke.edu (David J. Cherveny) writes:
We've been using BYU's version 2.01 Novell to packet driver interface,
version 7 packet drivers ( ni5210 ) and Clarkson's version of telnet,
CUTCP.
It works most of the time be we occasionally have the workstation go
read with a network connection message from Novell:
It sounds like the packet driver and/or the card is getting confused.
It's the packet driver. There's a note in read.me about it. You need
to reassemble the packet driver with DAN EQU 0. I don't know exactly
what the problem is, but it doesn't appear on all ni5210's, just some.
I'm working with someone to find the problem. If anyone else would
like to help, send me mail.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.AJGREEN%IRLEARN@PUCC.PRINCETON.EDU (Arthur Green) (11/07/90)
As far as I can remember, BYU passed the distribution rights on to some software company and hence the freeware licence for that release disappeared. I'm not certain what has happened since - BYU may have taken it back onto themselves. I'll check if you like. - AG
AJGREEN%IRLEARN@PUCC.PRINCETON.EDU (Arthur Green) (11/07/90)
Apologies for that last message - I didn't check to see where the reply
was going to.
- Arthur Green
- University College Dublin Computing Services -- AJGREEN@IRLEARN.BITNET --
AJGREEN@IRLEARN.UCD.IEnelson@sun.soe.clarkson.edu (Russ Nelson) (11/08/90)
In article <9011070909.aa05482@louie.udel.edu> AJGREEN%IRLEARN@PUCC.PRINCETON.EDU (Arthur Green) writes:
As far as I can remember, BYU passed the distribution rights on to some
software company and hence the freeware licence for that release
disappeared. I'm not certain what has happened since - BYU may have
taken it back onto themselves. I'll check if you like.
Just to make sure no one gets confused here, but the BYU 2.whatever
code is still freely copyable. It's the BYU 3.0 code that was
licensed to Atlantix. Kelly McDonald <kelly@dcsprod.byu.edu> has
permission from Atlantix to sell it separately.
I don't know what the difference between 2.? and 3.0 is, nor why
anyone would want 3.0, since I've never heard of anyone having
problems with the 2.?. Actually I had one person blame 2.? for long
timeouts after unplugging from the network. I don't know he's right,
or if he is, if 3.0 fixes that.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.