home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!MSU.EDU!08071TCP
- From: 08071TCP@MSU.EDU (Doug Nelson)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: Can ""traditional"" comm programs talk TCP/IP?
- Message-ID: <9207311340.aa12752@louie.udel.edu>
- Date: 31 Jul 92 17:25:41 GMT
- References: <olivea!tymix!niagara!billp@UUNET.UU.NET>
- Sender: daemon@ucbvax.BERKELEY.EDU
- Reply-To: Doug Nelson <NELSON@msu.edu>
- Distribution: world
- Organization: The Internet
- Lines: 30
-
- Bill Putney writes:
- >I bought the new Procom+. It has support for INT14 which has the
- >potential for being a real nice feature. I am also running FTP's
- >PC/TCP which has an INT14 "server" called tnglass.
- >
- >Too bad you have to start tnglass in DOS before you start windows!
- >The long and short of this is that you can get one session going
- >to one destination. If you want to disconnect and go to somewhere
- >else you're hosed! You have to quit windows and go restart tnglass.
- >The other gotcha is that what tnglass really does is to start up
- >a telnet session and just leave the display stuff hanging for the
- >INT14 emulator to attach to. If you don't get windows up and the
- >session going before the remote host gives up on the connection
- >you're out'a luck again.
-
- This just didn't sound right, so I finally got PC/TCP set up to run
- under Windows. I don't normally run this way, although I might try
- it for a while now....
-
- Anyway, I set up Windows and PC/TCP with the kernel started before
- Windows, and VxD (VPCTCP.386) in Window's SYSTEM.INI. I then brought up
- TN in one window, and TNGLASS with Kermit in another window. I had no
- problem switching between the two windows, or with terminating a TNGLASS
- session and starting a new one.
-
- You ought to be able to do the same if you are running version 2.05 of
- PC/TCP. I'm currently running 2.05 pl 4.
-
- Doug Nelson nelson@msu.edu
- Michigan State University
-