Newsgroups: bit.listserv.novell
Date:         Wed, 30 Dec 1992 21:59:21 -500
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Richard Holbo <holbor@CCMAIL.ORST.EDU>
Subject:      Re: ODIPKT/FTPBIN/TN3270

In article <NOVELL%92122913502946@SUVM.SYR.EDU> you write:
>   In my current attempt to utilitize the SMC Elite 16 Plus, ODI Drivers,
>the ODIPKT driver, and FTPBIN/TN3270 to see if I can get them to work
>together.  My preliminary attempt failed as the FTPBIN did not see my
>ODIPKT as a valid EtherNet driver. I have the Config.tel looking for a
>packet driver.
>

STEPHEN....

Since I JUST figured out how to do this, I'll send my current config.  I'm
not sure on all the details, but this setup works for me.  Also CUTCP, and I
think NCSA will do a search for the Packet driver interrupt, so you need not
specify exactly what the interrupt is in the Config.tel.  My network's
config.tel file is set for 60, but I use 6f and 6e on most of the packet
drivers.  CUTCP has no trouble finding and using the packet driver.  I also
use QVTNET, which is a LOT more picky about you telling it what the
interrupt is.  Anyway here the relevant parts of my autoexec.bat and net.cfg
with "some" explanation.

        LSL
        SMCPLUS
        LH ODIPKT 0 111
        LH PKTINT
        LH IPXODI

IMPORTANT !!! notice that there are TWO options for the ODIPKT driver the
first is the "virtual" card number, and the second is the interrupt number
in DECIMAL!!!!  If you watch the SMCPLUS driver load you will see that it
tells you something like:

SMC LAN Adapter MLID v2.11 (920406)
Copyright 1992 by Standard Microsystems Corp. All rights Reserved.

EtherCard PLUS16 (SMC8013EP)
Int 10, Port 280, Mem C8000, Node Address C0107424
Max Frame 1514 bytes, Line Speed 10 Mbps
Board 1, Frame ETHERNET_II
Board 2, Frame ETHERNET_802.3

Well the "virtual" card 0 is Board 1 as reported by the smcplus driver. So
ODIPKT 0 111 would attach the packet driver to the Ethernet_II frame type
with a software interrupt of 6f. Easy right :-)

Here's the Net.Cfg that I am using.
#
#       NET.CFG File for SMCPLUS

#Link Support
        Buffers 10 2048
#       Mempool

Protocol IPX
        Bind SMCPLUS
#       Sessions

Link Driver SMCPLUS
        Port #1 280 20
        Mem #1 000c8000 2000/10
        Int #1 10
        Protocol IPX 8137 Ethernet_II
        Frame Ethernet_II
        Frame Ethernet_802.3

Preferred Server = LONDON
Show Dots = ON

#
#       NET.CFG end
#

        I put the second Frame type in for this explanation, as I do not
actually use it, but you could pipe your IPX throug that frame type if you
want.  I do not know what all the options behind the port, and mem options
are, as they came on the superdisk from SMC I used them.

        Hope this helps.

                 =========================================
                 Richard Holbo              (503) 737-0952
                 Systems Analyst
                 Oregon State University Libraries
                          holbor@ccmail.orst.edu
                 =========================================
                You're looking at the Library of the Future
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU