home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!unlinfo.unl.edu!price
- From: price@helios.unl.edu (Chad Price)
- Subject: Re: NCSA telnet CPU usage
- Message-ID: <price.714418392@helios>
- Sender: news@unlinfo.unl.edu
- Nntp-Posting-Host: helios.unl.edu
- Organization: University of Nebraska - Lincoln
- References: <1992Aug21.135137.1131@murdoch.acc.Virginia.EDU> <66529@hydra.gatech.EDU>
- Distribution: usa
- Date: 21 Aug 92 17:33:12 GMT
- Lines: 29
-
- np4@prism.gatech.EDU (Nick Pomponio) writes:
-
- >In <1992Aug21.135137.1131@murdoch.acc.Virginia.EDU> wrp@cyclops.micr.Virginia.EDU (Bill Pearson) writes:
-
- >* When I run NCSA telnet under a DOS full screen window my Pulse meter
- >*suggests that I am hogging the CPU, even when it is in the background doing
- >*nothing. Likewise with epsilon for DOS.
- >*
- >* Is there a setting that I should change to tell these programs not
- >*to keep polling for something?
- >*
- >*Bill Pearson
-
- >I, too, have noticed this type of behavior. Even using 'type' to view a
- >file in another dos window while NCSA Telnet is running results in a slow,
- >jerky display.
- >--
-
- You need to play with the idle detect and the other parameter just above it
- on the DOS parameters list. Since NCSA telnet constantly polls to see what
- is happening, (as far as I can tell), you'll need to adjust the DOS session
- so reduce the priority in background.
-
- chad
-
- --
- chad
- price@helios.unl.edu
- cprice@molecular.unmc.edu
-