X-Organization: Penn State University / University Libraries
X-Envelope-to: win3-l@UICVM.BITNET
X-VMS-To: WIN3_L
Newsgroups: bit.listserv.win3-l
Date:         Tue, 1 Sep 1992 16:16:00 EST
From:         "J.Lance Wilkinson, (814) 865-1818" <JLW@PSULIAS.BITNET>
Subject:      Re: Win appl. thar uses a TSR ??
X-To:         WIN3-L@PSULIAS.BITNET

On 1-SEP-1992 15:52, "Alexandre Leib Grojsgold <ALGOLD@BRLNCC.BITNET>"
Asked, "Win appl. thar uses a TSR ??"
>-------------------------------------------------------------------------------
   -
>Can someone give any hints about running a windows application that must
>use a TSR DOS program?
>
>I am trying to use NCSA Telnet from within Windows 3.1, and the program
>requires access to a pcaket driver prevoiusly loaded.
>
>On every attempt, the system crasdhes.

The TSR must be loaded *BEFORE* invoking windows, like in your AUTOEXEC.BAT; I
suspect you're not trying to load it until you start your application (not that
I know that trying to run it as part of the application would fail; it's just
that I load the packet driver stuff during AUTOEXEC time, and it works fine
for me).  I run NCSA telnet as follows:

1) load the packet driver.  I use 3com's 3c523 MC Etherlink board; note the -w
switch to indicate Windows will [likely?] be in use.  Note also I load this
into high memory here.

        loadhigh 3c523 -w 0x60 3

2) load winpkt.  This is a driver I got somewhere (I can't remember where;
don't ask me and *don't* expect me to distribute a copy; try the DRIVERS list
<drivers@sun.soe.clarkson.edu> to look for packet driver stuff...) which
accomodates for the way that Windows might have swapped out the process needing
the packet driver at the time the packet driver might have data for it (I
*think*).  Note it uses software interrupt 0x61, and ties to the software
interrupt 0x60 used by the packet driver already loaded.

        loadhigh winpkt 0x61 0x60

3) run windows.  In windows you'll need a .PIF file for NCSA telnet that
invokes the batch job TELNET.BAT in your NCSA directory; make sure its working
directory is the NCSA directory or whatever else you need to do to make sure
NCSA telnet (TELBIN.EXE) is able to find it's CONFIG.TEL file, etc.  Mine
references a filename of C:\NCSA\TELNET.BAT, has a window title of "NCSA Telnet"
and a start-up directory of C:\, since C:\NCSA is in the PATH I set up before
running anything else in my autoexec.  I also flag Display Usage as Full
Screen.

Good luck; it works fine here.

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services             AT&T:      (814) 865-1818          |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU