public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Frantisek Hanzlik <franta@hanzlici.cz>
To: Frank Cox <theatre@sasktel.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOS program recording it's parameters and environment?
Date: Wed, 18 Jan 2012 19:36:26 +0100	[thread overview]
Message-ID: <4F17112A.8020600@hanzlici.cz> (raw)
In-Reply-To: <20120118115554.40e5333c.theatre@sasktel.net>

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

  reply	other threads:[~2012-01-18 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  5:20 DOS program recording it's parameters and environment? Frantisek Hanzlik
     [not found] ` <4F16E21B.9030804@gmail.com>
2012-01-18 17:46   ` Frantisek Hanzlik
2012-01-18 17:55     ` Frank Cox
2012-01-18 18:36       ` Frantisek Hanzlik [this message]
2012-01-18 19:17         ` Scott
2012-01-27 12:01 ` Paul Crawford
2012-02-16 18:54   ` Frantisek Hanzlik
2012-02-16 21:01     ` Paul Crawford
2012-02-16 21:34       ` Frantisek Hanzlik
2012-02-17  1:57       ` Samuel Bronson
2012-02-17 22:29         ` Scott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F17112A.8020600@hanzlici.cz \
    --to=franta@hanzlici.cz \
    --cc=linux-msdos@vger.kernel.org \
    --cc=theatre@sasktel.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox