From mboxrd@z Thu Jan  1 00:00:00 1970
From: Frantisek Hanzlik <franta@hanzlici.cz>
Subject: Re: DOS program recording it's parameters and environment?
Date: Wed, 18 Jan 2012 19:36:26 +0100
Message-ID: <4F17112A.8020600@hanzlici.cz>
References: <4F165699.1080204@hanzlici.cz> <4F16E21B.9030804@gmail.com> <4F170571.1090604@hanzlici.cz> <20120118115554.40e5333c.theatre@sasktel.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-msdos-owner@vger.kernel.org>
In-Reply-To: <20120118115554.40e5333c.theatre@sasktel.net>
Sender: linux-msdos-owner@vger.kernel.org
List-ID: <linux-msdos.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Frank Cox <theatre@sasktel.net>
Cc: linux-msdos@vger.kernel.org

Frank Cox wrote:
> On Wed, 18 Jan 2012 18:46:25 +0100
> Frantisek Hanzlik wrote:
> 
>> For example: closed-source DOS program which i'm using start windows
>> program WINPROG.EXE with parameters "C:\path\file /A delay=5".
> 
> Have you considered using "strings progname.exe" and see what you can find that
> way?  If the program isn't encrypted or compressed (with lzexe or whatever) you
> might find interesting things.  And if it is compressed, you may discover how
> and be able to uncompress it.

There is violent that DOS program assemble parameters ("command line") for
program which will execute dynamically, "strings" in this case will not be
very usefull.

Help will be, when DOSEMU debug made this, but such details IMO there are not.

Franta