Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!munnari.oz.au!metro!atom2!ian
From: ian@atom2.LHRL.OZ.AU (Ian Crakanthorp)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NCSA Telnet and ISOLINK BICC 4113 Ethernet card
Keywords: ISOLINK, BICC, NCSA Telnet
Message-ID: <63@atom2.LHRL.OZ.AU>
Date: 26 Feb 91 03:59:26 GMT
References: <60@atom2.LHRL.OZ.AU> <1991Feb21.132554.23910@unipalm.uucp>
Reply-To: ian@atom2.UUCP (Ian Crakanthorp)
Organization: Australian Nuclear Science & Technology Organisation
Lines: 28

|In article <1991Feb21.132554.23910@unipalm.uucp> leo@unipalm.uucp (E.J. Leoni-Smith) writes:
|>ian@atom2.LHRL.OZ.AU (Ian Crakanthorp) writes:
|>
|>>If somebody has got a ISOLINK card and has got the packet driver to work,
|>>could you tell me the parameters you use when you call the packetdriver.
|>>Also the jumper settings of the card.  Any help would be appreciated.
|>
|>1/. I think Russ Nelson said that this was buggy: 
|>
|>2/. We may try it later.
|>
|>3/. Please anyone - post any info to the net so we can all get the latest.

From the responses I received I solved my problem thank you.  It seems I 
had an 8-bit ISOLINK card, for which you use the ISOLAN.COM packetdriver.
The ISOLINK.COM packetdriver is for the 16-bit BICC 4110-2 cards.  The
description says the bug occurs when talking to a VAX and that other people
who have used it haven't complained.  As I dont have a 16-bit card I cannot
tell you how buggy it is.

Thanks


-- 
Ian Crakanthorp                              e-mail: ian@atom.lhrl.oz.au
ANSTO                                        phone : +61 2 543 3365
Australian Nuclear Science                   Fax   : +61 2 543 9273
& Technology Organisation


Brought to you by Super Global Mega Corp .com