All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott <drmemory@3rivers.net>
To: Frantisek Hanzlik <franta@hanzlici.cz>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOS program recording it's parameters and environment?
Date: Wed, 18 Jan 2012 12:17:54 -0700	[thread overview]
Message-ID: <20120118191754.GE765@drmemory.local> (raw)
In-Reply-To: <4F17112A.8020600@hanzlici.cz>

On Wed, Jan 18, 2012 at 07:36:26PM +0100, Frantisek Hanzlik wrote:
> 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?  

> 
> 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.

Franta,

I think that Frank is suggesting to use the "strings" not on
WINPROG.EXE but on the closed-source DOS program that calls
it. Wouldn't "strings" then show the command-lines which it is using?
Maybe I'm way off base here....

Scott.

  reply	other threads:[~2012-01-18 19:17 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
2012-01-18 19:17         ` Scott [this message]
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=20120118191754.GE765@drmemory.local \
    --to=drmemory@3rivers.net \
    --cc=franta@hanzlici.cz \
    --cc=linux-msdos@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.