home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!nic.csu.net!hippo.sonoma.edu!hippo
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: NCSA Telnet & WINPKT
- Message-ID: <hippo.41.0@sonoma.edu>
- From: hippo@sonoma.edu (Michel Davidoff)
- Date: 4 Sep 92 13:21:00 PDT
- References: <1992Sep4.184222.280@news.uiowa.edu>
- Organization: Sonoma state university
- Nntp-Posting-Host: hippo.sonoma.edu
- Lines: 34
-
- In article <1992Sep4.184222.280@news.uiowa.edu> boyken@herky.cs.uiowa.edu (Karl Boyken) writes:
- >Subject: NCSA Telnet & WINPKT
- >From: boyken@herky.cs.uiowa.edu (Karl Boyken)
- >Date: Fri, 4 Sep 1992 18:42:22 GMT
- >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
- >
- Try in the config.tel interupt=62
-