X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Tue, 26 Jan 1993 14:36:03 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: ODI ?

>        Is ODI some kind of cruel joke perpatrated by Novell on unspecting
>LAN administrators? We recentlly obtained PathWorks which requires the frame
>type of "Ethernet_II". In addition we are running all our Novell server using
>frame type "Ethernet_802.3". The VAST majority (nearly 100%) of our network
>cards are NE1000 and NE2000 cards.
>        According to the manual "Netware ODI Shell for DOS" that came with
>Novell 3.11, running the two frame type should be a peice of cake.
>Well...... I'm here to tell you that Novell is "out-to-lunch" on this one! I go
   t
>the manual out and followed it explecitly. I have since concluded that the
>manual has no resemblence to reality!
>
>        1) Can the NExxxx cards handle both frame types?
>        2) Has any one been sucsessfull in runnig Ethernet_II and Ethernet_802.
   3
>           on the SAME board at the SAME time?
>                I can run one or the other but not both.
>        3) Could some one please inform Novell that occasionally we really do
>           reley on there manuals and that they should include instructions
>           that really work?
>
>
>One of the many NET.CFG files I'v tried:                Batch File
>------------------------------------------------:    -----------------
>Link Support                                    :       LSL
>        BUFFERS 2                               :       NE2000
>                                                :       IPXODI
>Protocol ipx                                    :       NETX
>                                                :    -----------------
>Link Driver NE2000                              :
>        INT5                                    :
>        PORT 340                                :
>        FRAME Ethernet_II                       :
>        FRAME Ethernet_802.3                    :
>        PROTOCOL IPX 8137 ETHERNET_II           :
>        PROTOCOL IPX 0 ETHERNET_802.3           :
>------------------------------------------------:
>
>        Protocols get bound to Board#1 only and is soley dependent on which
>frame type is listed first!
>
>Any help would be apreciated:
>
>        Paul Anderson                           paul@vax1.iupui.edu
>        Wishard Memorial Hospital               317-630-6419
>        Indiana University Medical Center
-------------
        While we sympathize with your frustrations, this material is covered
by the manuals. Each frame kind activiated for a board produces a virtual
board, and is announced as such when starting the network components. Major
section   Protocol IPX   is needed if, and only if, there are conflicting
choices for frames, and you certainly have that situation. The major heading
by itself does precisely nothing; it serves as punctuation for the minor
heading (must be indented to qualify as "minor") details. See the BIND sub
heading.
        The manuals on NET.CFG can certainly be improved, and I have suggested
this. In the meanwhile some simple deductions are employed to discover how
it works. The "Major" and "minor" heading description is mine, based on how
programs expect to see NET.CFG. That is, a program, say IPX, reads NET.CFG
looking for major headings, and when the interesting one appears it then
reads the minor ones beneath for instructions.
        Stray stuff, such as PB buffers= , are major headings and thus must
be against the left margin. Never jumble major and minor material.
        For more insight on what frame and protocol minor headings do see
the MS-DOS Kermit v3.12 documentation files, particularly MSR312.UPD. Kermit
can use a major heading  Protocol Kermit  and Bind as a minor heading when
it works with ODI.
        For a really good time, unquote, try explaining NDIS Protocol.ini
to someone. Hint: see my guidance in the dis_pkt9.zip archive. Such fun.
        Good luck, and carry on regardless,
        Joe D.