home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip.ibmpc:4441 comp.sys.novell:6078
- Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!mips!news.cs.indiana.edu!bronze!indyvax.iupui.edu!harvey
- From: harvey@indyvax.iupui.edu
- Subject: Re: Help with Novell's ODI drivers
- Message-ID: <1992Jul27.181252.1@indyvax.iupui.edu>
- Lines: 52
- Sender: news@bronze.ucs.indiana.edu (USENET News System)
- Nntp-Posting-Host: indyvax.iupui.edu
- Organization: Indiana University
- References: <1992Jul25.045135.21123@CS.ORST.EDU> <14t5nkINN5r7@matt.ksu.ksu.edu> <BrzAx2.2x7@usenet.ucs.indiana.edu>
- Date: 27 Jul 92 18:12:52 -0500
-
- In article <BrzAx2.2x7@usenet.ucs.indiana.edu>, jiliu@copper.ucs.indiana.edu (Jian Liu) writes:
- >>>This is probably a FAQ. I have just started the process of migrating
- >>>from Crynwr Packet Drivers to Novell's ODI drivers for reasons too numerous
- >>>to enumarate here, but I would really love to keep using my favourite PD
- >>>applications like WINQVTNET and Trumpet. Is there a way to do that, and if
- >>>yes how do I go about it?
- >
- > I have both running under ODI. Here's my odi.bat, which is the last one
- > in my autoexec.bat
- >
- > lh lsl
- > lh wdplus
- > lh pktodi
- ^^^^^^What's this??
-
- > lh odipkt
- > lh pktint
- > lh netx
- >
- > For Trumpet, I just set it and it ran like magic. Nothing else was required.
-
- Obviously Trumpet searches for the a software interrupt vector hooked into a
- packet driver. The packet driver spec is purposefully designed to allow this.
- Not all applications do it however (i.e., lack of `magic' by wnqvtnet, see
- below).
-
- > For wnqvtnet (v 2.6), I had some problem first. Before I had the odi
- > drivers, I used wd8003e, where I could specify and irq number (0x60, etc), but
- > the new odi does not give you this opportunity, and in the qvt_tcp.rc of the
- > winqvtnet requires that packet_vector= to be filled with a value. I posted
- > a query in one of the newsnet groups, which I don't remember now, and thanks
- > to someone, who I don't remember now as well, who told me that the odipkt
- > uses 69 as the irq number, and I put 69 on that line, and wnqvtnet now runs
- > like magic as well.
- >
- > Jian
-
- It's not an IRQ number. `Vector' means the software interrupt number used
- by the packet driver. ODIPKT uses hex 69 as the default, for reasons known
- only to the author. It also parses arguments in decimal, so the docmentation
- states that the vector used is 105 (decimal). ODIPKT certainly does allow
- you to specify the vector used. For example, to use vector hex 60 on the
- first logical interface, load it as follows:
-
- ODIPKT 0 96
-
- And the reason it works isn't `magic', it's because the software interrupt
- number wnqvtnet is using to call the packet driver is the same one the packet
- driver is servicing calls on.
- --
- James Harvey IUPUI OIT Technical Support/Networks
- harvey@iupui.edu uucp: iugate!harvey bitnet: harvey@indyvax
-