Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!dog.ee.lbl.gov!izuba.ee.lbl.gov!jackz
From: jackz@izuba.ee.lbl.gov (Jack Zelver)
Newsgroups: comp.windows.ms
Subject: Re: NCSA telnet under windows ... PIF needed
Message-ID: <9562@dog.ee.lbl.gov>
Date: 5 Feb 91 19:17:35 GMT
References: <2200@travis.csd.harris.com> <wjhauber.665359864@calvin.cc.iastate.edu>
Reply-To: jackz@izuba.ee.lbl.gov (Jack Zelver)
Distribution: na
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 30
X-Local-Date: Tue, 5 Feb 91 11:17:35 PST

In article <wjhauber.665359864@calvin.cc.iastate.edu> wjhauber@iastate.edu (Hauber Wayne) writes:
>...
>I am using a PIF file to start NCSA Telnet under Windows.  If I recall
>correctly, the key thing is to check "exclusive" "full screen" and "close
>on exit".  I have memory set to 52 and kb desired set to -1.
>
>NCSA telnet won't tolerate running in a window hence the full screen setting
>and it WON'T run in the background as a server without losing characters.

This is very misleading... I manage several diverse PC systems on different
subnets here and we have NCSA Telnet running under windows in 
NON-exclusive, NON-full screen modes.  They've been running this way
ever since Windows 3.0 became available, using the modified packet driver
set for W3.0.  (Under 386 enhanced mode, of course)

I leave mine running in background as a server all the time unless I'm
using it.  Never have lost a character (that I know of!) yet.

My pif file is pretty much the default that came with Win3.0 except that I
allow background operation and close the window on exit.  Neither of these
is required, except you won't run in background unless you allow it, of
course.

The ethernet cards are WD8000's, 3C501's, and 3C503's.  Just make sure you
use the correct packet drivers.

Jack Zelver
Lawrence Berkeley Laboratory
U.C., Berkeley
jszelver@lbl.gov