From: harvey@indyvax.iupui.edu
Subject: Re: Novell and WinQVT/Net (Argggghhhh)
Organization: Indiana University
Date: Thu, 20 Aug 1992 20:09:53 GMT

In article <1992Aug14.194534.14216@kocrsv01.delcoelect.com>, swlodin@kocrsv01.delcoelect.com (Steve Lodin) writes:
>
> **** Posting for a friend who can't get his PC to work ****
>
> I am trying to set up an AST 486/33 to run on an existing Novell network
> (v3.11) WITH the ability to run WinQVT/Net.  I, like others in the past
> and present, am having difficulty making IPX and TCP/IP coexist.  I
> remember a posting several months ago on this subject which suggested
> the following additions to autoexec.bat:
>
>      lsl.com
>      3c507.com -n -w 0x60
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1.
>      odipkt.com
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2.
>      winpkt 0x60 0x63
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3.
>      pktint
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4.
>      ipxodi.com
>      netx.com
>
> When I run this, it seems everything loads into RAM except winpkt, which
> gives a message similar to "packet driver is at segment xxxx,
> there is no packet driver at 0x63".  When I run windows 3.1 after this
> sequence, my machine hangs.

There are several ways to make this work, but this isn't one of them.
Here is one way:

1.	If this is loading without error you are loading the 3C507 packet
	driver.  If the intent is to have an ODI driver actually driving
	the interface, you should be loading the 3C507 ODI MLID driver
	here instead.  I think you can get one from 3Com (anonymous FTP
	to ftp.3com.com)

2.	If you load ODIPKT using all defaults it provides a packet driver
	class service depending on the frame type of the 0th (actually
	first) ODI "logical interface" on interrupt 69.  You seem to want
	this on interrupt 63 so use "odipkt 0 99" (ODIPKT wants the software
	interrupt number in decimal).  This will prevent WINPKT from
	complaining that it can't find it.

3.	You only need to load WINPKT if you are using a Windows-unaware DOS
	TCP/IP application like NCSA Telnet or CUTCP TN3270.  If used, these
	applications should use software interrupt 63 for their packet driver
	interface under Windows (using 60 will bypassing WINPKT completely,
	and cause your system to crash and burn).

	If you are using WinQVTNet exclusively, you don't need this at all.

4.	Your QVT_NET.RC file should specify the use of software interrupt 63.
	There is no need for PKTINT to go through WINPKT.

Your NET.CFG file should look something like:

Show Dots = On

Link Driver 3C507
	Frame Ethernet_II
	Frame Ethernet_802.3
	Protocol IPX 0 Ethernet_802.3

If you use Ethernet II framing for IPX, use:

Show Dots = On

Link Driver 3C507
	Frame Ethernet_II
	Protocol IPX 8137 Ethernet_II

The fact the the Frame Ethernet_II comes first ensures that the first ODI
"logical interface" will be the type that ODIPKT wants for TCP/IP.

You don't have to list the protocols for TCP/IP in the Link Driver section,
since ODIPKT registers with the LSL as a "default" packet handler (gets
all packets not destined elsewhere).  If you prefer to list them they are:

	Protocol IP 800 Ethernet_II
	Protocol ARP 806 Ethernet_II
	Protocol RARP 8035 Ethernet_II

HTH.
--
James Harvey    IUPUI OIT Technical Support
harvey@iupui.edu  uucp: iugate!harvey  bitnet: harvey@indyvax