public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Crawford <psc@sat.dundee.ac.uk>
To: Frantisek Hanzlik <franta@hanzlici.cz>
Cc: DOSEMU/FreeDOS <linux-msdos@vger.kernel.org>
Subject: Re: DOS program recording it's parameters and environment?
Date: Fri, 27 Jan 2012 12:01:25 +0000	[thread overview]
Message-ID: <4F229215.1040801@sat.dundee.ac.uk> (raw)
In-Reply-To: <4F165699.1080204@hanzlici.cz>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

Dear Frantisek,
> Excuse me for slightly OT question. Know anyone DOS program, which is
> able record infos with what parameters was started and eventually
> other informations about calling environment (e.g. environment
> variables, available memory etc.)?

Attacked is a gzip'd tar file with a simple program to do this, but 
re-named .dat instead of .tgz as we use Google mail and it is too stupid 
to allow compressed executables to be emailed.

Save to a Linux box and then re-name, then the usual arcive manager or 
tar can extract the files.

It creates a file dosenv.txt in the working directory and prints out the 
calling arguments and the environment to that file. If you have a C 
compiler (I used Microsoft's C6.0 DOS compiler from around 1988) you 
could modify this program to do other things (e.g. date/time based file 
names if they fit the 8.3 limit of DOS, etc)

Regards,
Paul
-- 
Dr. Paul S. Crawford
Satellite Station
Dundee University
Small's Wynd, Dundee,
DD1 4HN, U.K.
Tel: +44 (0)1382 38 4687
Email: psc@sat.dundee.ac.uk
The University of Dundee is a Scottish Registered Charity, No. SC015096

[-- Attachment #2: dosenv.dat --]
[-- Type: application/x-ns-proxy-autoconfig, Size: 6377 bytes --]

  parent reply	other threads:[~2012-01-27 12:01 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
2012-01-27 12:01 ` Paul Crawford [this message]
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=4F229215.1040801@sat.dundee.ac.uk \
    --to=psc@sat.dundee.ac.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox