home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip.ibmpc:4444 comp.sys.novell:6087
- Path: sparky!uunet!gatech!news.byu.edu!yvax.byu.edu!cunyvm!rohvm1!rbyaml
- Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
- Subject: Re: Help with Novell's ODI drivers
- Message-ID: <92209.202057RBYAML@rohvm1.rohmhaas.com>
- From: Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com>
- Date: Mon, 27 Jul 1992 20:20:57 EDT
- References: <1992Jul25.045135.21123@CS.ORST.EDU><14t5nkINN5r7@matt.ksu.ksu.edu> <BrzAx2.2x7@usenet.ucs.indiana.edu>
- Organization: Rohm and Haas Company
- Lines: 30
-
- In article <BrzAx2.2x7@usenet.ucs.indiana.edu>, jiliu@copper.ucs.indiana.edu
- (Jian Liu) says:
- >
- >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.
- That was me. I used Manifest (it comes with QEMM) to see what interrupts
- ODIPKT used.
-
- One of the nice thing about ODI drivers is that they're all unloadable,
- so you can unload them if you need the memory back, or if you want to
- change your configuration (frame types, etc). Unfortunately, ODIPKT isn't
- unloadable, and it locks in all the other ODI drivers loaded before it.
-
- I never did like using MARK and RELEASE, so if anyone knows of a way to
- gracefully unload ODIPKT, I'd appreciate it.
- >
- >Jian
- >
- Aengus
- --
- RBYAML@ROHMHAAS.COM Aengus Lawlor
- RBYAML@ROHVM1.BITNET (who used to be ALAWLOR@DIT.IE)
- "How about some of that famous Dublin wit, Barman?"
- "Certainly, sir. Would that be Dry or Sparkling?"
-