home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.apps
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!dlg6627
- From: dlg6627@uxa.cso.uiuc.edu (Darmawan Ludirdja)
- Subject: Re: Windows and NCSA telnet....
- References: <BzDHwz.230@news.cso.uiuc.edu> <BzDv2A.H52@news.iastate.edu> <BzEs7J.3u0@m2.dseg.ti.com> <BzEvtH.Dwz@news.iastate.edu> <mcdonald.614@aries.scs.uiuc.edu>
- Message-ID: <BzF86E.DAI@news.cso.uiuc.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Date: Thu, 17 Dec 1992 20:42:10 GMT
- Lines: 66
-
- mcdonald@aries.scs.uiuc.edu (J. D. McDonald) writes:
-
- >In article <BzEvtH.Dwz@news.iastate.edu> rjhoffma@iastate.edu (Richard J. Hoffmann) writes:
-
-
- I just called NCSA here at the Univ. of Illinois.....just in case anybody
- need their phone #: (217)244-0638 or e-mail address: pctelnet@ncsa.uiuc.edu
- I talked to Terry....he said that there is a problem running telnet
- inside windows (background)....The next release of telnet (by May'93)
- may have this feature....If anybody has a clue on how to use
- it inside Windows, please e-mail and discuss with him.........
- He also mentioned that we need to change bios=yes in config.tel.
-
- >>As I think back on this problem, I realize that I did have problems with
- >>Telnet dropping me back to the DOS prompt during a session. The key to
- >>stopping this was adding the -w switch to the packet driver line in
- >>autoexec.bat. In other words, I load the packet driver thus:
-
- >>wd8003e -w 0x60 10 0x280 0xd800
-
- >>Until I did that, I could only execute Telnet under Windows if I set the
- >>*.pif so that Execution: was exclusive.
-
- For Dick, can you post the uuencode of the *.pif plese.
-
- >That is not the proper way to do it.
-
- >The proper ways are three:
-
- >1) If you don't need a packet driver for something else, use the
- > internal driver inside Telnet for your card. This may work well
- > inside Windows, or not.
-
- >2) If you want the pachet driverm you should load it **inside the DOS window
- > you are using for Telnet**. I.e. run Telnet from a batch file ..
- > first load thge packet driver, then telnet, then after exiting Telnet
- > unload the packet driver. Don't use the -w switch.
-
- >3) The best way, and the only reliable way if you want to run the
- > packet driver from DOS once and for all, is to load the packet driver
- > there (no -w switch), then outside Windows, load Pktmux, the packet
- > multiplexor. INSIDE windows run a batch file that loads a Pktdrv
- > (from the pktmux package), then telnet, and finally unloads the pktdrv.
- > This allows running Telnet, ftp, Trumpet, and lpr, all at once,
- > inside Windows. Outside Windows you can also run NFS too.
-
- I looked at the telnet manual...There is a section mention about
- Wollongong Group's WIN/TPC Installation (PKTDRV.EXE).....
- ^^^^^^^^^^^^
- I think this is similar to Doug's comment (#3) above...
-
- There are two notes however,
- a. The software interrupt number specified by the 8003/8013 packet
- driver (8003pkdr.exe) MUST be different from that specified by PKTDRV.
- For the 8003pkdr.exe program, this is specified by the /E Or
- /8 argument; in the PKTDRV.EXE, it is specified with the -N: argument.
- b. The hardware interrupt setting (specified with "-I:number") MUST match
- the hardware interrupt setting of the interface card (and the packet
- driver 8003pkdr.exe).
-
- Anybody know how to specify the parameters?
-
- >Doug McDonald
-
- Darmawan
- dlg6627@uxa.cso.uiuc.edu
-