Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3EFCA48A.1DE3465C@dessent.net>
Date:	Fri, 27 Jun 2003 13:09:46 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
X-Accept-Language:	en,pdf
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Output suppressed with ssh or telnet
References:	<3EFC2F1100000885 AT ims3c DOT cp DOT tin DOT it>

Marco Marcantelli wrote:

>      when I'm in telnet or ssh and run Dos programs like Word Star, Norton
> Commander or a Cobol run-time for dos, I do not receive any Output, but
> the programs are running !! If i try in local the programs works well.

Those old DOS apps don't use stdin/stdout but rather they write directly
to the screen buffer (or use BIOS calls.)  That was how things were done
in the old days, because no one really had any notion of remote access
in DOS.  You'll have to use a specialized program such as PC Anywhere
that can intercept the BIOS interrupts and/or virtualize the screen
buffer and cope with those old programs.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -