Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!enea!tut!santra!clinet!msa
From: msa@clinet.FI (Markku Savela)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re:  Another Request re. Telnet for Asynch Programs
Keywords: telnet, int14, cmu pc-ip
Message-ID: <568@clinet.FI>
Date: 15 Jan 88 23:42:59 GMT
References: <8801130752.aa13944@Louie.UDEL.EDU>
Reply-To: msa@clinet.UUCP (Markku Savela)
Organization: City Lines Oy, Helsinki, Finland
Lines: 53


> I think someone modified the CMU-PCIP to use the 14H INT about 6 mo ago,
> but I haven't heard anymore on that subject.  I might be able to
> provide you with a pointer, but unless you are a MSC codesmith you
> should steer clear.

	I *hacked* the CMU-PCIP telnet to catch the INT 14H. I even
	posted the assembler (MASM) code which did the catching.
	What I didn't post, were the modified modules 'TN.C' and
	'TELNET.C'. Should/Can I? They are useless without the full
	PC-IP distribution.

	The new Kermit 2.29c uses INT14 if it doesn't find the
	standard serial port. I could use that on top of my
	telnet, if I could somehow force the use of INT14....

> BE WARNED you may have troubles printing to a serial printer if you do
> this, the mode command (for printing) likes 14H as well.

	I have normally 3COM net on my PC and I usually redirect
	PRN to a remote printer on a server. I can still print to
	PRN (=remote printer) while my "catcher" is active. 3COM
	seems to catch printer earlier than INT14. There shouldn't
	be any problems, if the catcher leaves other ports alone
	(my version just calls the original INT14 handler for those).

	I use my program in connection with my own VT100 emulation.
	The host system is microVAX II running CMU TEK TCP-IP and
	sometimes Apollo workstation. Before raising any hopes too
	high, I must mention couple of problems (I haven't done much
	to the program after the first try):

	- sometimes the echo from VAX seems to get one character
	  too late. The state goes away, if I just stop for second
	  or two.

	- a more serious problem is, that occasionally it loses
	  a bunch of characters (coming from vax to pc). (I have
	  an internal buffer for incoming TCP data. If the buffer
	  becomes full, I just throw away -- I didn't know enough
	  of the internal PC-IP tasking to try a task switch while
	  handling TCP upcall -- if that is possible/allowed, the
	  problem may go away...).

	That's it. I just wanted to test an idea, the result works
	but is not perfect.

	ps.	Is there a version PC-IP, which would have the FTP?
--
-- (I cannot send private mail -- not allowed here, sorry)
-- Markku Savela, UUCP: msa@clinet.fi
-- Nokia Information Systems
-- P.O. BOX 780 SF-00101 HELSINKI, FINLAND