home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!wupost!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!news.uiowa.edu!boyken@herky.cs.uiowa.edu
- From: karl-boyken@uiowa.edu (Karl Boyken)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: SUMMARY: NCSA Telnet & WINPKT
- Message-ID: <1992Sep11.133027.26740@news.uiowa.edu>
- Date: 11 Sep 92 13:30:27 GMT
- Sender: news@news.uiowa.edu (News)
- Organization: Dept. of Comp. Sci., U. of Iowa
- Lines: 20
- Nntp-Posting-Host: makwa.cs.uiowa.edu
-
- Thanks to everyone who responded to my original question about why NCSA Telnet
- was complaining that it couldn't find the packet driver vector. I received
- a number of replies, ranging from "you're doing everything correctly; it must
- be a bug" to "use the decimal equivalent of the hex vector number" to "just
- let Telnet search for the vector".
-
- One suggestion does seem to work: in CONFIG.TEL, use "ioaddr" to specify the
- packet driver vector, not "interrupt". When I use ioaddr=60, Telnet quits
- complaining that it can't find the vector. However, Chapter 7 of the Telnet
- documentation states that the "interrupt" should be used to specify the vector.
- Is this a bug in the documentation?
-
- Unfortunately, I lost the original message that told me about using ioaddr, so
- I cannot thank the sender directly. So, thanks again--you know who you are.
-
- ***** _My_ views, no one else's--except those I plagiarize *****
- Karl Boyken, system programmer |
- Department of Computer Science | This is no social crisis
- The University of Iowa | Just another tricky day for you
- karl-boyken@uiowa.edu | -- Pete Townshend
-