home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!olivea!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!news.uiowa.edu!boyken@herky.cs.uiowa.edu
- From: boyken@herky.cs.uiowa.edu (Karl Boyken)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: NCSA Telnet & WINPKT
- Message-ID: <1992Sep4.184222.280@news.uiowa.edu>
- Date: 4 Sep 92 18:42:22 GMT
- Sender: news@news.uiowa.edu (News)
- Organization: Dept. of Comp. Sci., U. of Iowa
- Lines: 28
- Nntp-Posting-Host: makwa.cs.uiowa.edu
-
- I've set up a number of PCs with NCSA Telnet and Windows, using WINPKT.
- For the packet driver, I always use 0x62 for the packet interrupt, then use
-
- winpkt 0x60 0x62
-
- to start WINPKT. WINPKT says that it finds the packet driver and that the
- new interrupt is 0x60. I configure the config.tel thus:
-
- hardware=packet
- interrupt=60
-
- But, when I start Telnet in Windows, I always get this message:
-
- Warning, packet driver vector incorrect, using default search
-
- Telnet evidentally does find an interrupt, but I'd prefer that it didn't have
- to search for it.
-
- If I don't load WINPKT and change the packet driver invocation to 0x60,
- Telnet starts up without the warning.
-
- What am I doing wrong? Thanks in advance.
-
- ***** _My_ views, no one else's--except those I plagiarize *****
- Karl Boyken, system programmer | Distant cousins, there's a limited supply, and
- Department of Computer Science | we're down to the dozens, and this is why:
- The University of Iowa | big-eyed beans from Venus--oh my, oh my!
- boyken@herky.cs.uiowa.edu | -- Captain Beefheart
-