GA7779@SIUCVMB.BITNET (03/25/91)
Greetings again. Thanks to those of you who responded to my query concerning implementing ka9q as an ethernet to tokenring router. I think that I have obtained all the information that I need for that function. Now for the new twist.... Is the IBMTOKEN.COM packet driver broken? It never finishes opening the interface. JUst hangs. I have version 1.2 of the IBM Net Support programs and versions 7 and 8 of the packet driver. Neither will actually work with this TRUE BLUE token ring card.... IBM diagnostics says that both the card and the ring is ok. Any pointers? One person suggested that they use the ipx version ov the program. What type of performance loss can be anticipated using this package? Desparately seeking any advice that will come my way and MANY thanks in advance. Dan Ellison internet: ga7779@siucvmb.cdale.siu.edu Researcher II, Molecular Science Program Southern Illinois UNiversity at Carbondale Carbondale, IL (618) 453-7321
MARC@unb.CA (03/26/91)
On Mon, 25 Mar 91 12:05:35 AST GA7779%SIUCVMB.BITNET@cunyvm.cuny.edu writes: > > Is the IBMTOKEN.COM packet driver broken? It never finishes opening > the interface. JUst hangs. I have version 1.2 of the IBM Net Support > programs and versions 7 and 8 of the packet driver. Neither will > actually work with this TRUE BLUE token ring card.... IBM diagnostics > says that both the card and the ring is ok. Any pointers? One person > suggested that they use the ipx version ov the program. What type of > performance loss can be anticipated using this package? Desparately > seeking any advice that will come my way and MANY thanks in advance. > I could not get IBMTOKEN.COM from version 8 to work. However, the driver from version 7 works for us. We load it as follows: ibmtoken 0x66 0 | |__ card # ( you could have two token-ring cards) |______ software interrupt vector ( between 60 and 7f) Also, version 6 worked ok but would not recognize the last parameter for the card number (default was 0). marc ------- Marc Levesque Computing Services University of New Brunswick Fredericton, Canada marc@unb.ca
BHOLMES@CMS.CC.WAYNE.EDU (03/26/91)
It won't work on a true blue IBM XT, but AT class or above is fine as far as I know. I'm not sure about the 9.x driver though. ------------------------- Original Article ------------------------- Is the IBMTOKEN.COM packet driver broken? It never finishes opening the interface. JUst hangs. I have version 1.2 of the IBM Net Support programs and versions 7 and 8 of the packet driver.
nigam@mwunix.mitre.org (Alok Nigam) (03/26/91)
Does this packet driver work with other token ring cards (Proteon) or are other token ring packet drivers available? -- Alok C. Nigam (703) 883-6751 nigam@mitre.org
jbvb@FTP.COM ("James B. Van Bokkelen") (03/28/91)
Does this packet driver work with other token ring cards (Proteon) or
are other token ring packet drivers available?
The IBMTOKEN packet driver from Clarkson presents a Class 1 (DIX Ethernet)
interface to the world, and contains code which re-formats IP and ARP
packets to suit the RFC 1042 encapsulation used on 802.5. It should
be able to talk IP and ARP with other 802.5 hosts pretty well, but don't
expect it to know how to re-format other protocols. It also has a cache
for RIF information, which is needed to work through IBM source-routing
ring bridges. It is this cache which can come into conflict with ARP
cache timeouts and size in the Ethernet protocol stack, which is why
we don't support its use with PC/TCP.
The only Class 3 (native 802.5) Packet Driver I know of is the DIS_PKT.GUP
adapter module we ship with our Packet Driver version of PC/TCP (an
enhancement of the one released as freeware), which allows use of 802.5
NDIS drivers. It can talk to other things on 802.5 just fine too. Because
of the almost universal availability of ASI (LAN Support Program) drivers
for 802.5 cards and the nearly complete absence of Class 3 protocol stacks
has left little demand for board-specific packet drivers for 802.5 cards.
James B. VanBokkelen 26 Princess St., Wakefield, MA 01880
FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901