Mail Archives: djgpp-workers/1999/04/13/09:38:50
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> Hmm, now that I think about this, maybe calling `system' to run
> AUTOEXEC.BAT, and then examining the results in the environment *is*
> the way to deal with many of the complexities which were mentioned in
> this thread?
No, my autoexec.bat files (I have more than 17 managed by a program) normally
ends calling something like Norton Commander, this will be at least confusing
for the user. Also: Some autoexec.bat files loads TSRs that won't check if
they are already loaded. Also: Some autoexec.bat files initializes hardware,
not a good idea to reset some settings, etc, etc. Running autoexec.bat isn't
a simple thing.
I think is much more easy to interpret and simulate the autoexec.bat. After
all the language is very silly. You'll need to find the size of the path and
environment, but looking at the OS version and the config.sys you can get
close, also you can do some tests.
SET
------------------------------------ 0 --------------------------------
Visit my home page: http://welcome.to/SetSoft
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(5411) 4759 0013
- Raw text -