Date:	Mon, 2 Jul 2001 13:12:16 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	ghphpr <ghphpr AT ntlworld DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Dos Shell/Full Dos Window Problems
In-Reply-To:	<000701c102d1$18561680$5de4ff3e@ghphpr>
Message-ID:	<Pine.SUN.3.91.1010702131014.4695B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 2 Jul 2001, ghphpr wrote:

> Because the output from the scrren flashes by at high speed I cannot capture
> the files that are being executed by the dos shell stub which is what I need
> to do if I am to determine which sub file is causing the problem.
> Is there a de-compiler available that I can use for this purpose or do you
> have any other ideas as to how I can capture the output from the dos shell
> screen?

Did you try the methods suggested by section 6.15 of the DJGPP FAQ list 
(http://www.delorie.com/djgpp/v2faq/faq6_15.html)?  In particular, the 
program SCRIPT mentioned there can capture any DOS output and put it into 
a file.

- Raw text -